Displaying 5 results from an estimated 5 matches for "notify_read".
Did you mean:
inotify_read
2015 Jul 24
0
libvirt events and Ruby's EventMachine
...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 i...
2019 Jun 05
2
Re: [PATCH libnbd 4/4] lib: Atomically update h->state when leaving the locked region.
...uot;;
> - pr " ev, nbd_internal_state_short_string (get_state (h)));\n";
> + pr " ev, nbd_internal_state_short_string (get_next_state (h)));\n";
I'm also wondering if we should treat external events more like
interrupts, where calling nbd_aio_notify_read() in an incorrect state
succeeds by setting a flag that is not cleared until we later reach a
state that can actually care about the flag, rather than by rejecting
the call out-right for being in the wrong state. (That is, states where
we are NOT expecting a notify_read() are the same as setting a...
2019 Jun 08
0
Re: [PATCH libnbd 4/4] lib: Atomically update h->state when leaving the locked region.
...d
need to support more complex thread models or can we rely on callers
to use their own mutex on top?
More comments below ...
On Wed, Jun 05, 2019 at 10:23:57AM -0500, Eric Blake wrote:
> I'm also wondering if we should treat external events more like
> interrupts, where calling nbd_aio_notify_read() in an incorrect state
> succeeds by setting a flag that is not cleared until we later reach a
> state that can actually care about the flag, rather than by rejecting
> the call out-right for being in the wrong state. (That is, states where
> we are NOT expecting a notify_read() are t...
2019 Jun 05
9
[PATCH libnbd 0/4] lib: Atomically update h->state.
I need to think about this patch series a bit more, but it
does at least pass the tests.
Rich.
2019 May 23
2
[PATCH libnbd] api: Get rid of nbd_connection.
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