search for: nbd_notify_error

...ket 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. I'm still wondering if we want to add an nbd_notify_error for the I/O thread to inform libnbd about a POLLERR situation (as otherwise the libnbd state machine may not notice the error until much later). I don't think nbd_read_to_error() sounds good, so keeping the name nbd_notify_FOO for notifying the state machine about a particular change in the fd...

On Sat, Jun 29, 2019 at 08:28:28AM -0500, Eric Blake wrote: > As mentioned in the previous patch, there are situations where an aio > client wants instant notification when a given command is complete, > rather than having to maintain a separate data structure to track all > in-flight commands and then iterate over that structure to learn which > commands are complete. It's