search for: nbd_notify_write

...mand. (Perhaps the > generator could reduce some of the boilerplate duplication, if a later > patch wants to refactor this). I'm writing some code now using these new nbd_aio_<CMD>_notify functions, and I temporarily confused myself because these are similar to nbd_notify_read and nbd_notify_write (the functions used to signal to the state machine that the socket is ready for reading/writing). I wonder if we should rename something here. My suggestions are either of the following or both: (I) Rename nbd_notify_read / nbd_notify_write to nbd_ready_to_read / nbd_ready_to_write. (II) Rename...

...generator could reduce some of the boilerplate duplication, if a later >> patch wants to refactor this). > > I'm writing some code now using these new nbd_aio_<CMD>_notify > functions, and I temporarily confused myself because these are similar > to nbd_notify_read and nbd_notify_write (the functions used to signal > to the state machine that the socket is ready for reading/writing). > > I wonder if we should rename something here. My suggestions are > either of the following or both: > > (I) Rename nbd_notify_read / nbd_notify_write to nbd_ready_to_read / &g...

I still need to wire in the use of *_notify functions into nbdkit to prove whether it makes the code any faster or easier to maintain, but at least the added example shows one good use case for the new API. Eric Blake (6): api: Add nbd_aio_in_flight generator: Allow DEAD state actions to run generator: Allow Int64 in callbacks states: Prepare for aio notify callback api: Add new