[ViewVC] Diff of: cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.127 by root, Fri Feb 1 13:47:08 2008 UTC vs.
Revision 1.128 by root, Fri Feb 1 13:53:56 2008 UTC

 =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)
 That means that changing a timer costs less than removing/adding them
 as only the relative motion in the event queue has to be paid for.
-=item Starting io/check/prepare/idle/signal/child watchers: O(1)
+=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
 These just add the watcher into an array or at the head of a list.
-=item Stopping check/prepare/idle watchers: O(1)
+=item Stopping check/prepare/idle/fork/async watchers: O(1)
 =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
 These watchers are stored in lists then need to be walked to find the
 correct watcher to remove. The lists are usually short (you don't usually
 Priorities are implemented by allocating some space for each
 priority. When doing priority-based operations, libev usually has to
 linearly search all the priorities, but starting/stopping and activating
 watchers becomes O(1) w.r.t. prioritiy handling.
+=item Sending an ev_async: O(1)
+=item Processing ev_async_send: O(number_of_async_watchers)
+=item Processing signals: O(max_signal_number)
+Sending involves a syscall I<iff> there were no other C<ev_async_send>
+calls in the current loop iteration. Checking for async and signal events
+involves iterating over all running async watchers or all signal numbers.
 =back
 =head1 Win32 platform limitations and workarounds

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines