Displaying 3 results from an estimated 3 matches for "nbdkit_plugin_open".
2020 Jul 30
3
Re: [PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
...lugin, it would also allow us
to create a new --filter=shared that can be thrown in front of any
plugin (rendering the existing 'nbdkit nbd --shared' obsolete in favor
of 'nbdkit nbd --filter=shared').
Basically, I'm thinking we need the following filter-only functions:
int nbdkit_plugin_open(int readonly, struct nbdkit_next_ops **next_ops,
void **nxdata);
which a filter can call at any point between .after_fork and .unload to
open a distinct connection into the plugin independent of any filter
clients, and which returns by reference a next_ops/nxdata pair tha...
2020 Jul 30
0
Re: [PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
...us to create a new --filter=shared that can be thrown in front of
> any plugin (rendering the existing 'nbdkit nbd --shared' obsolete in
> favor of 'nbdkit nbd --filter=shared').
>
> Basically, I'm thinking we need the following filter-only functions:
>
> int nbdkit_plugin_open(int readonly, struct nbdkit_next_ops **next_ops,
> void **nxdata);
>
> which a filter can call at any point between .after_fork and .unload
> to open a distinct connection into the plugin independent of any
> filter clients, and which returns by reference a nex...
2020 Jul 22
3
[PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
Updated proposal, taking into account the default export. Instead of
adding a second call, I made a couple of changes to list_exports:
(1) If the plugin has a concept of a default export, it should add it
as the first element in the exports list.
(2) There is a new default_only flag which tells the plugin that the
client is trying to request the name of the default export, so the