Re: [Libguestfs] [PATCH libnbd proposal] api: Add semi-private function for freeing persistent data.

On 8/11/19 8:03 AM, Richard W.M. Jones wrote: Would this change the signature of callbacks? With this in place, you no longer need the VALID|FREE parameter, but can defer the free action to an added free callback. How would you actually track when to call the free callback? I guess each time a pointer lifetime ends (basically, when retiring a completed command) we check each pointer grabbed by that command and compare it against the list of registered pointers for any free callbacks to use? How does that scale, if the user can register an arbitrary number of pointers because they queue up a large number of requests before starting the poll loop? Is the existing idea of a VALID|FREE parameter not sufficient? If we can convince the C bindings for python nbd.aio_pread to increase the refcount of buf, and then install a C completion handler (whether the python user called nbd.aio_pread with no python completer, or whether they called nbd.aio_pread_complete) that does the decref when called with FREE, then that would do the same job, even without the need for nbd_add_free_callback, wouldn't it? And there's no issue of scanning through a list of pointers with a free callback associated with them (storing registered pointers with some sort of hash may eventually get to amortized O(1) lookup, but that seems like a lot of overhead compared to the fact that we already have O(1) access to when to call the completion callback with the FREE flag). -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org