diff options
author | root <root> | 2008-02-06 18:34:24 +0000 |
---|---|---|
committer | root <root> | 2008-02-06 18:34:24 +0000 |
commit | bee0323ee42a59ad3d8494412b081ea09d10319e (patch) | |
tree | 405d2a5586f531d40772d4e82bb97c5c5e5bc526 /ev.pod | |
parent | a82219690a0ce1703abdc9bf10d0d4e5a9d26efa (diff) |
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r-- | ev.pod | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -2080,7 +2080,8 @@ 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 @@ -2127,7 +2128,7 @@ either...). 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; |