Eio.Condition
Waiting for a condition to become true.
Waiters call await
in a loop as long as some condition is false. Fibers that modify inputs to the condition must call broadcast
soon afterwards so that waiters can re-check the condition.
Example:
let x = ref 0
let cond = Eio.Condition.create ()
let mutex = Eio.Mutex.create ()
let set_x value =
Eio.Mutex.use_rw ~protect:false mutex (fun () -> x := value);
Eio.Condition.broadcast cond
let await_x p =
Eio.Mutex.use_ro mutex (fun () ->
while not (p !x) do (* [x] cannot change, as mutex is locked. *)
Eio.Condition.await cond mutex (* Mutex is unlocked while suspended. *)
done
)
It is used like this:
Fiber.both
(fun () ->
traceln "x = %d" !x;
await_x ((=) 42);
traceln "x = %d" !x
)
(fun () ->
set_x 5;
Fiber.yield ();
set_x 7;
set_x 42;
)
val create : unit -> t
create ()
creates a new condition variable.
await t mutex
suspends the current fiber until it is notified by t
.
You should lock mutex
before testing whether the condition is true, and leave it locked while calling this function. It will be unlocked while the fiber is waiting and locked again before returning (it is also locked again if the wait is cancelled).
val await_no_mutex : t -> unit
await_no_mutex t
suspends the current fiber until it is notified by t
.
This is only safe to use in the case where t
is only used within a single domain, and the test for the condition was done without switching fibers. i.e. you know the condition is still false, and no notification of a change can be sent until await_no_mutex
has finished suspending the fiber.
val loop_no_mutex : t -> (unit -> 'a option) -> 'a
loop_no_mutex t update
runs update ()
until it returns Some x
, then returns x
.
If update ()
returns None
then it waits until broadcast
is called before retrying. If broadcast
is called while update
is running, update
runs again immediately.
For example, if broadcast config_changed
is performed after some configuration file is changed, then you can ensure load_config
will always eventually have seen the latest configuration like this:
Fiber.fork_daemon ~sw (fun () ->
loop_no_mutex config_changed (fun () -> load_config (); None)
)
Note that, since there is no lock, load_config
may see a half-written update if the configuration is changed again before it finishes reading it, so it should just log the error and wait to be called again.
val broadcast : t -> unit
broadcast t
wakes up any waiting fibers (by appending them to the run-queue to resume later).
If no fibers are waiting, nothing happens.
This is intended only for integrating Eio with other IO libraries.
register_immediate t fn
will call fn ()
the next time broadcast
is called.
fn
runs immediately from the caller's context, which might not be an Eio thread, or may be a signal handler, etc. Therefore, care is needed here. This is typically used to send a wake-up event to some non-Eio library.
val cancel : request -> bool
cancel request
tries to cancel a request created with register_unsafe
.
It returns true
if the request was cancelled (the callback will never be called), or false
if the request was already complete (the callback has already been called).