Displaying 4 results from an estimated 4 matches for "extents_list".
2019 Mar 20
2
New extents structure proposal
I think the extents map is just too complicated and is unnecessarily
so. How about instead we define the plugin interface to be:
int can_extents (void *handle); // as before
int extents (void *handle, uint32_t count, uint64_t offset, uint32_t flags,
struct nbdkit_extents_list *list);
and have the extents_list be a simple list. The first extent you add
must start at offset. And you're only allowed to append monotonically
increasing adjacent extents to it. Plugins must return at least one
extent, but are not required to return more than one extent
(regardless of f...
2019 Mar 20
0
Re: New extents structure proposal
...extents map is just too complicated and is unnecessarily
> so. How about instead we define the plugin interface to be:
>
> int can_extents (void *handle); // as before
> int extents (void *handle, uint32_t count, uint64_t offset, uint32_t flags,
> struct nbdkit_extents_list *list);
>
> and have the extents_list be a simple list. The first extent you add
> must start at offset. And you're only allowed to append monotonically
> increasing adjacent extents to it. Plugins must return at least one
> extent, but are not required to return more than on...
2019 Mar 20
2
Re: New extents structure proposal
...complicated and is unnecessarily
> > so. How about instead we define the plugin interface to be:
> >
> > int can_extents (void *handle); // as before
> > int extents (void *handle, uint32_t count, uint64_t offset, uint32_t flags,
> > struct nbdkit_extents_list *list);
> >
> > and have the extents_list be a simple list. The first extent you add
> > must start at offset. And you're only allowed to append monotonically
> > increasing adjacent extents to it. Plugins must return at least one
> > extent, but are not requir...
2020 Jul 22
2
[nbdkit PATCH] server: Reinstate limited use of -e/-exportname.
While we are unlikely to change our decision that -e should not
control our response to NBD_OPT_LIST (because we intend to add a new
callback .extents_list for that), it turns out that it is a lot easier
to write:
nbdkit -U - -e foo info --run 'nbdsh -u "$uri" -c "print(h.pread(3, 0))"'
than it is to write the equivalent:
nbdkit -U - info --run 'nbdsh -u nbd+unix:///foo\?socket=$unixsocket \
-c "print(h.pread(...