search for: libnbd_state_hole

...constants in the scope later on, Yeah, could be a problem. We have until API stability freeze to change our minds. I'm guessing we might need: LIBNBD_CONTEXT_BASE_ALLOCATION_STATE_HOLE LIBNBD_CONTEXT_BASE_ALLOCATION_STATE_ZERO but yes, that's a mouthful to type. Keeping the short names LIBNBD_STATE_HOLE for now is okay. > > - the fact that "base" and "base:allocation" are even defined, which might be > useless, since listing contexts of a namespace is not exposed, Rich still has the idea of adding a 'qemu-nbd --list' counterpart, so defining a...

This just defines the namespace, its contexts and related constants and the only supported one is currently base:allocation. The names of the constants are not very future-proof, but shorter than LIBNBD_META_NS_CONTEXT_BASE_ALLOCATION or similar. Currently the output looks like this: /* "base" namespace */ /* "base" namespace contexts */ /* "base:allocation"

...t; >Yeah, could be a problem. We have until API stability freeze to change >our minds. I'm guessing we might need: > >LIBNBD_CONTEXT_BASE_ALLOCATION_STATE_HOLE >LIBNBD_CONTEXT_BASE_ALLOCATION_STATE_ZERO > >but yes, that's a mouthful to type. Keeping the short names >LIBNBD_STATE_HOLE for now is okay. > I forgot to say I also went with that naming as NBD_STATE_{HOLE,ZERO} are defined and spelled that way in the NBD protocol spec. >> >> - the fact that "base" and "base:allocation" are even defined, which might be >> useless, si...