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

Comparing libev/ev.pod (file contents):
Revision 1.128 by root, Fri Feb 1 13:53:56 2008 UTC vs.
Revision 1.130 by root, Wed Feb 6 18:34:24 2008 UTC

 is that the author does not know of a simple (or any) algorithm for a
 multiple-writer-single-reader queue that works in all cases and doesn't
 need elaborate support such as pthreads.
 That means that if you want to queue data, you have to provide your own
-queue. And here is how you would implement locking:
+queue. But at least I can tell you would implement locking around your
+queue:
 =over 4
 =item queueing from a signal handler context
 =item queueing from a thread context
 The strategy for threads is different, as you cannot (easily) block
 threads but you can easily preempt them, so to queue safely you need to
-emply a traditional mutex lock, such as in this pthread example:
+employ a traditional mutex lock, such as in this pthread example:
    static ev_async mysig;
    static pthread_mutex_t mymutex = PTHREAD_MUTEX_INITIALIZER;
    static void
 =item Priority handling: O(number_of_priorities)
 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.
+watchers becomes O(1) w.r.t. priority handling.
 =item Sending an ev_async: O(1)
 =item Processing ev_async_send: O(number_of_async_watchers)

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