On 7/21/20 9:04 AM, Eric Blake wrote:
I was wondering if we should instead have the core server handle memory,
similar to how we handle .exports (that is, the server allocates a
I meant .extents there.
container, passes it to the plugin, and the plugin calls
nbdkit_export_list_add("...") as many times as it wants, where the
server now frees the list instead of throwing the burden on the plugin).
 Offhand, I'm thinking either approach could be made to work, so it
becomes a decision on which is easier to maintain (both from the
perspective of the core server code, and for an arbitrary plugin writer).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization:
qemu.org |
libvirt.org