|
|
1 | =encoding utf-8 |
|
|
2 | |
1 | =head1 NAME |
3 | =head1 NAME |
2 | |
4 | |
3 | libev - a high performance full-featured event loop written in C |
5 | libev - a high performance full-featured event loop written in C |
4 | |
6 | |
5 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
… | |
… | |
82 | |
84 | |
83 | =head1 WHAT TO READ WHEN IN A HURRY |
85 | =head1 WHAT TO READ WHEN IN A HURRY |
84 | |
86 | |
85 | This manual tries to be very detailed, but unfortunately, this also makes |
87 | This manual tries to be very detailed, but unfortunately, this also makes |
86 | it very long. If you just want to know the basics of libev, I suggest |
88 | it very long. If you just want to know the basics of libev, I suggest |
87 | reading L<ANATOMY OF A WATCHER>, then the L<EXAMPLE PROGRAM> above and |
89 | reading L</ANATOMY OF A WATCHER>, then the L</EXAMPLE PROGRAM> above and |
88 | look up the missing functions in L<GLOBAL FUNCTIONS> and the C<ev_io> and |
90 | look up the missing functions in L</GLOBAL FUNCTIONS> and the C<ev_io> and |
89 | C<ev_timer> sections in L<WATCHER TYPES>. |
91 | C<ev_timer> sections in L</WATCHER TYPES>. |
90 | |
92 | |
91 | =head1 ABOUT LIBEV |
93 | =head1 ABOUT LIBEV |
92 | |
94 | |
93 | Libev is an event loop: you register interest in certain events (such as a |
95 | Libev is an event loop: you register interest in certain events (such as a |
94 | file descriptor being readable or a timeout occurring), and it will manage |
96 | file descriptor being readable or a timeout occurring), and it will manage |
… | |
… | |
396 | |
398 | |
397 | If this flag bit is or'ed into the flag value (or the program runs setuid |
399 | If this flag bit is or'ed into the flag value (or the program runs setuid |
398 | or setgid) then libev will I<not> look at the environment variable |
400 | or setgid) then libev will I<not> look at the environment variable |
399 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
401 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
400 | override the flags completely if it is found in the environment. This is |
402 | override the flags completely if it is found in the environment. This is |
401 | useful to try out specific backends to test their performance, or to work |
403 | useful to try out specific backends to test their performance, to work |
402 | around bugs. |
404 | around bugs, or to make libev threadsafe (accessing environment variables |
|
|
405 | cannot be done in a threadsafe way, but usually it works if no other |
|
|
406 | thread modifies them). |
403 | |
407 | |
404 | =item C<EVFLAG_FORKCHECK> |
408 | =item C<EVFLAG_FORKCHECK> |
405 | |
409 | |
406 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
410 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
407 | make libev check for a fork in each iteration by enabling this flag. |
411 | make libev check for a fork in each iteration by enabling this flag. |
… | |
… | |
569 | kernel is more efficient (which says nothing about its actual speed, of |
573 | kernel is more efficient (which says nothing about its actual speed, of |
570 | course). While stopping, setting and starting an I/O watcher does never |
574 | course). While stopping, setting and starting an I/O watcher does never |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
575 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
572 | two event changes per incident. Support for C<fork ()> is very bad (you |
576 | two event changes per incident. Support for C<fork ()> is very bad (you |
573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
577 | might have to leak fd's on fork, but it's more sane than epoll) and it |
574 | drops fds silently in similarly hard-to-detect cases |
578 | drops fds silently in similarly hard-to-detect cases. |
575 | |
579 | |
576 | This backend usually performs well under most conditions. |
580 | This backend usually performs well under most conditions. |
577 | |
581 | |
578 | While nominally embeddable in other event loops, this doesn't work |
582 | While nominally embeddable in other event loops, this doesn't work |
579 | everywhere, so you might need to test for this. And since it is broken |
583 | everywhere, so you might need to test for this. And since it is broken |
… | |
… | |
678 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
682 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
679 | and C<ev_loop_destroy>. |
683 | and C<ev_loop_destroy>. |
680 | |
684 | |
681 | =item ev_loop_fork (loop) |
685 | =item ev_loop_fork (loop) |
682 | |
686 | |
683 | This function sets a flag that causes subsequent C<ev_run> iterations to |
687 | This function sets a flag that causes subsequent C<ev_run> iterations |
684 | reinitialise the kernel state for backends that have one. Despite the |
688 | to reinitialise the kernel state for backends that have one. Despite |
685 | name, you can call it anytime, but it makes most sense after forking, in |
689 | the name, you can call it anytime you are allowed to start or stop |
686 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
690 | watchers (except inside an C<ev_prepare> callback), but it makes most |
|
|
691 | sense after forking, in the child process. You I<must> call it (or use |
687 | child before resuming or calling C<ev_run>. |
692 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
688 | |
693 | |
689 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
694 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
690 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
695 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
691 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
696 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
692 | during fork. |
697 | during fork. |
693 | |
698 | |
694 | On the other hand, you only need to call this function in the child |
699 | On the other hand, you only need to call this function in the child |
… | |
… | |
764 | |
769 | |
765 | This function is rarely useful, but when some event callback runs for a |
770 | This function is rarely useful, but when some event callback runs for a |
766 | very long time without entering the event loop, updating libev's idea of |
771 | very long time without entering the event loop, updating libev's idea of |
767 | the current time is a good idea. |
772 | the current time is a good idea. |
768 | |
773 | |
769 | See also L<The special problem of time updates> in the C<ev_timer> section. |
774 | See also L</The special problem of time updates> in the C<ev_timer> section. |
770 | |
775 | |
771 | =item ev_suspend (loop) |
776 | =item ev_suspend (loop) |
772 | |
777 | |
773 | =item ev_resume (loop) |
778 | =item ev_resume (loop) |
774 | |
779 | |
… | |
… | |
1174 | |
1179 | |
1175 | =item C<EV_PREPARE> |
1180 | =item C<EV_PREPARE> |
1176 | |
1181 | |
1177 | =item C<EV_CHECK> |
1182 | =item C<EV_CHECK> |
1178 | |
1183 | |
1179 | All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts |
1184 | All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts to |
1180 | to gather new events, and all C<ev_check> watchers are invoked just after |
1185 | gather new events, and all C<ev_check> watchers are queued (not invoked) |
1181 | C<ev_run> has gathered them, but before it invokes any callbacks for any |
1186 | just after C<ev_run> has gathered them, but before it queues any callbacks |
|
|
1187 | for any received events. That means C<ev_prepare> watchers are the last |
|
|
1188 | watchers invoked before the event loop sleeps or polls for new events, and |
|
|
1189 | C<ev_check> watchers will be invoked before any other watchers of the same |
|
|
1190 | or lower priority within an event loop iteration. |
|
|
1191 | |
1182 | received events. Callbacks of both watcher types can start and stop as |
1192 | Callbacks of both watcher types can start and stop as many watchers as |
1183 | many watchers as they want, and all of them will be taken into account |
1193 | they want, and all of them will be taken into account (for example, a |
1184 | (for example, a C<ev_prepare> watcher might start an idle watcher to keep |
1194 | C<ev_prepare> watcher might start an idle watcher to keep C<ev_run> from |
1185 | C<ev_run> from blocking). |
1195 | blocking). |
1186 | |
1196 | |
1187 | =item C<EV_EMBED> |
1197 | =item C<EV_EMBED> |
1188 | |
1198 | |
1189 | The embedded event loop specified in the C<ev_embed> watcher needs attention. |
1199 | The embedded event loop specified in the C<ev_embed> watcher needs attention. |
1190 | |
1200 | |
… | |
… | |
1313 | |
1323 | |
1314 | =item callback ev_cb (ev_TYPE *watcher) |
1324 | =item callback ev_cb (ev_TYPE *watcher) |
1315 | |
1325 | |
1316 | Returns the callback currently set on the watcher. |
1326 | Returns the callback currently set on the watcher. |
1317 | |
1327 | |
1318 | =item ev_cb_set (ev_TYPE *watcher, callback) |
1328 | =item ev_set_cb (ev_TYPE *watcher, callback) |
1319 | |
1329 | |
1320 | Change the callback. You can change the callback at virtually any time |
1330 | Change the callback. You can change the callback at virtually any time |
1321 | (modulo threads). |
1331 | (modulo threads). |
1322 | |
1332 | |
1323 | =item ev_set_priority (ev_TYPE *watcher, int priority) |
1333 | =item ev_set_priority (ev_TYPE *watcher, int priority) |
… | |
… | |
1341 | or might not have been clamped to the valid range. |
1351 | or might not have been clamped to the valid range. |
1342 | |
1352 | |
1343 | The default priority used by watchers when no priority has been set is |
1353 | The default priority used by watchers when no priority has been set is |
1344 | always C<0>, which is supposed to not be too high and not be too low :). |
1354 | always C<0>, which is supposed to not be too high and not be too low :). |
1345 | |
1355 | |
1346 | See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of |
1356 | See L</WATCHER PRIORITY MODELS>, below, for a more thorough treatment of |
1347 | priorities. |
1357 | priorities. |
1348 | |
1358 | |
1349 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1359 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1350 | |
1360 | |
1351 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
1361 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
… | |
… | |
1376 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
1386 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
1377 | functions that do not need a watcher. |
1387 | functions that do not need a watcher. |
1378 | |
1388 | |
1379 | =back |
1389 | =back |
1380 | |
1390 | |
1381 | See also the L<ASSOCIATING CUSTOM DATA WITH A WATCHER> and L<BUILDING YOUR |
1391 | See also the L</ASSOCIATING CUSTOM DATA WITH A WATCHER> and L</BUILDING YOUR |
1382 | OWN COMPOSITE WATCHERS> idioms. |
1392 | OWN COMPOSITE WATCHERS> idioms. |
1383 | |
1393 | |
1384 | =head2 WATCHER STATES |
1394 | =head2 WATCHER STATES |
1385 | |
1395 | |
1386 | There are various watcher states mentioned throughout this manual - |
1396 | There are various watcher states mentioned throughout this manual - |
… | |
… | |
1388 | transition between them will be described in more detail - and while these |
1398 | transition between them will be described in more detail - and while these |
1389 | rules might look complicated, they usually do "the right thing". |
1399 | rules might look complicated, they usually do "the right thing". |
1390 | |
1400 | |
1391 | =over 4 |
1401 | =over 4 |
1392 | |
1402 | |
1393 | =item initialiased |
1403 | =item initialised |
1394 | |
1404 | |
1395 | Before a watcher can be registered with the event loop it has to be |
1405 | Before a watcher can be registered with the event loop it has to be |
1396 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
1406 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
1397 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
1407 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
1398 | |
1408 | |
… | |
… | |
1874 | callback (EV_P_ ev_timer *w, int revents) |
1884 | callback (EV_P_ ev_timer *w, int revents) |
1875 | { |
1885 | { |
1876 | // calculate when the timeout would happen |
1886 | // calculate when the timeout would happen |
1877 | ev_tstamp after = last_activity - ev_now (EV_A) + timeout; |
1887 | ev_tstamp after = last_activity - ev_now (EV_A) + timeout; |
1878 | |
1888 | |
1879 | // if negative, it means we the timeout already occured |
1889 | // if negative, it means we the timeout already occurred |
1880 | if (after < 0.) |
1890 | if (after < 0.) |
1881 | { |
1891 | { |
1882 | // timeout occurred, take action |
1892 | // timeout occurred, take action |
1883 | } |
1893 | } |
1884 | else |
1894 | else |
… | |
… | |
1902 | |
1912 | |
1903 | Otherwise, we now the earliest time at which the timeout would trigger, |
1913 | Otherwise, we now the earliest time at which the timeout would trigger, |
1904 | and simply start the timer with this timeout value. |
1914 | and simply start the timer with this timeout value. |
1905 | |
1915 | |
1906 | In other words, each time the callback is invoked it will check whether |
1916 | In other words, each time the callback is invoked it will check whether |
1907 | the timeout cocured. If not, it will simply reschedule itself to check |
1917 | the timeout occurred. If not, it will simply reschedule itself to check |
1908 | again at the earliest time it could time out. Rinse. Repeat. |
1918 | again at the earliest time it could time out. Rinse. Repeat. |
1909 | |
1919 | |
1910 | This scheme causes more callback invocations (about one every 60 seconds |
1920 | This scheme causes more callback invocations (about one every 60 seconds |
1911 | minus half the average time between activity), but virtually no calls to |
1921 | minus half the average time between activity), but virtually no calls to |
1912 | libev to change the timeout. |
1922 | libev to change the timeout. |
… | |
… | |
1926 | if (activity detected) |
1936 | if (activity detected) |
1927 | last_activity = ev_now (EV_A); |
1937 | last_activity = ev_now (EV_A); |
1928 | |
1938 | |
1929 | When your timeout value changes, then the timeout can be changed by simply |
1939 | When your timeout value changes, then the timeout can be changed by simply |
1930 | providing a new value, stopping the timer and calling the callback, which |
1940 | providing a new value, stopping the timer and calling the callback, which |
1931 | will agaion do the right thing (for example, time out immediately :). |
1941 | will again do the right thing (for example, time out immediately :). |
1932 | |
1942 | |
1933 | timeout = new_value; |
1943 | timeout = new_value; |
1934 | ev_timer_stop (EV_A_ &timer); |
1944 | ev_timer_stop (EV_A_ &timer); |
1935 | callback (EV_A_ &timer, 0); |
1945 | callback (EV_A_ &timer, 0); |
1936 | |
1946 | |
… | |
… | |
2131 | =item If the timer is repeating, make the C<repeat> value the new timeout |
2141 | =item If the timer is repeating, make the C<repeat> value the new timeout |
2132 | and start the timer, if necessary. |
2142 | and start the timer, if necessary. |
2133 | |
2143 | |
2134 | =back |
2144 | =back |
2135 | |
2145 | |
2136 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
2146 | This sounds a bit complicated, see L</Be smart about timeouts>, above, for a |
2137 | usage example. |
2147 | usage example. |
2138 | |
2148 | |
2139 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
2149 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
2140 | |
2150 | |
2141 | Returns the remaining time until a timer fires. If the timer is active, |
2151 | Returns the remaining time until a timer fires. If the timer is active, |
… | |
… | |
2384 | |
2394 | |
2385 | ev_periodic hourly_tick; |
2395 | ev_periodic hourly_tick; |
2386 | ev_periodic_init (&hourly_tick, clock_cb, |
2396 | ev_periodic_init (&hourly_tick, clock_cb, |
2387 | fmod (ev_now (loop), 3600.), 3600., 0); |
2397 | fmod (ev_now (loop), 3600.), 3600., 0); |
2388 | ev_periodic_start (loop, &hourly_tick); |
2398 | ev_periodic_start (loop, &hourly_tick); |
2389 | |
2399 | |
2390 | |
2400 | |
2391 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2401 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2392 | |
2402 | |
2393 | Signal watchers will trigger an event when the process receives a specific |
2403 | Signal watchers will trigger an event when the process receives a specific |
2394 | signal one or more times. Even though signals are very asynchronous, libev |
2404 | signal one or more times. Even though signals are very asynchronous, libev |
… | |
… | |
2404 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2414 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2405 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2415 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2406 | C<SIGINT> in both the default loop and another loop at the same time. At |
2416 | C<SIGINT> in both the default loop and another loop at the same time. At |
2407 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2417 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2408 | |
2418 | |
2409 | When the first watcher gets started will libev actually register something |
2419 | Only after the first watcher for a signal is started will libev actually |
2410 | with the kernel (thus it coexists with your own signal handlers as long as |
2420 | register something with the kernel. It thus coexists with your own signal |
2411 | you don't register any with libev for the same signal). |
2421 | handlers as long as you don't register any with libev for the same signal. |
2412 | |
2422 | |
2413 | If possible and supported, libev will install its handlers with |
2423 | If possible and supported, libev will install its handlers with |
2414 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2424 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2415 | not be unduly interrupted. If you have a problem with system calls getting |
2425 | not be unduly interrupted. If you have a problem with system calls getting |
2416 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2426 | interrupted by signals you can block all signals in an C<ev_check> watcher |
… | |
… | |
2601 | |
2611 | |
2602 | =head2 C<ev_stat> - did the file attributes just change? |
2612 | =head2 C<ev_stat> - did the file attributes just change? |
2603 | |
2613 | |
2604 | This watches a file system path for attribute changes. That is, it calls |
2614 | This watches a file system path for attribute changes. That is, it calls |
2605 | C<stat> on that path in regular intervals (or when the OS says it changed) |
2615 | C<stat> on that path in regular intervals (or when the OS says it changed) |
2606 | and sees if it changed compared to the last time, invoking the callback if |
2616 | and sees if it changed compared to the last time, invoking the callback |
2607 | it did. |
2617 | if it did. Starting the watcher C<stat>'s the file, so only changes that |
|
|
2618 | happen after the watcher has been started will be reported. |
2608 | |
2619 | |
2609 | The path does not need to exist: changing from "path exists" to "path does |
2620 | The path does not need to exist: changing from "path exists" to "path does |
2610 | not exist" is a status change like any other. The condition "path does not |
2621 | not exist" is a status change like any other. The condition "path does not |
2611 | exist" (or more correctly "path cannot be stat'ed") is signified by the |
2622 | exist" (or more correctly "path cannot be stat'ed") is signified by the |
2612 | C<st_nlink> field being zero (which is otherwise always forced to be at |
2623 | C<st_nlink> field being zero (which is otherwise always forced to be at |
… | |
… | |
2842 | Apart from keeping your process non-blocking (which is a useful |
2853 | Apart from keeping your process non-blocking (which is a useful |
2843 | effect on its own sometimes), idle watchers are a good place to do |
2854 | effect on its own sometimes), idle watchers are a good place to do |
2844 | "pseudo-background processing", or delay processing stuff to after the |
2855 | "pseudo-background processing", or delay processing stuff to after the |
2845 | event loop has handled all outstanding events. |
2856 | event loop has handled all outstanding events. |
2846 | |
2857 | |
|
|
2858 | =head3 Abusing an C<ev_idle> watcher for its side-effect |
|
|
2859 | |
|
|
2860 | As long as there is at least one active idle watcher, libev will never |
|
|
2861 | sleep unnecessarily. Or in other words, it will loop as fast as possible. |
|
|
2862 | For this to work, the idle watcher doesn't need to be invoked at all - the |
|
|
2863 | lowest priority will do. |
|
|
2864 | |
|
|
2865 | This mode of operation can be useful together with an C<ev_check> watcher, |
|
|
2866 | to do something on each event loop iteration - for example to balance load |
|
|
2867 | between different connections. |
|
|
2868 | |
|
|
2869 | See L</Abusing an ev_check watcher for its side-effect> for a longer |
|
|
2870 | example. |
|
|
2871 | |
2847 | =head3 Watcher-Specific Functions and Data Members |
2872 | =head3 Watcher-Specific Functions and Data Members |
2848 | |
2873 | |
2849 | =over 4 |
2874 | =over 4 |
2850 | |
2875 | |
2851 | =item ev_idle_init (ev_idle *, callback) |
2876 | =item ev_idle_init (ev_idle *, callback) |
… | |
… | |
2862 | callback, free it. Also, use no error checking, as usual. |
2887 | callback, free it. Also, use no error checking, as usual. |
2863 | |
2888 | |
2864 | static void |
2889 | static void |
2865 | idle_cb (struct ev_loop *loop, ev_idle *w, int revents) |
2890 | idle_cb (struct ev_loop *loop, ev_idle *w, int revents) |
2866 | { |
2891 | { |
|
|
2892 | // stop the watcher |
|
|
2893 | ev_idle_stop (loop, w); |
|
|
2894 | |
|
|
2895 | // now we can free it |
2867 | free (w); |
2896 | free (w); |
|
|
2897 | |
2868 | // now do something you wanted to do when the program has |
2898 | // now do something you wanted to do when the program has |
2869 | // no longer anything immediate to do. |
2899 | // no longer anything immediate to do. |
2870 | } |
2900 | } |
2871 | |
2901 | |
2872 | ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
2902 | ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
… | |
… | |
2874 | ev_idle_start (loop, idle_watcher); |
2904 | ev_idle_start (loop, idle_watcher); |
2875 | |
2905 | |
2876 | |
2906 | |
2877 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
2907 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
2878 | |
2908 | |
2879 | Prepare and check watchers are usually (but not always) used in pairs: |
2909 | Prepare and check watchers are often (but not always) used in pairs: |
2880 | prepare watchers get invoked before the process blocks and check watchers |
2910 | prepare watchers get invoked before the process blocks and check watchers |
2881 | afterwards. |
2911 | afterwards. |
2882 | |
2912 | |
2883 | You I<must not> call C<ev_run> or similar functions that enter |
2913 | You I<must not> call C<ev_run> (or similar functions that enter the |
2884 | the current event loop from either C<ev_prepare> or C<ev_check> |
2914 | current event loop) or C<ev_loop_fork> from either C<ev_prepare> or |
2885 | watchers. Other loops than the current one are fine, however. The |
2915 | C<ev_check> watchers. Other loops than the current one are fine, |
2886 | rationale behind this is that you do not need to check for recursion in |
2916 | however. The rationale behind this is that you do not need to check |
2887 | those watchers, i.e. the sequence will always be C<ev_prepare>, blocking, |
2917 | for recursion in those watchers, i.e. the sequence will always be |
2888 | C<ev_check> so if you have one watcher of each kind they will always be |
2918 | C<ev_prepare>, blocking, C<ev_check> so if you have one watcher of each |
2889 | called in pairs bracketing the blocking call. |
2919 | kind they will always be called in pairs bracketing the blocking call. |
2890 | |
2920 | |
2891 | Their main purpose is to integrate other event mechanisms into libev and |
2921 | Their main purpose is to integrate other event mechanisms into libev and |
2892 | their use is somewhat advanced. They could be used, for example, to track |
2922 | their use is somewhat advanced. They could be used, for example, to track |
2893 | variable changes, implement your own watchers, integrate net-snmp or a |
2923 | variable changes, implement your own watchers, integrate net-snmp or a |
2894 | coroutine library and lots more. They are also occasionally useful if |
2924 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
2912 | with priority higher than or equal to the event loop and one coroutine |
2942 | with priority higher than or equal to the event loop and one coroutine |
2913 | of lower priority, but only once, using idle watchers to keep the event |
2943 | of lower priority, but only once, using idle watchers to keep the event |
2914 | loop from blocking if lower-priority coroutines are active, thus mapping |
2944 | loop from blocking if lower-priority coroutines are active, thus mapping |
2915 | low-priority coroutines to idle/background tasks). |
2945 | low-priority coroutines to idle/background tasks). |
2916 | |
2946 | |
2917 | It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>) |
2947 | When used for this purpose, it is recommended to give C<ev_check> watchers |
2918 | priority, to ensure that they are being run before any other watchers |
2948 | highest (C<EV_MAXPRI>) priority, to ensure that they are being run before |
2919 | after the poll (this doesn't matter for C<ev_prepare> watchers). |
2949 | any other watchers after the poll (this doesn't matter for C<ev_prepare> |
|
|
2950 | watchers). |
2920 | |
2951 | |
2921 | Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not |
2952 | Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not |
2922 | activate ("feed") events into libev. While libev fully supports this, they |
2953 | activate ("feed") events into libev. While libev fully supports this, they |
2923 | might get executed before other C<ev_check> watchers did their job. As |
2954 | might get executed before other C<ev_check> watchers did their job. As |
2924 | C<ev_check> watchers are often used to embed other (non-libev) event |
2955 | C<ev_check> watchers are often used to embed other (non-libev) event |
2925 | loops those other event loops might be in an unusable state until their |
2956 | loops those other event loops might be in an unusable state until their |
2926 | C<ev_check> watcher ran (always remind yourself to coexist peacefully with |
2957 | C<ev_check> watcher ran (always remind yourself to coexist peacefully with |
2927 | others). |
2958 | others). |
|
|
2959 | |
|
|
2960 | =head3 Abusing an C<ev_check> watcher for its side-effect |
|
|
2961 | |
|
|
2962 | C<ev_check> (and less often also C<ev_prepare>) watchers can also be |
|
|
2963 | useful because they are called once per event loop iteration. For |
|
|
2964 | example, if you want to handle a large number of connections fairly, you |
|
|
2965 | normally only do a bit of work for each active connection, and if there |
|
|
2966 | is more work to do, you wait for the next event loop iteration, so other |
|
|
2967 | connections have a chance of making progress. |
|
|
2968 | |
|
|
2969 | Using an C<ev_check> watcher is almost enough: it will be called on the |
|
|
2970 | next event loop iteration. However, that isn't as soon as possible - |
|
|
2971 | without external events, your C<ev_check> watcher will not be invoked. |
|
|
2972 | |
|
|
2973 | This is where C<ev_idle> watchers come in handy - all you need is a |
|
|
2974 | single global idle watcher that is active as long as you have one active |
|
|
2975 | C<ev_check> watcher. The C<ev_idle> watcher makes sure the event loop |
|
|
2976 | will not sleep, and the C<ev_check> watcher makes sure a callback gets |
|
|
2977 | invoked. Neither watcher alone can do that. |
2928 | |
2978 | |
2929 | =head3 Watcher-Specific Functions and Data Members |
2979 | =head3 Watcher-Specific Functions and Data Members |
2930 | |
2980 | |
2931 | =over 4 |
2981 | =over 4 |
2932 | |
2982 | |
… | |
… | |
3133 | |
3183 | |
3134 | =over 4 |
3184 | =over 4 |
3135 | |
3185 | |
3136 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop) |
3186 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop) |
3137 | |
3187 | |
3138 | =item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop) |
3188 | =item ev_embed_set (ev_embed *, struct ev_loop *embedded_loop) |
3139 | |
3189 | |
3140 | Configures the watcher to embed the given loop, which must be |
3190 | Configures the watcher to embed the given loop, which must be |
3141 | embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be |
3191 | embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be |
3142 | invoked automatically, otherwise it is the responsibility of the callback |
3192 | invoked automatically, otherwise it is the responsibility of the callback |
3143 | to invoke it (it will continue to be called until the sweep has been done, |
3193 | to invoke it (it will continue to be called until the sweep has been done, |
… | |
… | |
3164 | used). |
3214 | used). |
3165 | |
3215 | |
3166 | struct ev_loop *loop_hi = ev_default_init (0); |
3216 | struct ev_loop *loop_hi = ev_default_init (0); |
3167 | struct ev_loop *loop_lo = 0; |
3217 | struct ev_loop *loop_lo = 0; |
3168 | ev_embed embed; |
3218 | ev_embed embed; |
3169 | |
3219 | |
3170 | // see if there is a chance of getting one that works |
3220 | // see if there is a chance of getting one that works |
3171 | // (remember that a flags value of 0 means autodetection) |
3221 | // (remember that a flags value of 0 means autodetection) |
3172 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3222 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3173 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3223 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3174 | : 0; |
3224 | : 0; |
… | |
… | |
3188 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3238 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3189 | |
3239 | |
3190 | struct ev_loop *loop = ev_default_init (0); |
3240 | struct ev_loop *loop = ev_default_init (0); |
3191 | struct ev_loop *loop_socket = 0; |
3241 | struct ev_loop *loop_socket = 0; |
3192 | ev_embed embed; |
3242 | ev_embed embed; |
3193 | |
3243 | |
3194 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3244 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3195 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3245 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3196 | { |
3246 | { |
3197 | ev_embed_init (&embed, 0, loop_socket); |
3247 | ev_embed_init (&embed, 0, loop_socket); |
3198 | ev_embed_start (loop, &embed); |
3248 | ev_embed_start (loop, &embed); |
… | |
… | |
3206 | |
3256 | |
3207 | =head2 C<ev_fork> - the audacity to resume the event loop after a fork |
3257 | =head2 C<ev_fork> - the audacity to resume the event loop after a fork |
3208 | |
3258 | |
3209 | Fork watchers are called when a C<fork ()> was detected (usually because |
3259 | Fork watchers are called when a C<fork ()> was detected (usually because |
3210 | whoever is a good citizen cared to tell libev about it by calling |
3260 | whoever is a good citizen cared to tell libev about it by calling |
3211 | C<ev_default_fork> or C<ev_loop_fork>). The invocation is done before the |
3261 | C<ev_loop_fork>). The invocation is done before the event loop blocks next |
3212 | event loop blocks next and before C<ev_check> watchers are being called, |
3262 | and before C<ev_check> watchers are being called, and only in the child |
3213 | and only in the child after the fork. If whoever good citizen calling |
3263 | after the fork. If whoever good citizen calling C<ev_default_fork> cheats |
3214 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
3264 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3215 | handlers will be invoked, too, of course. |
3265 | of course. |
3216 | |
3266 | |
3217 | =head3 The special problem of life after fork - how is it possible? |
3267 | =head3 The special problem of life after fork - how is it possible? |
3218 | |
3268 | |
3219 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3269 | Most uses of C<fork ()> consist of forking, then some simple calls to set |
3220 | up/change the process environment, followed by a call to C<exec()>. This |
3270 | up/change the process environment, followed by a call to C<exec()>. This |
3221 | sequence should be handled by libev without any problems. |
3271 | sequence should be handled by libev without any problems. |
3222 | |
3272 | |
3223 | This changes when the application actually wants to do event handling |
3273 | This changes when the application actually wants to do event handling |
3224 | in the child, or both parent in child, in effect "continuing" after the |
3274 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3313 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3363 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3314 | |
3364 | |
3315 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3365 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3316 | too, are asynchronous in nature, and signals, too, will be compressed |
3366 | too, are asynchronous in nature, and signals, too, will be compressed |
3317 | (i.e. the number of callback invocations may be less than the number of |
3367 | (i.e. the number of callback invocations may be less than the number of |
3318 | C<ev_async_sent> calls). In fact, you could use signal watchers as a kind |
3368 | C<ev_async_send> calls). In fact, you could use signal watchers as a kind |
3319 | of "global async watchers" by using a watcher on an otherwise unused |
3369 | of "global async watchers" by using a watcher on an otherwise unused |
3320 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3370 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3321 | even without knowing which loop owns the signal. |
3371 | even without knowing which loop owns the signal. |
3322 | |
3372 | |
3323 | =head3 Queueing |
3373 | =head3 Queueing |
… | |
… | |
3614 | already been invoked. |
3664 | already been invoked. |
3615 | |
3665 | |
3616 | A common way around all these issues is to make sure that |
3666 | A common way around all these issues is to make sure that |
3617 | C<start_new_request> I<always> returns before the callback is invoked. If |
3667 | C<start_new_request> I<always> returns before the callback is invoked. If |
3618 | C<start_new_request> immediately knows the result, it can artificially |
3668 | C<start_new_request> immediately knows the result, it can artificially |
3619 | delay invoking the callback by e.g. using a C<prepare> or C<idle> watcher |
3669 | delay invoking the callback by using a C<prepare> or C<idle> watcher for |
3620 | for example, or more sneakily, by reusing an existing (stopped) watcher |
3670 | example, or more sneakily, by reusing an existing (stopped) watcher and |
3621 | and pushing it into the pending queue: |
3671 | pushing it into the pending queue: |
3622 | |
3672 | |
3623 | ev_set_cb (watcher, callback); |
3673 | ev_set_cb (watcher, callback); |
3624 | ev_feed_event (EV_A_ watcher, 0); |
3674 | ev_feed_event (EV_A_ watcher, 0); |
3625 | |
3675 | |
3626 | This way, C<start_new_request> can safely return before the callback is |
3676 | This way, C<start_new_request> can safely return before the callback is |
… | |
… | |
3634 | |
3684 | |
3635 | This brings the problem of exiting - a callback might want to finish the |
3685 | This brings the problem of exiting - a callback might want to finish the |
3636 | main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but |
3686 | main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but |
3637 | a modal "Are you sure?" dialog is still waiting), or just the nested one |
3687 | a modal "Are you sure?" dialog is still waiting), or just the nested one |
3638 | and not the main one (e.g. user clocked "Ok" in a modal dialog), or some |
3688 | and not the main one (e.g. user clocked "Ok" in a modal dialog), or some |
3639 | other combination: In these cases, C<ev_break> will not work alone. |
3689 | other combination: In these cases, a simple C<ev_break> will not work. |
3640 | |
3690 | |
3641 | The solution is to maintain "break this loop" variable for each C<ev_run> |
3691 | The solution is to maintain "break this loop" variable for each C<ev_run> |
3642 | invocation, and use a loop around C<ev_run> until the condition is |
3692 | invocation, and use a loop around C<ev_run> until the condition is |
3643 | triggered, using C<EVRUN_ONCE>: |
3693 | triggered, using C<EVRUN_ONCE>: |
3644 | |
3694 | |
… | |
… | |
3830 | called): |
3880 | called): |
3831 | |
3881 | |
3832 | void |
3882 | void |
3833 | wait_for_event (ev_watcher *w) |
3883 | wait_for_event (ev_watcher *w) |
3834 | { |
3884 | { |
3835 | ev_cb_set (w) = current_coro; |
3885 | ev_set_cb (w, current_coro); |
3836 | switch_to (libev_coro); |
3886 | switch_to (libev_coro); |
3837 | } |
3887 | } |
3838 | |
3888 | |
3839 | That basically suspends the coroutine inside C<wait_for_event> and |
3889 | That basically suspends the coroutine inside C<wait_for_event> and |
3840 | continues the libev coroutine, which, when appropriate, switches back to |
3890 | continues the libev coroutine, which, when appropriate, switches back to |
… | |
… | |
3843 | You can do similar tricks if you have, say, threads with an event queue - |
3893 | You can do similar tricks if you have, say, threads with an event queue - |
3844 | instead of storing a coroutine, you store the queue object and instead of |
3894 | instead of storing a coroutine, you store the queue object and instead of |
3845 | switching to a coroutine, you push the watcher onto the queue and notify |
3895 | switching to a coroutine, you push the watcher onto the queue and notify |
3846 | any waiters. |
3896 | any waiters. |
3847 | |
3897 | |
3848 | To embed libev, see L<EMBEDDING>, but in short, it's easiest to create two |
3898 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3849 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3899 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3850 | |
3900 | |
3851 | // my_ev.h |
3901 | // my_ev.h |
3852 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3902 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3853 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
3903 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
… | |
… | |
3905 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3955 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3906 | will work fine. |
3956 | will work fine. |
3907 | |
3957 | |
3908 | Proper exception specifications might have to be added to callbacks passed |
3958 | Proper exception specifications might have to be added to callbacks passed |
3909 | to libev: exceptions may be thrown only from watcher callbacks, all |
3959 | to libev: exceptions may be thrown only from watcher callbacks, all |
3910 | other callbacks (allocator, syserr, loop acquire/release and periodioc |
3960 | other callbacks (allocator, syserr, loop acquire/release and periodic |
3911 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
3961 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
3912 | ()> specification. If you have code that needs to be compiled as both C |
3962 | ()> specification. If you have code that needs to be compiled as both C |
3913 | and C++ you can use the C<EV_THROW> macro for this: |
3963 | and C++ you can use the C<EV_THROW> macro for this: |
3914 | |
3964 | |
3915 | static void |
3965 | static void |
… | |
… | |
3921 | |
3971 | |
3922 | ... |
3972 | ... |
3923 | ev_set_syserr_cb (fatal_error); |
3973 | ev_set_syserr_cb (fatal_error); |
3924 | |
3974 | |
3925 | The only API functions that can currently throw exceptions are C<ev_run>, |
3975 | The only API functions that can currently throw exceptions are C<ev_run>, |
3926 | C<ev_inoke> and C<ev_invoke_pending>. |
3976 | C<ev_invoke>, C<ev_invoke_pending> and C<ev_loop_destroy> (the latter |
|
|
3977 | because it runs cleanup watchers). |
3927 | |
3978 | |
3928 | Throwing exceptions in watcher callbacks is only supported if libev itself |
3979 | Throwing exceptions in watcher callbacks is only supported if libev itself |
3929 | is compiled with a C++ compiler or your C and C++ environments allow |
3980 | is compiled with a C++ compiler or your C and C++ environments allow |
3930 | throwing exceptions through C libraries (most do). |
3981 | throwing exceptions through C libraries (most do). |
3931 | |
3982 | |
… | |
… | |
3934 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3985 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3935 | you to use some convenience methods to start/stop watchers and also change |
3986 | you to use some convenience methods to start/stop watchers and also change |
3936 | the callback model to a model using method callbacks on objects. |
3987 | the callback model to a model using method callbacks on objects. |
3937 | |
3988 | |
3938 | To use it, |
3989 | To use it, |
3939 | |
3990 | |
3940 | #include <ev++.h> |
3991 | #include <ev++.h> |
3941 | |
3992 | |
3942 | This automatically includes F<ev.h> and puts all of its definitions (many |
3993 | This automatically includes F<ev.h> and puts all of its definitions (many |
3943 | of them macros) into the global namespace. All C++ specific things are |
3994 | of them macros) into the global namespace. All C++ specific things are |
3944 | put into the C<ev> namespace. It should support all the same embedding |
3995 | put into the C<ev> namespace. It should support all the same embedding |
… | |
… | |
4047 | void operator() (ev::io &w, int revents) |
4098 | void operator() (ev::io &w, int revents) |
4048 | { |
4099 | { |
4049 | ... |
4100 | ... |
4050 | } |
4101 | } |
4051 | } |
4102 | } |
4052 | |
4103 | |
4053 | myfunctor f; |
4104 | myfunctor f; |
4054 | |
4105 | |
4055 | ev::io w; |
4106 | ev::io w; |
4056 | w.set (&f); |
4107 | w.set (&f); |
4057 | |
4108 | |
… | |
… | |
4075 | Associates a different C<struct ev_loop> with this watcher. You can only |
4126 | Associates a different C<struct ev_loop> with this watcher. You can only |
4076 | do this when the watcher is inactive (and not pending either). |
4127 | do this when the watcher is inactive (and not pending either). |
4077 | |
4128 | |
4078 | =item w->set ([arguments]) |
4129 | =item w->set ([arguments]) |
4079 | |
4130 | |
4080 | Basically the same as C<ev_TYPE_set>, with the same arguments. Either this |
4131 | Basically the same as C<ev_TYPE_set> (except for C<ev::embed> watchers>), |
4081 | method or a suitable start method must be called at least once. Unlike the |
4132 | with the same arguments. Either this method or a suitable start method |
4082 | C counterpart, an active watcher gets automatically stopped and restarted |
4133 | must be called at least once. Unlike the C counterpart, an active watcher |
4083 | when reconfiguring it with this method. |
4134 | gets automatically stopped and restarted when reconfiguring it with this |
|
|
4135 | method. |
|
|
4136 | |
|
|
4137 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
|
|
4138 | clashing with the C<set (loop)> method. |
4084 | |
4139 | |
4085 | =item w->start () |
4140 | =item w->start () |
4086 | |
4141 | |
4087 | Starts the watcher. Note that there is no C<loop> argument, as the |
4142 | Starts the watcher. Note that there is no C<loop> argument, as the |
4088 | constructor already stores the event loop. |
4143 | constructor already stores the event loop. |
… | |
… | |
4191 | =item Lua |
4246 | =item Lua |
4192 | |
4247 | |
4193 | Brian Maher has written a partial interface to libev for lua (at the |
4248 | Brian Maher has written a partial interface to libev for lua (at the |
4194 | time of this writing, only C<ev_io> and C<ev_timer>), to be found at |
4249 | time of this writing, only C<ev_io> and C<ev_timer>), to be found at |
4195 | L<http://github.com/brimworks/lua-ev>. |
4250 | L<http://github.com/brimworks/lua-ev>. |
|
|
4251 | |
|
|
4252 | =item Javascript |
|
|
4253 | |
|
|
4254 | Node.js (L<http://nodejs.org>) uses libev as the underlying event library. |
|
|
4255 | |
|
|
4256 | =item Others |
|
|
4257 | |
|
|
4258 | There are others, and I stopped counting. |
4196 | |
4259 | |
4197 | =back |
4260 | =back |
4198 | |
4261 | |
4199 | |
4262 | |
4200 | =head1 MACRO MAGIC |
4263 | =head1 MACRO MAGIC |
… | |
… | |
4499 | |
4562 | |
4500 | If programs implement their own fd to handle mapping on win32, then this |
4563 | If programs implement their own fd to handle mapping on win32, then this |
4501 | macro can be used to override the C<close> function, useful to unregister |
4564 | macro can be used to override the C<close> function, useful to unregister |
4502 | file descriptors again. Note that the replacement function has to close |
4565 | file descriptors again. Note that the replacement function has to close |
4503 | the underlying OS handle. |
4566 | the underlying OS handle. |
|
|
4567 | |
|
|
4568 | =item EV_USE_WSASOCKET |
|
|
4569 | |
|
|
4570 | If defined to be C<1>, libev will use C<WSASocket> to create its internal |
|
|
4571 | communication socket, which works better in some environments. Otherwise, |
|
|
4572 | the normal C<socket> function will be used, which works better in other |
|
|
4573 | environments. |
4504 | |
4574 | |
4505 | =item EV_USE_POLL |
4575 | =item EV_USE_POLL |
4506 | |
4576 | |
4507 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
4577 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
4508 | backend. Otherwise it will be enabled on non-win32 platforms. It |
4578 | backend. Otherwise it will be enabled on non-win32 platforms. It |
… | |
… | |
4553 | different cpus (or different cpu cores). This reduces dependencies |
4623 | different cpus (or different cpu cores). This reduces dependencies |
4554 | and makes libev faster. |
4624 | and makes libev faster. |
4555 | |
4625 | |
4556 | =item EV_NO_THREADS |
4626 | =item EV_NO_THREADS |
4557 | |
4627 | |
4558 | If defined to be C<1>, libev will assume that it will never be called |
4628 | If defined to be C<1>, libev will assume that it will never be called from |
4559 | from different threads, which is a stronger assumption than C<EV_NO_SMP>, |
4629 | different threads (that includes signal handlers), which is a stronger |
4560 | above. This reduces dependencies and makes libev faster. |
4630 | assumption than C<EV_NO_SMP>, above. This reduces dependencies and makes |
|
|
4631 | libev faster. |
4561 | |
4632 | |
4562 | =item EV_ATOMIC_T |
4633 | =item EV_ATOMIC_T |
4563 | |
4634 | |
4564 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4635 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4565 | access is atomic and serialised with respect to other threads or signal |
4636 | access is atomic with respect to other threads or signal contexts. No |
4566 | contexts. No such type is easily found in the C language, so you can |
4637 | such type is easily found in the C language, so you can provide your own |
4567 | provide your own type that you know is safe for your purposes. It is used |
4638 | type that you know is safe for your purposes. It is used both for signal |
4568 | both for signal handler "locking" as well as for signal and thread safety |
4639 | handler "locking" as well as for signal and thread safety in C<ev_async> |
4569 | in C<ev_async> watchers. |
4640 | watchers. |
4570 | |
4641 | |
4571 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
4642 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
4572 | (from F<signal.h>), which is usually good enough on most platforms, |
4643 | (from F<signal.h>), which is usually good enough on most platforms. |
4573 | although strictly speaking using a type that also implies a memory fence |
|
|
4574 | is required. |
|
|
4575 | |
4644 | |
4576 | =item EV_H (h) |
4645 | =item EV_H (h) |
4577 | |
4646 | |
4578 | The name of the F<ev.h> header file used to include it. The default if |
4647 | The name of the F<ev.h> header file used to include it. The default if |
4579 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
4648 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
… | |
… | |
4947 | default loop and triggering an C<ev_async> watcher from the default loop |
5016 | default loop and triggering an C<ev_async> watcher from the default loop |
4948 | watcher callback into the event loop interested in the signal. |
5017 | watcher callback into the event loop interested in the signal. |
4949 | |
5018 | |
4950 | =back |
5019 | =back |
4951 | |
5020 | |
4952 | See also L<THREAD LOCKING EXAMPLE>. |
5021 | See also L</THREAD LOCKING EXAMPLE>. |
4953 | |
5022 | |
4954 | =head3 COROUTINES |
5023 | =head3 COROUTINES |
4955 | |
5024 | |
4956 | Libev is very accommodating to coroutines ("cooperative threads"): |
5025 | Libev is very accommodating to coroutines ("cooperative threads"): |
4957 | libev fully supports nesting calls to its functions from different |
5026 | libev fully supports nesting calls to its functions from different |
… | |
… | |
5248 | thread" or will block signals process-wide, both behaviours would |
5317 | thread" or will block signals process-wide, both behaviours would |
5249 | be compatible with libev. Interaction between C<sigprocmask> and |
5318 | be compatible with libev. Interaction between C<sigprocmask> and |
5250 | C<pthread_sigmask> could complicate things, however. |
5319 | C<pthread_sigmask> could complicate things, however. |
5251 | |
5320 | |
5252 | The most portable way to handle signals is to block signals in all threads |
5321 | The most portable way to handle signals is to block signals in all threads |
5253 | except the initial one, and run the default loop in the initial thread as |
5322 | except the initial one, and run the signal handling loop in the initial |
5254 | well. |
5323 | thread as well. |
5255 | |
5324 | |
5256 | =item C<long> must be large enough for common memory allocation sizes |
5325 | =item C<long> must be large enough for common memory allocation sizes |
5257 | |
5326 | |
5258 | To improve portability and simplify its API, libev uses C<long> internally |
5327 | To improve portability and simplify its API, libev uses C<long> internally |
5259 | instead of C<size_t> when allocating its data structures. On non-POSIX |
5328 | instead of C<size_t> when allocating its data structures. On non-POSIX |
… | |
… | |
5363 | =over 4 |
5432 | =over 4 |
5364 | |
5433 | |
5365 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5434 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5366 | |
5435 | |
5367 | The backward compatibility mechanism can be controlled by |
5436 | The backward compatibility mechanism can be controlled by |
5368 | C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING> |
5437 | C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING> |
5369 | section. |
5438 | section. |
5370 | |
5439 | |
5371 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5440 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5372 | |
5441 | |
5373 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
5442 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
… | |
… | |
5416 | =over 4 |
5485 | =over 4 |
5417 | |
5486 | |
5418 | =item active |
5487 | =item active |
5419 | |
5488 | |
5420 | A watcher is active as long as it has been started and not yet stopped. |
5489 | A watcher is active as long as it has been started and not yet stopped. |
5421 | See L<WATCHER STATES> for details. |
5490 | See L</WATCHER STATES> for details. |
5422 | |
5491 | |
5423 | =item application |
5492 | =item application |
5424 | |
5493 | |
5425 | In this document, an application is whatever is using libev. |
5494 | In this document, an application is whatever is using libev. |
5426 | |
5495 | |
… | |
… | |
5462 | watchers and events. |
5531 | watchers and events. |
5463 | |
5532 | |
5464 | =item pending |
5533 | =item pending |
5465 | |
5534 | |
5466 | A watcher is pending as soon as the corresponding event has been |
5535 | A watcher is pending as soon as the corresponding event has been |
5467 | detected. See L<WATCHER STATES> for details. |
5536 | detected. See L</WATCHER STATES> for details. |
5468 | |
5537 | |
5469 | =item real time |
5538 | =item real time |
5470 | |
5539 | |
5471 | The physical time that is observed. It is apparently strictly monotonic :) |
5540 | The physical time that is observed. It is apparently strictly monotonic :) |
5472 | |
5541 | |