search for: nbdkit_extents_list

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...

...ink 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 on...

...st 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 requir...