… | |
… | |
633 | This function is rarely useful, but when some event callback runs for a |
633 | This function is rarely useful, but when some event callback runs for a |
634 | very long time without entering the event loop, updating libev's idea of |
634 | very long time without entering the event loop, updating libev's idea of |
635 | the current time is a good idea. |
635 | the current time is a good idea. |
636 | |
636 | |
637 | See also "The special problem of time updates" in the C<ev_timer> section. |
637 | See also "The special problem of time updates" in the C<ev_timer> section. |
|
|
638 | |
|
|
639 | =item ev_suspend (loop) |
|
|
640 | |
|
|
641 | =item ev_resume (loop) |
|
|
642 | |
|
|
643 | These two functions suspend and resume a loop, for use when the loop is |
|
|
644 | not used for a while and timeouts should not be processed. |
|
|
645 | |
|
|
646 | A typical use case would be an interactive program such as a game: When |
|
|
647 | the user presses C<^Z> to suspend the game and resumes it an hour later it |
|
|
648 | would be best to handle timeouts as if no time had actually passed while |
|
|
649 | the program was suspended. This can be achieved by calling C<ev_suspend> |
|
|
650 | in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling |
|
|
651 | C<ev_resume> directly afterwards to resume timer processing. |
|
|
652 | |
|
|
653 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
|
|
654 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
|
|
655 | will be rescheduled (that is, they will lose any events that would have |
|
|
656 | occured while suspended). |
|
|
657 | |
|
|
658 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
|
|
659 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
|
|
660 | without a previous call to C<ev_suspend>. |
|
|
661 | |
|
|
662 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
|
|
663 | event loop time (see C<ev_now_update>). |
638 | |
664 | |
639 | =item ev_loop (loop, int flags) |
665 | =item ev_loop (loop, int flags) |
640 | |
666 | |
641 | Finally, this is it, the event handler. This function usually is called |
667 | Finally, this is it, the event handler. This function usually is called |
642 | after you initialised all your watchers and you want to start handling |
668 | after you initialised all your watchers and you want to start handling |
… | |
… | |
726 | |
752 | |
727 | If you have a watcher you never unregister that should not keep C<ev_loop> |
753 | If you have a watcher you never unregister that should not keep C<ev_loop> |
728 | from returning, call ev_unref() after starting, and ev_ref() before |
754 | from returning, call ev_unref() after starting, and ev_ref() before |
729 | stopping it. |
755 | stopping it. |
730 | |
756 | |
731 | As an example, libev itself uses this for its internal signal pipe: It is |
757 | As an example, libev itself uses this for its internal signal pipe: It |
732 | not visible to the libev user and should not keep C<ev_loop> from exiting |
758 | is not visible to the libev user and should not keep C<ev_loop> from |
733 | if no event watchers registered by it are active. It is also an excellent |
759 | exiting if no event watchers registered by it are active. It is also an |
734 | way to do this for generic recurring timers or from within third-party |
760 | excellent way to do this for generic recurring timers or from within |
735 | libraries. Just remember to I<unref after start> and I<ref before stop> |
761 | third-party libraries. Just remember to I<unref after start> and I<ref |
736 | (but only if the watcher wasn't active before, or was active before, |
762 | before stop> (but only if the watcher wasn't active before, or was active |
737 | respectively). |
763 | before, respectively. Note also that libev might stop watchers itself |
|
|
764 | (e.g. non-repeating timers) in which case you have to C<ev_ref> |
|
|
765 | in the callback). |
738 | |
766 | |
739 | Example: Create a signal watcher, but keep it from keeping C<ev_loop> |
767 | Example: Create a signal watcher, but keep it from keeping C<ev_loop> |
740 | running when nothing else is active. |
768 | running when nothing else is active. |
741 | |
769 | |
742 | ev_signal exitsig; |
770 | ev_signal exitsig; |
… | |
… | |
926 | |
954 | |
927 | =item C<EV_ASYNC> |
955 | =item C<EV_ASYNC> |
928 | |
956 | |
929 | The given async watcher has been asynchronously notified (see C<ev_async>). |
957 | The given async watcher has been asynchronously notified (see C<ev_async>). |
930 | |
958 | |
|
|
959 | =item C<EV_CUSTOM> |
|
|
960 | |
|
|
961 | Not ever sent (or otherwise used) by libev itself, but can be freely used |
|
|
962 | by libev users to signal watchers (e.g. via C<ev_feed_event>). |
|
|
963 | |
931 | =item C<EV_ERROR> |
964 | =item C<EV_ERROR> |
932 | |
965 | |
933 | An unspecified error has occurred, the watcher has been stopped. This might |
966 | An unspecified error has occurred, the watcher has been stopped. This might |
934 | happen because the watcher could not be properly started because libev |
967 | happen because the watcher could not be properly started because libev |
935 | ran out of memory, a file descriptor was found to be closed or any other |
968 | ran out of memory, a file descriptor was found to be closed or any other |
… | |
… | |
1050 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1083 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1051 | (default: C<-2>). Pending watchers with higher priority will be invoked |
1084 | (default: C<-2>). Pending watchers with higher priority will be invoked |
1052 | before watchers with lower priority, but priority will not keep watchers |
1085 | before watchers with lower priority, but priority will not keep watchers |
1053 | from being executed (except for C<ev_idle> watchers). |
1086 | from being executed (except for C<ev_idle> watchers). |
1054 | |
1087 | |
1055 | This means that priorities are I<only> used for ordering callback |
|
|
1056 | invocation after new events have been received. This is useful, for |
|
|
1057 | example, to reduce latency after idling, or more often, to bind two |
|
|
1058 | watchers on the same event and make sure one is called first. |
|
|
1059 | |
|
|
1060 | If you need to suppress invocation when higher priority events are pending |
1088 | If you need to suppress invocation when higher priority events are pending |
1061 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1089 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1062 | |
1090 | |
1063 | You I<must not> change the priority of a watcher as long as it is active or |
1091 | You I<must not> change the priority of a watcher as long as it is active or |
1064 | pending. |
1092 | pending. |
1065 | |
|
|
1066 | The default priority used by watchers when no priority has been set is |
|
|
1067 | always C<0>, which is supposed to not be too high and not be too low :). |
|
|
1068 | |
1093 | |
1069 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
1094 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
1070 | fine, as long as you do not mind that the priority value you query might |
1095 | fine, as long as you do not mind that the priority value you query might |
1071 | or might not have been clamped to the valid range. |
1096 | or might not have been clamped to the valid range. |
|
|
1097 | |
|
|
1098 | The default priority used by watchers when no priority has been set is |
|
|
1099 | always C<0>, which is supposed to not be too high and not be too low :). |
|
|
1100 | |
|
|
1101 | See L<WATCHER PRIORITIES>, below, for a more thorough treatment of |
|
|
1102 | priorities. |
1072 | |
1103 | |
1073 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1104 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1074 | |
1105 | |
1075 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
1106 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
1076 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
1107 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
… | |
… | |
1151 | t2_cb (EV_P_ ev_timer *w, int revents) |
1182 | t2_cb (EV_P_ ev_timer *w, int revents) |
1152 | { |
1183 | { |
1153 | struct my_biggy big = (struct my_biggy * |
1184 | struct my_biggy big = (struct my_biggy * |
1154 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1185 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1155 | } |
1186 | } |
|
|
1187 | |
|
|
1188 | =head2 WATCHER PRIORITY MODELS |
|
|
1189 | |
|
|
1190 | Many event loops support I<watcher priorities>, which are usually small |
|
|
1191 | integers that influence the ordering of event callback invocation |
|
|
1192 | between watchers in some way, all else being equal. |
|
|
1193 | |
|
|
1194 | In libev, Watcher priorities can be set using C<ev_set_priority>. See its |
|
|
1195 | description for the more technical details such as the actual priority |
|
|
1196 | range. |
|
|
1197 | |
|
|
1198 | There are two common ways how these these priorities are being interpreted |
|
|
1199 | by event loops: |
|
|
1200 | |
|
|
1201 | In the more common lock-out model, higher priorities "lock out" invocation |
|
|
1202 | of lower priority watchers, which means as long as higher priority |
|
|
1203 | watchers receive events, lower priority watchers are not being invoked. |
|
|
1204 | |
|
|
1205 | The less common only-for-ordering model uses priorities solely to order |
|
|
1206 | callback invocation within a single event loop iteration: Higher priority |
|
|
1207 | watchers are invoked before lower priority ones, but they all get invoked |
|
|
1208 | before polling for new events. |
|
|
1209 | |
|
|
1210 | Libev uses the second (only-for-ordering) model for all its watchers |
|
|
1211 | except for idle watchers (which use the lock-out model). |
|
|
1212 | |
|
|
1213 | The rationale behind this is that implementing the lock-out model for |
|
|
1214 | watchers is not well supported by most kernel interfaces, and most event |
|
|
1215 | libraries will just poll for the same events again and again as long as |
|
|
1216 | their callbacks have not been executed, which is very inefficient in the |
|
|
1217 | common case of one high-priority watcher locking out a mass of lower |
|
|
1218 | priority ones. |
|
|
1219 | |
|
|
1220 | Static (ordering) priorities are most useful when you have two or more |
|
|
1221 | watchers handling the same resource: a typical usage example is having an |
|
|
1222 | C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle |
|
|
1223 | timeouts. Under load, data might be received while the program handles |
|
|
1224 | other jobs, but since timers normally get invoked first, the timeout |
|
|
1225 | handler will be executed before checking for data. In that case, giving |
|
|
1226 | the timer a lower priority than the I/O watcher ensures that I/O will be |
|
|
1227 | handled first even under adverse conditions (which is usually, but not |
|
|
1228 | always, what you want). |
|
|
1229 | |
|
|
1230 | Since idle watchers use the "lock-out" model, meaning that idle watchers |
|
|
1231 | will only be executed when no same or higher priority watchers have |
|
|
1232 | received events, they can be used to implement the "lock-out" model when |
|
|
1233 | required. |
|
|
1234 | |
|
|
1235 | For example, to emulate how many other event libraries handle priorities, |
|
|
1236 | you can associate an C<ev_idle> watcher to each such watcher, and in |
|
|
1237 | the normal watcher callback, you just start the idle watcher. The real |
|
|
1238 | processing is done in the idle watcher callback. This causes libev to |
|
|
1239 | continously poll and process kernel event data for the watcher, but when |
|
|
1240 | the lock-out case is known to be rare (which in turn is rare :), this is |
|
|
1241 | workable. |
|
|
1242 | |
|
|
1243 | Usually, however, the lock-out model implemented that way will perform |
|
|
1244 | miserably under the type of load it was designed to handle. In that case, |
|
|
1245 | it might be preferable to stop the real watcher before starting the |
|
|
1246 | idle watcher, so the kernel will not have to process the event in case |
|
|
1247 | the actual processing will be delayed for considerable time. |
|
|
1248 | |
|
|
1249 | Here is an example of an I/O watcher that should run at a strictly lower |
|
|
1250 | priority than the default, and which should only process data when no |
|
|
1251 | other events are pending: |
|
|
1252 | |
|
|
1253 | ev_idle idle; // actual processing watcher |
|
|
1254 | ev_io io; // actual event watcher |
|
|
1255 | |
|
|
1256 | static void |
|
|
1257 | io_cb (EV_P_ ev_io *w, int revents) |
|
|
1258 | { |
|
|
1259 | // stop the I/O watcher, we received the event, but |
|
|
1260 | // are not yet ready to handle it. |
|
|
1261 | ev_io_stop (EV_A_ w); |
|
|
1262 | |
|
|
1263 | // start the idle watcher to ahndle the actual event. |
|
|
1264 | // it will not be executed as long as other watchers |
|
|
1265 | // with the default priority are receiving events. |
|
|
1266 | ev_idle_start (EV_A_ &idle); |
|
|
1267 | } |
|
|
1268 | |
|
|
1269 | static void |
|
|
1270 | idle-cb (EV_P_ ev_idle *w, int revents) |
|
|
1271 | { |
|
|
1272 | // actual processing |
|
|
1273 | read (STDIN_FILENO, ...); |
|
|
1274 | |
|
|
1275 | // have to start the I/O watcher again, as |
|
|
1276 | // we have handled the event |
|
|
1277 | ev_io_start (EV_P_ &io); |
|
|
1278 | } |
|
|
1279 | |
|
|
1280 | // initialisation |
|
|
1281 | ev_idle_init (&idle, idle_cb); |
|
|
1282 | ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ); |
|
|
1283 | ev_io_start (EV_DEFAULT_ &io); |
|
|
1284 | |
|
|
1285 | In the "real" world, it might also be beneficial to start a timer, so that |
|
|
1286 | low-priority connections can not be locked out forever under load. This |
|
|
1287 | enables your program to keep a lower latency for important connections |
|
|
1288 | during short periods of high load, while not completely locking out less |
|
|
1289 | important ones. |
1156 | |
1290 | |
1157 | |
1291 | |
1158 | =head1 WATCHER TYPES |
1292 | =head1 WATCHER TYPES |
1159 | |
1293 | |
1160 | This section describes each watcher in detail, but will not repeat |
1294 | This section describes each watcher in detail, but will not repeat |
… | |
… | |
1317 | year, it will still time out after (roughly) one hour. "Roughly" because |
1451 | year, it will still time out after (roughly) one hour. "Roughly" because |
1318 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1452 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1319 | monotonic clock option helps a lot here). |
1453 | monotonic clock option helps a lot here). |
1320 | |
1454 | |
1321 | The callback is guaranteed to be invoked only I<after> its timeout has |
1455 | The callback is guaranteed to be invoked only I<after> its timeout has |
1322 | passed, but if multiple timers become ready during the same loop iteration |
1456 | passed. If multiple timers become ready during the same loop iteration |
1323 | then order of execution is undefined. |
1457 | then the ones with earlier time-out values are invoked before ones with |
|
|
1458 | later time-out values (but this is no longer true when a callback calls |
|
|
1459 | C<ev_loop> recursively). |
1324 | |
1460 | |
1325 | =head3 Be smart about timeouts |
1461 | =head3 Be smart about timeouts |
1326 | |
1462 | |
1327 | Many real-world problems involve some kind of timeout, usually for error |
1463 | Many real-world problems involve some kind of timeout, usually for error |
1328 | recovery. A typical example is an HTTP request - if the other side hangs, |
1464 | recovery. A typical example is an HTTP request - if the other side hangs, |
… | |
… | |
1547 | If the timer is started but non-repeating, stop it (as if it timed out). |
1683 | If the timer is started but non-repeating, stop it (as if it timed out). |
1548 | |
1684 | |
1549 | If the timer is repeating, either start it if necessary (with the |
1685 | If the timer is repeating, either start it if necessary (with the |
1550 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1686 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1551 | |
1687 | |
1552 | This sounds a bit complicated, see "Be smart about timeouts", above, for a |
1688 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1553 | usage example. |
1689 | usage example. |
1554 | |
1690 | |
1555 | =item ev_tstamp repeat [read-write] |
1691 | =item ev_tstamp repeat [read-write] |
1556 | |
1692 | |
1557 | The current C<repeat> value. Will be used each time the watcher times out |
1693 | The current C<repeat> value. Will be used each time the watcher times out |
… | |
… | |
1596 | =head2 C<ev_periodic> - to cron or not to cron? |
1732 | =head2 C<ev_periodic> - to cron or not to cron? |
1597 | |
1733 | |
1598 | Periodic watchers are also timers of a kind, but they are very versatile |
1734 | Periodic watchers are also timers of a kind, but they are very versatile |
1599 | (and unfortunately a bit complex). |
1735 | (and unfortunately a bit complex). |
1600 | |
1736 | |
1601 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
1737 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
1602 | but on wall clock time (absolute time). You can tell a periodic watcher |
1738 | relative time, the physical time that passes) but on wall clock time |
1603 | to trigger after some specific point in time. For example, if you tell a |
1739 | (absolute time, the thing you can read on your calender or clock). The |
1604 | periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now () |
1740 | difference is that wall clock time can run faster or slower than real |
1605 | + 10.>, that is, an absolute time not a delay) and then reset your system |
1741 | time, and time jumps are not uncommon (e.g. when you adjust your |
1606 | clock to January of the previous year, then it will take more than year |
1742 | wrist-watch). |
1607 | to trigger the event (unlike an C<ev_timer>, which would still trigger |
|
|
1608 | roughly 10 seconds later as it uses a relative timeout). |
|
|
1609 | |
1743 | |
|
|
1744 | You can tell a periodic watcher to trigger after some specific point |
|
|
1745 | in time: for example, if you tell a periodic watcher to trigger "in 10 |
|
|
1746 | seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time |
|
|
1747 | not a delay) and then reset your system clock to January of the previous |
|
|
1748 | year, then it will take a year or more to trigger the event (unlike an |
|
|
1749 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
|
|
1750 | it, as it uses a relative timeout). |
|
|
1751 | |
1610 | C<ev_periodic>s can also be used to implement vastly more complex timers, |
1752 | C<ev_periodic> watchers can also be used to implement vastly more complex |
1611 | such as triggering an event on each "midnight, local time", or other |
1753 | timers, such as triggering an event on each "midnight, local time", or |
1612 | complicated rules. |
1754 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
|
|
1755 | those cannot react to time jumps. |
1613 | |
1756 | |
1614 | As with timers, the callback is guaranteed to be invoked only when the |
1757 | As with timers, the callback is guaranteed to be invoked only when the |
1615 | time (C<at>) has passed, but if multiple periodic timers become ready |
1758 | point in time where it is supposed to trigger has passed. If multiple |
1616 | during the same loop iteration, then order of execution is undefined. |
1759 | timers become ready during the same loop iteration then the ones with |
|
|
1760 | earlier time-out values are invoked before ones with later time-out values |
|
|
1761 | (but this is no longer true when a callback calls C<ev_loop> recursively). |
1617 | |
1762 | |
1618 | =head3 Watcher-Specific Functions and Data Members |
1763 | =head3 Watcher-Specific Functions and Data Members |
1619 | |
1764 | |
1620 | =over 4 |
1765 | =over 4 |
1621 | |
1766 | |
1622 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1767 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1623 | |
1768 | |
1624 | =item ev_periodic_set (ev_periodic *, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1769 | =item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1625 | |
1770 | |
1626 | Lots of arguments, lets sort it out... There are basically three modes of |
1771 | Lots of arguments, let's sort it out... There are basically three modes of |
1627 | operation, and we will explain them from simplest to most complex: |
1772 | operation, and we will explain them from simplest to most complex: |
1628 | |
1773 | |
1629 | =over 4 |
1774 | =over 4 |
1630 | |
1775 | |
1631 | =item * absolute timer (at = time, interval = reschedule_cb = 0) |
1776 | =item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0) |
1632 | |
1777 | |
1633 | In this configuration the watcher triggers an event after the wall clock |
1778 | In this configuration the watcher triggers an event after the wall clock |
1634 | time C<at> has passed. It will not repeat and will not adjust when a time |
1779 | time C<offset> has passed. It will not repeat and will not adjust when a |
1635 | jump occurs, that is, if it is to be run at January 1st 2011 then it will |
1780 | time jump occurs, that is, if it is to be run at January 1st 2011 then it |
1636 | only run when the system clock reaches or surpasses this time. |
1781 | will be stopped and invoked when the system clock reaches or surpasses |
|
|
1782 | this point in time. |
1637 | |
1783 | |
1638 | =item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1784 | =item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0) |
1639 | |
1785 | |
1640 | In this mode the watcher will always be scheduled to time out at the next |
1786 | In this mode the watcher will always be scheduled to time out at the next |
1641 | C<at + N * interval> time (for some integer N, which can also be negative) |
1787 | C<offset + N * interval> time (for some integer N, which can also be |
1642 | and then repeat, regardless of any time jumps. |
1788 | negative) and then repeat, regardless of any time jumps. The C<offset> |
|
|
1789 | argument is merely an offset into the C<interval> periods. |
1643 | |
1790 | |
1644 | This can be used to create timers that do not drift with respect to the |
1791 | This can be used to create timers that do not drift with respect to the |
1645 | system clock, for example, here is a C<ev_periodic> that triggers each |
1792 | system clock, for example, here is an C<ev_periodic> that triggers each |
1646 | hour, on the hour: |
1793 | hour, on the hour (with respect to UTC): |
1647 | |
1794 | |
1648 | ev_periodic_set (&periodic, 0., 3600., 0); |
1795 | ev_periodic_set (&periodic, 0., 3600., 0); |
1649 | |
1796 | |
1650 | This doesn't mean there will always be 3600 seconds in between triggers, |
1797 | This doesn't mean there will always be 3600 seconds in between triggers, |
1651 | but only that the callback will be called when the system time shows a |
1798 | but only that the callback will be called when the system time shows a |
1652 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1799 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1653 | by 3600. |
1800 | by 3600. |
1654 | |
1801 | |
1655 | Another way to think about it (for the mathematically inclined) is that |
1802 | Another way to think about it (for the mathematically inclined) is that |
1656 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1803 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1657 | time where C<time = at (mod interval)>, regardless of any time jumps. |
1804 | time where C<time = offset (mod interval)>, regardless of any time jumps. |
1658 | |
1805 | |
1659 | For numerical stability it is preferable that the C<at> value is near |
1806 | For numerical stability it is preferable that the C<offset> value is near |
1660 | C<ev_now ()> (the current time), but there is no range requirement for |
1807 | C<ev_now ()> (the current time), but there is no range requirement for |
1661 | this value, and in fact is often specified as zero. |
1808 | this value, and in fact is often specified as zero. |
1662 | |
1809 | |
1663 | Note also that there is an upper limit to how often a timer can fire (CPU |
1810 | Note also that there is an upper limit to how often a timer can fire (CPU |
1664 | speed for example), so if C<interval> is very small then timing stability |
1811 | speed for example), so if C<interval> is very small then timing stability |
1665 | will of course deteriorate. Libev itself tries to be exact to be about one |
1812 | will of course deteriorate. Libev itself tries to be exact to be about one |
1666 | millisecond (if the OS supports it and the machine is fast enough). |
1813 | millisecond (if the OS supports it and the machine is fast enough). |
1667 | |
1814 | |
1668 | =item * manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1815 | =item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback) |
1669 | |
1816 | |
1670 | In this mode the values for C<interval> and C<at> are both being |
1817 | In this mode the values for C<interval> and C<offset> are both being |
1671 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1818 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1672 | reschedule callback will be called with the watcher as first, and the |
1819 | reschedule callback will be called with the watcher as first, and the |
1673 | current time as second argument. |
1820 | current time as second argument. |
1674 | |
1821 | |
1675 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
1822 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever, |
1676 | ever, or make ANY other event loop modifications whatsoever>. |
1823 | or make ANY other event loop modifications whatsoever, unless explicitly |
|
|
1824 | allowed by documentation here>. |
1677 | |
1825 | |
1678 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1826 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1679 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1827 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1680 | only event loop modification you are allowed to do). |
1828 | only event loop modification you are allowed to do). |
1681 | |
1829 | |
… | |
… | |
1711 | a different time than the last time it was called (e.g. in a crond like |
1859 | a different time than the last time it was called (e.g. in a crond like |
1712 | program when the crontabs have changed). |
1860 | program when the crontabs have changed). |
1713 | |
1861 | |
1714 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1862 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1715 | |
1863 | |
1716 | When active, returns the absolute time that the watcher is supposed to |
1864 | When active, returns the absolute time that the watcher is supposed |
1717 | trigger next. |
1865 | to trigger next. This is not the same as the C<offset> argument to |
|
|
1866 | C<ev_periodic_set>, but indeed works even in interval and manual |
|
|
1867 | rescheduling modes. |
1718 | |
1868 | |
1719 | =item ev_tstamp offset [read-write] |
1869 | =item ev_tstamp offset [read-write] |
1720 | |
1870 | |
1721 | When repeating, this contains the offset value, otherwise this is the |
1871 | When repeating, this contains the offset value, otherwise this is the |
1722 | absolute point in time (the C<at> value passed to C<ev_periodic_set>). |
1872 | absolute point in time (the C<offset> value passed to C<ev_periodic_set>, |
|
|
1873 | although libev might modify this value for better numerical stability). |
1723 | |
1874 | |
1724 | Can be modified any time, but changes only take effect when the periodic |
1875 | Can be modified any time, but changes only take effect when the periodic |
1725 | timer fires or C<ev_periodic_again> is being called. |
1876 | timer fires or C<ev_periodic_again> is being called. |
1726 | |
1877 | |
1727 | =item ev_tstamp interval [read-write] |
1878 | =item ev_tstamp interval [read-write] |
… | |
… | |
2682 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2833 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2683 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2834 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2684 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2835 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2685 | section below on what exactly this means). |
2836 | section below on what exactly this means). |
2686 | |
2837 | |
|
|
2838 | Note that, as with other watchers in libev, multiple events might get |
|
|
2839 | compressed into a single callback invocation (another way to look at this |
|
|
2840 | is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>, |
|
|
2841 | reset when the event loop detects that). |
|
|
2842 | |
2687 | This call incurs the overhead of a system call only once per loop iteration, |
2843 | This call incurs the overhead of a system call only once per event loop |
2688 | so while the overhead might be noticeable, it doesn't apply to repeated |
2844 | iteration, so while the overhead might be noticeable, it doesn't apply to |
2689 | calls to C<ev_async_send>. |
2845 | repeated calls to C<ev_async_send> for the same event loop. |
2690 | |
2846 | |
2691 | =item bool = ev_async_pending (ev_async *) |
2847 | =item bool = ev_async_pending (ev_async *) |
2692 | |
2848 | |
2693 | Returns a non-zero value when C<ev_async_send> has been called on the |
2849 | Returns a non-zero value when C<ev_async_send> has been called on the |
2694 | watcher but the event has not yet been processed (or even noted) by the |
2850 | watcher but the event has not yet been processed (or even noted) by the |
… | |
… | |
2697 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2853 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2698 | the loop iterates next and checks for the watcher to have become active, |
2854 | the loop iterates next and checks for the watcher to have become active, |
2699 | it will reset the flag again. C<ev_async_pending> can be used to very |
2855 | it will reset the flag again. C<ev_async_pending> can be used to very |
2700 | quickly check whether invoking the loop might be a good idea. |
2856 | quickly check whether invoking the loop might be a good idea. |
2701 | |
2857 | |
2702 | Not that this does I<not> check whether the watcher itself is pending, only |
2858 | Not that this does I<not> check whether the watcher itself is pending, |
2703 | whether it has been requested to make this watcher pending. |
2859 | only whether it has been requested to make this watcher pending: there |
|
|
2860 | is a time window between the event loop checking and resetting the async |
|
|
2861 | notification, and the callback being invoked. |
2704 | |
2862 | |
2705 | =back |
2863 | =back |
2706 | |
2864 | |
2707 | |
2865 | |
2708 | =head1 OTHER FUNCTIONS |
2866 | =head1 OTHER FUNCTIONS |
… | |
… | |
3012 | L<http://software.schmorp.de/pkg/EV>. |
3170 | L<http://software.schmorp.de/pkg/EV>. |
3013 | |
3171 | |
3014 | =item Python |
3172 | =item Python |
3015 | |
3173 | |
3016 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
3174 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
3017 | seems to be quite complete and well-documented. Note, however, that the |
3175 | seems to be quite complete and well-documented. |
3018 | patch they require for libev is outright dangerous as it breaks the ABI |
|
|
3019 | for everybody else, and therefore, should never be applied in an installed |
|
|
3020 | libev (if python requires an incompatible ABI then it needs to embed |
|
|
3021 | libev). |
|
|
3022 | |
3176 | |
3023 | =item Ruby |
3177 | =item Ruby |
3024 | |
3178 | |
3025 | Tony Arcieri has written a ruby extension that offers access to a subset |
3179 | Tony Arcieri has written a ruby extension that offers access to a subset |
3026 | of the libev API and adds file handle abstractions, asynchronous DNS and |
3180 | of the libev API and adds file handle abstractions, asynchronous DNS and |
3027 | more on top of it. It can be found via gem servers. Its homepage is at |
3181 | more on top of it. It can be found via gem servers. Its homepage is at |
3028 | L<http://rev.rubyforge.org/>. |
3182 | L<http://rev.rubyforge.org/>. |
3029 | |
3183 | |
3030 | Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190> |
3184 | Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190> |
3031 | makes rev work even on mingw. |
3185 | makes rev work even on mingw. |
|
|
3186 | |
|
|
3187 | =item Haskell |
|
|
3188 | |
|
|
3189 | A haskell binding to libev is available at |
|
|
3190 | L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
3032 | |
3191 | |
3033 | =item D |
3192 | =item D |
3034 | |
3193 | |
3035 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3194 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3036 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
3195 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |