search for: notify_readable

...uby/examples/event_test.rb to use EventMachine (a library for writing event driven programs). I have attached my attempt, which appears subscribe to events but never executes the callbacks I provide. I know this because when I reset domains (virsh reset VM) I see messages appear from the Handlers::notify_readable(), which should then invoke Libvirt::event_invoke_handle_callback() - but the output from the callbacks never appears. Typical output from the program looks like: add_handle fd=11 events=1 add_timer interval=-1 :notify_readable id=0 fd=11 events=1 update_timer id=0 interval=0 :notify_readable id=0...

On 6/5/19 6:15 AM, Richard W.M. Jones wrote: > Split h->state into: > > - h->state = the state on entry to the locked region > > - h->next_state = the current state and what the "publicly visible" > state will become when we leave the locked region The rest of this thread discusses potential other names, such as h->public_state for the state visible

I think in general we should have a good idea of the thread model that we support with libnbd. At the moment we have a handle lock which only means that simultaneous calls into the handle won't corrupt it; however it doesn't mean that you don't expect the handle state to change between calls if the handle is accessible by two threads. Is that the model we trying to achieve or

I need to think about this patch series a bit more, but it does at least pass the tests. Rich.

This isn't quite finished because not all of the tests or examples have been updated, but it demonstrates an idea: Should we forget about the concept of having multiple connections managed under a single handle? In this patch there is a single ‘struct nbd_handle *’ which manages a single state machine and connection (and therefore no nbd_connection). To connect to a multi-conn server you must