… | |
… | |
505 | =item ev_loop_fork (loop) |
505 | =item ev_loop_fork (loop) |
506 | |
506 | |
507 | Like C<ev_default_fork>, but acts on an event loop created by |
507 | Like C<ev_default_fork>, but acts on an event loop created by |
508 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
508 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
509 | after fork, and how you do this is entirely your own problem. |
509 | after fork, and how you do this is entirely your own problem. |
|
|
510 | |
|
|
511 | =item int ev_is_default_loop (loop) |
|
|
512 | |
|
|
513 | Returns true when the given loop actually is the default loop, false otherwise. |
510 | |
514 | |
511 | =item unsigned int ev_loop_count (loop) |
515 | =item unsigned int ev_loop_count (loop) |
512 | |
516 | |
513 | Returns the count of loop iterations for the loop, which is identical to |
517 | Returns the count of loop iterations for the loop, which is identical to |
514 | the number of times libev did poll for new events. It starts at C<0> and |
518 | the number of times libev did poll for new events. It starts at C<0> and |
… | |
… | |
774 | =item C<EV_FORK> |
778 | =item C<EV_FORK> |
775 | |
779 | |
776 | The event loop has been resumed in the child process after fork (see |
780 | The event loop has been resumed in the child process after fork (see |
777 | C<ev_fork>). |
781 | C<ev_fork>). |
778 | |
782 | |
|
|
783 | =item C<EV_ASYNC> |
|
|
784 | |
|
|
785 | The given async watcher has been asynchronously notified (see C<ev_async>). |
|
|
786 | |
779 | =item C<EV_ERROR> |
787 | =item C<EV_ERROR> |
780 | |
788 | |
781 | An unspecified error has occured, the watcher has been stopped. This might |
789 | An unspecified error has occured, the watcher has been stopped. This might |
782 | happen because the watcher could not be properly started because libev |
790 | happen because the watcher could not be properly started because libev |
783 | ran out of memory, a file descriptor was found to be closed or any other |
791 | ran out of memory, a file descriptor was found to be closed or any other |
… | |
… | |
1148 | configure a timer to trigger every 10 seconds, then it will trigger at |
1156 | configure a timer to trigger every 10 seconds, then it will trigger at |
1149 | exactly 10 second intervals. If, however, your program cannot keep up with |
1157 | exactly 10 second intervals. If, however, your program cannot keep up with |
1150 | the timer (because it takes longer than those 10 seconds to do stuff) the |
1158 | the timer (because it takes longer than those 10 seconds to do stuff) the |
1151 | timer will not fire more than once per event loop iteration. |
1159 | timer will not fire more than once per event loop iteration. |
1152 | |
1160 | |
1153 | =item ev_timer_again (loop) |
1161 | =item ev_timer_again (loop, ev_timer *) |
1154 | |
1162 | |
1155 | This will act as if the timer timed out and restart it again if it is |
1163 | This will act as if the timer timed out and restart it again if it is |
1156 | repeating. The exact semantics are: |
1164 | repeating. The exact semantics are: |
1157 | |
1165 | |
1158 | If the timer is pending, its pending status is cleared. |
1166 | If the timer is pending, its pending status is cleared. |
… | |
… | |
1267 | In this configuration the watcher triggers an event at the wallclock time |
1275 | In this configuration the watcher triggers an event at the wallclock time |
1268 | C<at> and doesn't repeat. It will not adjust when a time jump occurs, |
1276 | C<at> and doesn't repeat. It will not adjust when a time jump occurs, |
1269 | that is, if it is to be run at January 1st 2011 then it will run when the |
1277 | that is, if it is to be run at January 1st 2011 then it will run when the |
1270 | system time reaches or surpasses this time. |
1278 | system time reaches or surpasses this time. |
1271 | |
1279 | |
1272 | =item * non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1280 | =item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1273 | |
1281 | |
1274 | In this mode the watcher will always be scheduled to time out at the next |
1282 | In this mode the watcher will always be scheduled to time out at the next |
1275 | C<at + N * interval> time (for some integer N, which can also be negative) |
1283 | C<at + N * interval> time (for some integer N, which can also be negative) |
1276 | and then repeat, regardless of any time jumps. |
1284 | and then repeat, regardless of any time jumps. |
1277 | |
1285 | |
… | |
… | |
1428 | |
1436 | |
1429 | The signal the watcher watches out for. |
1437 | The signal the watcher watches out for. |
1430 | |
1438 | |
1431 | =back |
1439 | =back |
1432 | |
1440 | |
|
|
1441 | =head3 Examples |
|
|
1442 | |
|
|
1443 | Example: Try to exit cleanly on SIGINT and SIGTERM. |
|
|
1444 | |
|
|
1445 | static void |
|
|
1446 | sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) |
|
|
1447 | { |
|
|
1448 | ev_unloop (loop, EVUNLOOP_ALL); |
|
|
1449 | } |
|
|
1450 | |
|
|
1451 | struct ev_signal signal_watcher; |
|
|
1452 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
|
|
1453 | ev_signal_start (loop, &sigint_cb); |
|
|
1454 | |
1433 | |
1455 | |
1434 | =head2 C<ev_child> - watch out for process status changes |
1456 | =head2 C<ev_child> - watch out for process status changes |
1435 | |
1457 | |
1436 | Child watchers trigger when your process receives a SIGCHLD in response to |
1458 | Child watchers trigger when your process receives a SIGCHLD in response to |
1437 | some child status changes (most typically when a child of yours dies). |
1459 | some child status changes (most typically when a child of yours dies). |
1438 | |
1460 | |
1439 | =head3 Watcher-Specific Functions and Data Members |
1461 | =head3 Watcher-Specific Functions and Data Members |
1440 | |
1462 | |
1441 | =over 4 |
1463 | =over 4 |
1442 | |
1464 | |
1443 | =item ev_child_init (ev_child *, callback, int pid) |
1465 | =item ev_child_init (ev_child *, callback, int pid, int trace) |
1444 | |
1466 | |
1445 | =item ev_child_set (ev_child *, int pid) |
1467 | =item ev_child_set (ev_child *, int pid, int trace) |
1446 | |
1468 | |
1447 | Configures the watcher to wait for status changes of process C<pid> (or |
1469 | Configures the watcher to wait for status changes of process C<pid> (or |
1448 | I<any> process if C<pid> is specified as C<0>). The callback can look |
1470 | I<any> process if C<pid> is specified as C<0>). The callback can look |
1449 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
1471 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
1450 | the status word (use the macros from C<sys/wait.h> and see your systems |
1472 | the status word (use the macros from C<sys/wait.h> and see your systems |
1451 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
1473 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
1452 | process causing the status change. |
1474 | process causing the status change. C<trace> must be either C<0> (only |
|
|
1475 | activate the watcher when the process terminates) or C<1> (additionally |
|
|
1476 | activate the watcher when the process is stopped or continued). |
1453 | |
1477 | |
1454 | =item int pid [read-only] |
1478 | =item int pid [read-only] |
1455 | |
1479 | |
1456 | The process id this watcher watches out for, or C<0>, meaning any process id. |
1480 | The process id this watcher watches out for, or C<0>, meaning any process id. |
1457 | |
1481 | |
… | |
… | |
1463 | |
1487 | |
1464 | The process exit/trace status caused by C<rpid> (see your systems |
1488 | The process exit/trace status caused by C<rpid> (see your systems |
1465 | C<waitpid> and C<sys/wait.h> documentation for details). |
1489 | C<waitpid> and C<sys/wait.h> documentation for details). |
1466 | |
1490 | |
1467 | =back |
1491 | =back |
1468 | |
|
|
1469 | =head3 Examples |
|
|
1470 | |
|
|
1471 | Example: Try to exit cleanly on SIGINT and SIGTERM. |
|
|
1472 | |
|
|
1473 | static void |
|
|
1474 | sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) |
|
|
1475 | { |
|
|
1476 | ev_unloop (loop, EVUNLOOP_ALL); |
|
|
1477 | } |
|
|
1478 | |
|
|
1479 | struct ev_signal signal_watcher; |
|
|
1480 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
|
|
1481 | ev_signal_start (loop, &sigint_cb); |
|
|
1482 | |
1492 | |
1483 | |
1493 | |
1484 | =head2 C<ev_stat> - did the file attributes just change? |
1494 | =head2 C<ev_stat> - did the file attributes just change? |
1485 | |
1495 | |
1486 | This watches a filesystem path for attribute changes. That is, it calls |
1496 | This watches a filesystem path for attribute changes. That is, it calls |
… | |
… | |
1566 | |
1576 | |
1567 | The callback will be receive C<EV_STAT> when a change was detected, |
1577 | The callback will be receive C<EV_STAT> when a change was detected, |
1568 | relative to the attributes at the time the watcher was started (or the |
1578 | relative to the attributes at the time the watcher was started (or the |
1569 | last change was detected). |
1579 | last change was detected). |
1570 | |
1580 | |
1571 | =item ev_stat_stat (ev_stat *) |
1581 | =item ev_stat_stat (loop, ev_stat *) |
1572 | |
1582 | |
1573 | Updates the stat buffer immediately with new values. If you change the |
1583 | Updates the stat buffer immediately with new values. If you change the |
1574 | watched path in your callback, you could call this fucntion to avoid |
1584 | watched path in your callback, you could call this fucntion to avoid |
1575 | detecting this change (while introducing a race condition). Can also be |
1585 | detecting this change (while introducing a race condition). Can also be |
1576 | useful simply to find out the new values. |
1586 | useful simply to find out the new values. |
… | |
… | |
1693 | static void |
1703 | static void |
1694 | idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) |
1704 | idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) |
1695 | { |
1705 | { |
1696 | free (w); |
1706 | free (w); |
1697 | // now do something you wanted to do when the program has |
1707 | // now do something you wanted to do when the program has |
1698 | // no longer asnything immediate to do. |
1708 | // no longer anything immediate to do. |
1699 | } |
1709 | } |
1700 | |
1710 | |
1701 | struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1711 | struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1702 | ev_idle_init (idle_watcher, idle_cb); |
1712 | ev_idle_init (idle_watcher, idle_cb); |
1703 | ev_idle_start (loop, idle_cb); |
1713 | ev_idle_start (loop, idle_cb); |
… | |
… | |
2044 | believe me. |
2054 | believe me. |
2045 | |
2055 | |
2046 | =back |
2056 | =back |
2047 | |
2057 | |
2048 | |
2058 | |
|
|
2059 | =head2 C<ev_async> - how to wake up another event loop |
|
|
2060 | |
|
|
2061 | In general, you cannot use an C<ev_loop> from multiple threads or other |
|
|
2062 | asynchronous sources such as signal handlers (as opposed to multiple event |
|
|
2063 | loops - those are of course safe to use in different threads). |
|
|
2064 | |
|
|
2065 | Sometimes, however, you need to wake up another event loop you do not |
|
|
2066 | control, for example because it belongs to another thread. This is what |
|
|
2067 | C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you |
|
|
2068 | can signal it by calling C<ev_async_send>, which is thread- and signal |
|
|
2069 | safe. |
|
|
2070 | |
|
|
2071 | This functionality is very similar to C<ev_signal> watchers, as signals, |
|
|
2072 | too, are asynchronous in nature, and signals, too, will be compressed |
|
|
2073 | (i.e. the number of callback invocations may be less than the number of |
|
|
2074 | C<ev_async_sent> calls). |
|
|
2075 | |
|
|
2076 | Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not |
|
|
2077 | just the default loop. |
|
|
2078 | |
|
|
2079 | =head3 Queueing |
|
|
2080 | |
|
|
2081 | C<ev_async> does not support queueing of data in any way. The reason |
|
|
2082 | is that the author does not know of a simple (or any) algorithm for a |
|
|
2083 | multiple-writer-single-reader queue that works in all cases and doesn't |
|
|
2084 | need elaborate support such as pthreads. |
|
|
2085 | |
|
|
2086 | That means that if you want to queue data, you have to provide your own |
|
|
2087 | queue. But at least I can tell you would implement locking around your |
|
|
2088 | queue: |
|
|
2089 | |
|
|
2090 | =over 4 |
|
|
2091 | |
|
|
2092 | =item queueing from a signal handler context |
|
|
2093 | |
|
|
2094 | To implement race-free queueing, you simply add to the queue in the signal |
|
|
2095 | handler but you block the signal handler in the watcher callback. Here is an example that does that for |
|
|
2096 | some fictitiuous SIGUSR1 handler: |
|
|
2097 | |
|
|
2098 | static ev_async mysig; |
|
|
2099 | |
|
|
2100 | static void |
|
|
2101 | sigusr1_handler (void) |
|
|
2102 | { |
|
|
2103 | sometype data; |
|
|
2104 | |
|
|
2105 | // no locking etc. |
|
|
2106 | queue_put (data); |
|
|
2107 | ev_async_send (DEFAULT_ &mysig); |
|
|
2108 | } |
|
|
2109 | |
|
|
2110 | static void |
|
|
2111 | mysig_cb (EV_P_ ev_async *w, int revents) |
|
|
2112 | { |
|
|
2113 | sometype data; |
|
|
2114 | sigset_t block, prev; |
|
|
2115 | |
|
|
2116 | sigemptyset (&block); |
|
|
2117 | sigaddset (&block, SIGUSR1); |
|
|
2118 | sigprocmask (SIG_BLOCK, &block, &prev); |
|
|
2119 | |
|
|
2120 | while (queue_get (&data)) |
|
|
2121 | process (data); |
|
|
2122 | |
|
|
2123 | if (sigismember (&prev, SIGUSR1) |
|
|
2124 | sigprocmask (SIG_UNBLOCK, &block, 0); |
|
|
2125 | } |
|
|
2126 | |
|
|
2127 | (Note: pthreads in theory requires you to use C<pthread_setmask> |
|
|
2128 | instead of C<sigprocmask> when you use threads, but libev doesn't do it |
|
|
2129 | either...). |
|
|
2130 | |
|
|
2131 | =item queueing from a thread context |
|
|
2132 | |
|
|
2133 | The strategy for threads is different, as you cannot (easily) block |
|
|
2134 | threads but you can easily preempt them, so to queue safely you need to |
|
|
2135 | employ a traditional mutex lock, such as in this pthread example: |
|
|
2136 | |
|
|
2137 | static ev_async mysig; |
|
|
2138 | static pthread_mutex_t mymutex = PTHREAD_MUTEX_INITIALIZER; |
|
|
2139 | |
|
|
2140 | static void |
|
|
2141 | otherthread (void) |
|
|
2142 | { |
|
|
2143 | // only need to lock the actual queueing operation |
|
|
2144 | pthread_mutex_lock (&mymutex); |
|
|
2145 | queue_put (data); |
|
|
2146 | pthread_mutex_unlock (&mymutex); |
|
|
2147 | |
|
|
2148 | ev_async_send (DEFAULT_ &mysig); |
|
|
2149 | } |
|
|
2150 | |
|
|
2151 | static void |
|
|
2152 | mysig_cb (EV_P_ ev_async *w, int revents) |
|
|
2153 | { |
|
|
2154 | pthread_mutex_lock (&mymutex); |
|
|
2155 | |
|
|
2156 | while (queue_get (&data)) |
|
|
2157 | process (data); |
|
|
2158 | |
|
|
2159 | pthread_mutex_unlock (&mymutex); |
|
|
2160 | } |
|
|
2161 | |
|
|
2162 | =back |
|
|
2163 | |
|
|
2164 | |
|
|
2165 | =head3 Watcher-Specific Functions and Data Members |
|
|
2166 | |
|
|
2167 | =over 4 |
|
|
2168 | |
|
|
2169 | =item ev_async_init (ev_async *, callback) |
|
|
2170 | |
|
|
2171 | Initialises and configures the async watcher - it has no parameters of any |
|
|
2172 | kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless, |
|
|
2173 | believe me. |
|
|
2174 | |
|
|
2175 | =item ev_async_send (loop, ev_async *) |
|
|
2176 | |
|
|
2177 | Sends/signals/activates the given C<ev_async> watcher, that is, feeds |
|
|
2178 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
|
|
2179 | C<ev_feed_event>, this call is safe to do in other threads, signal or |
|
|
2180 | similar contexts (see the dicusssion of C<EV_ATOMIC_T> in the embedding |
|
|
2181 | section below on what exactly this means). |
|
|
2182 | |
|
|
2183 | This call incurs the overhead of a syscall only once per loop iteration, |
|
|
2184 | so while the overhead might be noticable, it doesn't apply to repeated |
|
|
2185 | calls to C<ev_async_send>. |
|
|
2186 | |
|
|
2187 | =back |
|
|
2188 | |
|
|
2189 | |
2049 | =head1 OTHER FUNCTIONS |
2190 | =head1 OTHER FUNCTIONS |
2050 | |
2191 | |
2051 | There are some other functions of possible interest. Described. Here. Now. |
2192 | There are some other functions of possible interest. Described. Here. Now. |
2052 | |
2193 | |
2053 | =over 4 |
2194 | =over 4 |
… | |
… | |
2280 | Example: Define a class with an IO and idle watcher, start one of them in |
2421 | Example: Define a class with an IO and idle watcher, start one of them in |
2281 | the constructor. |
2422 | the constructor. |
2282 | |
2423 | |
2283 | class myclass |
2424 | class myclass |
2284 | { |
2425 | { |
2285 | ev_io io; void io_cb (ev::io &w, int revents); |
2426 | ev::io io; void io_cb (ev::io &w, int revents); |
2286 | ev_idle idle void idle_cb (ev::idle &w, int revents); |
2427 | ev:idle idle void idle_cb (ev::idle &w, int revents); |
2287 | |
2428 | |
2288 | myclass (); |
2429 | myclass (int fd) |
2289 | } |
|
|
2290 | |
|
|
2291 | myclass::myclass (int fd) |
|
|
2292 | { |
2430 | { |
2293 | io .set <myclass, &myclass::io_cb > (this); |
2431 | io .set <myclass, &myclass::io_cb > (this); |
2294 | idle.set <myclass, &myclass::idle_cb> (this); |
2432 | idle.set <myclass, &myclass::idle_cb> (this); |
2295 | |
2433 | |
2296 | io.start (fd, ev::READ); |
2434 | io.start (fd, ev::READ); |
|
|
2435 | } |
2297 | } |
2436 | }; |
2298 | |
2437 | |
2299 | |
2438 | |
2300 | =head1 MACRO MAGIC |
2439 | =head1 MACRO MAGIC |
2301 | |
2440 | |
2302 | Libev can be compiled with a variety of options, the most fundamantal |
2441 | Libev can be compiled with a variety of options, the most fundamantal |
… | |
… | |
2558 | |
2697 | |
2559 | If defined to be C<1>, libev will compile in support for the Linux inotify |
2698 | If defined to be C<1>, libev will compile in support for the Linux inotify |
2560 | interface to speed up C<ev_stat> watchers. Its actual availability will |
2699 | interface to speed up C<ev_stat> watchers. Its actual availability will |
2561 | be detected at runtime. |
2700 | be detected at runtime. |
2562 | |
2701 | |
|
|
2702 | =item EV_ATOMIC_T |
|
|
2703 | |
|
|
2704 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
|
|
2705 | access is atomic with respect to other threads or signal contexts. No such |
|
|
2706 | type is easily found in the C language, so you can provide your own type |
|
|
2707 | that you know is safe for your purposes. It is used both for signal handler "locking" |
|
|
2708 | as well as for signal and thread safety in C<ev_async> watchers. |
|
|
2709 | |
|
|
2710 | In the absense of this define, libev will use C<sig_atomic_t volatile> |
|
|
2711 | (from F<signal.h>), which is usually good enough on most platforms. |
|
|
2712 | |
2563 | =item EV_H |
2713 | =item EV_H |
2564 | |
2714 | |
2565 | The name of the F<ev.h> header file used to include it. The default if |
2715 | The name of the F<ev.h> header file used to include it. The default if |
2566 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
2716 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
2567 | used to virtually rename the F<ev.h> header file in case of conflicts. |
2717 | used to virtually rename the F<ev.h> header file in case of conflicts. |
… | |
… | |
2632 | defined to be C<0>, then they are not. |
2782 | defined to be C<0>, then they are not. |
2633 | |
2783 | |
2634 | =item EV_FORK_ENABLE |
2784 | =item EV_FORK_ENABLE |
2635 | |
2785 | |
2636 | If undefined or defined to be C<1>, then fork watchers are supported. If |
2786 | If undefined or defined to be C<1>, then fork watchers are supported. If |
|
|
2787 | defined to be C<0>, then they are not. |
|
|
2788 | |
|
|
2789 | =item EV_ASYNC_ENABLE |
|
|
2790 | |
|
|
2791 | If undefined or defined to be C<1>, then async watchers are supported. If |
2637 | defined to be C<0>, then they are not. |
2792 | defined to be C<0>, then they are not. |
2638 | |
2793 | |
2639 | =item EV_MINIMAL |
2794 | =item EV_MINIMAL |
2640 | |
2795 | |
2641 | If you need to shave off some kilobytes of code at the expense of some |
2796 | If you need to shave off some kilobytes of code at the expense of some |
… | |
… | |
2762 | =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers) |
2917 | =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers) |
2763 | |
2918 | |
2764 | That means that changing a timer costs less than removing/adding them |
2919 | That means that changing a timer costs less than removing/adding them |
2765 | as only the relative motion in the event queue has to be paid for. |
2920 | as only the relative motion in the event queue has to be paid for. |
2766 | |
2921 | |
2767 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
2922 | =item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1) |
2768 | |
2923 | |
2769 | These just add the watcher into an array or at the head of a list. |
2924 | These just add the watcher into an array or at the head of a list. |
2770 | |
2925 | |
2771 | =item Stopping check/prepare/idle watchers: O(1) |
2926 | =item Stopping check/prepare/idle/fork/async watchers: O(1) |
2772 | |
2927 | |
2773 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
2928 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
2774 | |
2929 | |
2775 | These watchers are stored in lists then need to be walked to find the |
2930 | These watchers are stored in lists then need to be walked to find the |
2776 | correct watcher to remove. The lists are usually short (you don't usually |
2931 | correct watcher to remove. The lists are usually short (you don't usually |
… | |
… | |
2792 | =item Priority handling: O(number_of_priorities) |
2947 | =item Priority handling: O(number_of_priorities) |
2793 | |
2948 | |
2794 | Priorities are implemented by allocating some space for each |
2949 | Priorities are implemented by allocating some space for each |
2795 | priority. When doing priority-based operations, libev usually has to |
2950 | priority. When doing priority-based operations, libev usually has to |
2796 | linearly search all the priorities, but starting/stopping and activating |
2951 | linearly search all the priorities, but starting/stopping and activating |
2797 | watchers becomes O(1) w.r.t. prioritiy handling. |
2952 | watchers becomes O(1) w.r.t. priority handling. |
|
|
2953 | |
|
|
2954 | =item Sending an ev_async: O(1) |
|
|
2955 | |
|
|
2956 | =item Processing ev_async_send: O(number_of_async_watchers) |
|
|
2957 | |
|
|
2958 | =item Processing signals: O(max_signal_number) |
|
|
2959 | |
|
|
2960 | Sending involves a syscall I<iff> there were no other C<ev_async_send> |
|
|
2961 | calls in the current loop iteration. Checking for async and signal events |
|
|
2962 | involves iterating over all running async watchers or all signal numbers. |
2798 | |
2963 | |
2799 | =back |
2964 | =back |
2800 | |
2965 | |
2801 | |
2966 | |
2802 | =head1 Win32 platform limitations and workarounds |
2967 | =head1 Win32 platform limitations and workarounds |