… | |
… | |
117 | |
117 | |
118 | =item int ev_version_major () |
118 | =item int ev_version_major () |
119 | |
119 | |
120 | =item int ev_version_minor () |
120 | =item int ev_version_minor () |
121 | |
121 | |
122 | You can find out the major and minor version numbers of the library |
122 | You can find out the major and minor ABI version numbers of the library |
123 | you linked against by calling the functions C<ev_version_major> and |
123 | you linked against by calling the functions C<ev_version_major> and |
124 | C<ev_version_minor>. If you want, you can compare against the global |
124 | C<ev_version_minor>. If you want, you can compare against the global |
125 | symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the |
125 | symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the |
126 | version of the library your program was compiled against. |
126 | version of the library your program was compiled against. |
127 | |
127 | |
|
|
128 | These version numbers refer to the ABI version of the library, not the |
|
|
129 | release version. |
|
|
130 | |
128 | Usually, it's a good idea to terminate if the major versions mismatch, |
131 | Usually, it's a good idea to terminate if the major versions mismatch, |
129 | as this indicates an incompatible change. Minor versions are usually |
132 | as this indicates an incompatible change. Minor versions are usually |
130 | compatible to older versions, so a larger minor version alone is usually |
133 | compatible to older versions, so a larger minor version alone is usually |
131 | not a problem. |
134 | not a problem. |
132 | |
135 | |
133 | Example: Make sure we haven't accidentally been linked against the wrong |
136 | Example: Make sure we haven't accidentally been linked against the wrong |
134 | version. |
137 | version. |
… | |
… | |
486 | libev watchers. However, a pair of C<ev_prepare>/C<ev_check> watchers is |
489 | libev watchers. However, a pair of C<ev_prepare>/C<ev_check> watchers is |
487 | usually a better approach for this kind of thing. |
490 | usually a better approach for this kind of thing. |
488 | |
491 | |
489 | Here are the gory details of what C<ev_loop> does: |
492 | Here are the gory details of what C<ev_loop> does: |
490 | |
493 | |
|
|
494 | - Before the first iteration, call any pending watchers. |
491 | * If there are no active watchers (reference count is zero), return. |
495 | * If there are no active watchers (reference count is zero), return. |
492 | - Queue prepare watchers and then call all outstanding watchers. |
496 | - Queue all prepare watchers and then call all outstanding watchers. |
493 | - If we have been forked, recreate the kernel state. |
497 | - If we have been forked, recreate the kernel state. |
494 | - Update the kernel state with all outstanding changes. |
498 | - Update the kernel state with all outstanding changes. |
495 | - Update the "event loop time". |
499 | - Update the "event loop time". |
496 | - Calculate for how long to block. |
500 | - Calculate for how long to block. |
497 | - Block the process, waiting for any events. |
501 | - Block the process, waiting for any events. |
… | |
… | |
777 | |
781 | |
778 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
782 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
779 | fine, as long as you do not mind that the priority value you query might |
783 | fine, as long as you do not mind that the priority value you query might |
780 | or might not have been adjusted to be within valid range. |
784 | or might not have been adjusted to be within valid range. |
781 | |
785 | |
|
|
786 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
|
|
787 | |
|
|
788 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
|
|
789 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
|
|
790 | can deal with that fact. |
|
|
791 | |
|
|
792 | =item int ev_clear_pending (loop, ev_TYPE *watcher) |
|
|
793 | |
|
|
794 | If the watcher is pending, this function returns clears its pending status |
|
|
795 | and returns its C<revents> bitset (as if its callback was invoked). If the |
|
|
796 | watcher isn't pending it does nothing and returns C<0>. |
|
|
797 | |
782 | =back |
798 | =back |
783 | |
799 | |
784 | |
800 | |
785 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
801 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
786 | |
802 | |
… | |
… | |
895 | play around with an Xlib connection), then you have to seperately re-test |
911 | play around with an Xlib connection), then you have to seperately re-test |
896 | whether a file descriptor is really ready with a known-to-be good interface |
912 | whether a file descriptor is really ready with a known-to-be good interface |
897 | such as poll (fortunately in our Xlib example, Xlib already does this on |
913 | such as poll (fortunately in our Xlib example, Xlib already does this on |
898 | its own, so its quite safe to use). |
914 | its own, so its quite safe to use). |
899 | |
915 | |
|
|
916 | =head3 The special problem of disappearing file descriptors |
|
|
917 | |
|
|
918 | Some backends (e.g kqueue, epoll) need to be told about closing a file |
|
|
919 | descriptor (either by calling C<close> explicitly or by any other means, |
|
|
920 | such as C<dup>). The reason is that you register interest in some file |
|
|
921 | descriptor, but when it goes away, the operating system will silently drop |
|
|
922 | this interest. If another file descriptor with the same number then is |
|
|
923 | registered with libev, there is no efficient way to see that this is, in |
|
|
924 | fact, a different file descriptor. |
|
|
925 | |
|
|
926 | To avoid having to explicitly tell libev about such cases, libev follows |
|
|
927 | the following policy: Each time C<ev_io_set> is being called, libev |
|
|
928 | will assume that this is potentially a new file descriptor, otherwise |
|
|
929 | it is assumed that the file descriptor stays the same. That means that |
|
|
930 | you I<have> to call C<ev_io_set> (or C<ev_io_init>) when you change the |
|
|
931 | descriptor even if the file descriptor number itself did not change. |
|
|
932 | |
|
|
933 | This is how one would do it normally anyway, the important point is that |
|
|
934 | the libev application should not optimise around libev but should leave |
|
|
935 | optimisations to libev. |
|
|
936 | |
|
|
937 | |
|
|
938 | =head3 Watcher-Specific Functions |
|
|
939 | |
900 | =over 4 |
940 | =over 4 |
901 | |
941 | |
902 | =item ev_io_init (ev_io *, callback, int fd, int events) |
942 | =item ev_io_init (ev_io *, callback, int fd, int events) |
903 | |
943 | |
904 | =item ev_io_set (ev_io *, int fd, int events) |
944 | =item ev_io_set (ev_io *, int fd, int events) |
… | |
… | |
956 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
996 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
957 | |
997 | |
958 | The callback is guarenteed to be invoked only when its timeout has passed, |
998 | The callback is guarenteed to be invoked only when its timeout has passed, |
959 | but if multiple timers become ready during the same loop iteration then |
999 | but if multiple timers become ready during the same loop iteration then |
960 | order of execution is undefined. |
1000 | order of execution is undefined. |
|
|
1001 | |
|
|
1002 | =head3 Watcher-Specific Functions and Data Members |
961 | |
1003 | |
962 | =over 4 |
1004 | =over 4 |
963 | |
1005 | |
964 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
1006 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
965 | |
1007 | |
… | |
… | |
1061 | but on wallclock time (absolute time). You can tell a periodic watcher |
1103 | but on wallclock time (absolute time). You can tell a periodic watcher |
1062 | to trigger "at" some specific point in time. For example, if you tell a |
1104 | to trigger "at" some specific point in time. For example, if you tell a |
1063 | periodic watcher to trigger in 10 seconds (by specifiying e.g. C<ev_now () |
1105 | periodic watcher to trigger in 10 seconds (by specifiying e.g. C<ev_now () |
1064 | + 10.>) and then reset your system clock to the last year, then it will |
1106 | + 10.>) and then reset your system clock to the last year, then it will |
1065 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
1107 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
1066 | roughly 10 seconds later and of course not if you reset your system time |
1108 | roughly 10 seconds later). |
1067 | again). |
|
|
1068 | |
1109 | |
1069 | They can also be used to implement vastly more complex timers, such as |
1110 | They can also be used to implement vastly more complex timers, such as |
1070 | triggering an event on eahc midnight, local time. |
1111 | triggering an event on each midnight, local time or other, complicated, |
|
|
1112 | rules. |
1071 | |
1113 | |
1072 | As with timers, the callback is guarenteed to be invoked only when the |
1114 | As with timers, the callback is guarenteed to be invoked only when the |
1073 | time (C<at>) has been passed, but if multiple periodic timers become ready |
1115 | time (C<at>) has been passed, but if multiple periodic timers become ready |
1074 | during the same loop iteration then order of execution is undefined. |
1116 | during the same loop iteration then order of execution is undefined. |
1075 | |
1117 | |
|
|
1118 | =head3 Watcher-Specific Functions and Data Members |
|
|
1119 | |
1076 | =over 4 |
1120 | =over 4 |
1077 | |
1121 | |
1078 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1122 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1079 | |
1123 | |
1080 | =item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb) |
1124 | =item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb) |
… | |
… | |
1082 | Lots of arguments, lets sort it out... There are basically three modes of |
1126 | Lots of arguments, lets sort it out... There are basically three modes of |
1083 | operation, and we will explain them from simplest to complex: |
1127 | operation, and we will explain them from simplest to complex: |
1084 | |
1128 | |
1085 | =over 4 |
1129 | =over 4 |
1086 | |
1130 | |
1087 | =item * absolute timer (interval = reschedule_cb = 0) |
1131 | =item * absolute timer (at = time, interval = reschedule_cb = 0) |
1088 | |
1132 | |
1089 | In this configuration the watcher triggers an event at the wallclock time |
1133 | In this configuration the watcher triggers an event at the wallclock time |
1090 | C<at> and doesn't repeat. It will not adjust when a time jump occurs, |
1134 | C<at> and doesn't repeat. It will not adjust when a time jump occurs, |
1091 | that is, if it is to be run at January 1st 2011 then it will run when the |
1135 | that is, if it is to be run at January 1st 2011 then it will run when the |
1092 | system time reaches or surpasses this time. |
1136 | system time reaches or surpasses this time. |
1093 | |
1137 | |
1094 | =item * non-repeating interval timer (interval > 0, reschedule_cb = 0) |
1138 | =item * non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1095 | |
1139 | |
1096 | In this mode the watcher will always be scheduled to time out at the next |
1140 | In this mode the watcher will always be scheduled to time out at the next |
1097 | C<at + N * interval> time (for some integer N) and then repeat, regardless |
1141 | C<at + N * interval> time (for some integer N, which can also be negative) |
1098 | of any time jumps. |
1142 | and then repeat, regardless of any time jumps. |
1099 | |
1143 | |
1100 | This can be used to create timers that do not drift with respect to system |
1144 | This can be used to create timers that do not drift with respect to system |
1101 | time: |
1145 | time: |
1102 | |
1146 | |
1103 | ev_periodic_set (&periodic, 0., 3600., 0); |
1147 | ev_periodic_set (&periodic, 0., 3600., 0); |
… | |
… | |
1109 | |
1153 | |
1110 | Another way to think about it (for the mathematically inclined) is that |
1154 | Another way to think about it (for the mathematically inclined) is that |
1111 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1155 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1112 | time where C<time = at (mod interval)>, regardless of any time jumps. |
1156 | time where C<time = at (mod interval)>, regardless of any time jumps. |
1113 | |
1157 | |
|
|
1158 | For numerical stability it is preferable that the C<at> value is near |
|
|
1159 | C<ev_now ()> (the current time), but there is no range requirement for |
|
|
1160 | this value. |
|
|
1161 | |
1114 | =item * manual reschedule mode (reschedule_cb = callback) |
1162 | =item * manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1115 | |
1163 | |
1116 | In this mode the values for C<interval> and C<at> are both being |
1164 | In this mode the values for C<interval> and C<at> are both being |
1117 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1165 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1118 | reschedule callback will be called with the watcher as first, and the |
1166 | reschedule callback will be called with the watcher as first, and the |
1119 | current time as second argument. |
1167 | current time as second argument. |
1120 | |
1168 | |
1121 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
1169 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
1122 | ever, or make any event loop modifications>. If you need to stop it, |
1170 | ever, or make any event loop modifications>. If you need to stop it, |
1123 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
1171 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
1124 | starting a prepare watcher). |
1172 | starting an C<ev_prepare> watcher, which is legal). |
1125 | |
1173 | |
1126 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1174 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1127 | ev_tstamp now)>, e.g.: |
1175 | ev_tstamp now)>, e.g.: |
1128 | |
1176 | |
1129 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1177 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
… | |
… | |
1151 | |
1199 | |
1152 | Simply stops and restarts the periodic watcher again. This is only useful |
1200 | Simply stops and restarts the periodic watcher again. This is only useful |
1153 | when you changed some parameters or the reschedule callback would return |
1201 | when you changed some parameters or the reschedule callback would return |
1154 | a different time than the last time it was called (e.g. in a crond like |
1202 | a different time than the last time it was called (e.g. in a crond like |
1155 | program when the crontabs have changed). |
1203 | program when the crontabs have changed). |
|
|
1204 | |
|
|
1205 | =item ev_tstamp offset [read-write] |
|
|
1206 | |
|
|
1207 | When repeating, this contains the offset value, otherwise this is the |
|
|
1208 | absolute point in time (the C<at> value passed to C<ev_periodic_set>). |
|
|
1209 | |
|
|
1210 | Can be modified any time, but changes only take effect when the periodic |
|
|
1211 | timer fires or C<ev_periodic_again> is being called. |
1156 | |
1212 | |
1157 | =item ev_tstamp interval [read-write] |
1213 | =item ev_tstamp interval [read-write] |
1158 | |
1214 | |
1159 | The current interval value. Can be modified any time, but changes only |
1215 | The current interval value. Can be modified any time, but changes only |
1160 | take effect when the periodic timer fires or C<ev_periodic_again> is being |
1216 | take effect when the periodic timer fires or C<ev_periodic_again> is being |
… | |
… | |
1214 | with the kernel (thus it coexists with your own signal handlers as long |
1270 | with the kernel (thus it coexists with your own signal handlers as long |
1215 | as you don't register any with libev). Similarly, when the last signal |
1271 | as you don't register any with libev). Similarly, when the last signal |
1216 | watcher for a signal is stopped libev will reset the signal handler to |
1272 | watcher for a signal is stopped libev will reset the signal handler to |
1217 | SIG_DFL (regardless of what it was set to before). |
1273 | SIG_DFL (regardless of what it was set to before). |
1218 | |
1274 | |
|
|
1275 | =head3 Watcher-Specific Functions and Data Members |
|
|
1276 | |
1219 | =over 4 |
1277 | =over 4 |
1220 | |
1278 | |
1221 | =item ev_signal_init (ev_signal *, callback, int signum) |
1279 | =item ev_signal_init (ev_signal *, callback, int signum) |
1222 | |
1280 | |
1223 | =item ev_signal_set (ev_signal *, int signum) |
1281 | =item ev_signal_set (ev_signal *, int signum) |
… | |
… | |
1234 | |
1292 | |
1235 | =head2 C<ev_child> - watch out for process status changes |
1293 | =head2 C<ev_child> - watch out for process status changes |
1236 | |
1294 | |
1237 | Child watchers trigger when your process receives a SIGCHLD in response to |
1295 | Child watchers trigger when your process receives a SIGCHLD in response to |
1238 | some child status changes (most typically when a child of yours dies). |
1296 | some child status changes (most typically when a child of yours dies). |
|
|
1297 | |
|
|
1298 | =head3 Watcher-Specific Functions and Data Members |
1239 | |
1299 | |
1240 | =over 4 |
1300 | =over 4 |
1241 | |
1301 | |
1242 | =item ev_child_init (ev_child *, callback, int pid) |
1302 | =item ev_child_init (ev_child *, callback, int pid) |
1243 | |
1303 | |
… | |
… | |
1311 | reader). Inotify will be used to give hints only and should not change the |
1371 | reader). Inotify will be used to give hints only and should not change the |
1312 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
1372 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
1313 | to fall back to regular polling again even with inotify, but changes are |
1373 | to fall back to regular polling again even with inotify, but changes are |
1314 | usually detected immediately, and if the file exists there will be no |
1374 | usually detected immediately, and if the file exists there will be no |
1315 | polling. |
1375 | polling. |
|
|
1376 | |
|
|
1377 | =head3 Watcher-Specific Functions and Data Members |
1316 | |
1378 | |
1317 | =over 4 |
1379 | =over 4 |
1318 | |
1380 | |
1319 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1381 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1320 | |
1382 | |
… | |
… | |
1403 | Apart from keeping your process non-blocking (which is a useful |
1465 | Apart from keeping your process non-blocking (which is a useful |
1404 | effect on its own sometimes), idle watchers are a good place to do |
1466 | effect on its own sometimes), idle watchers are a good place to do |
1405 | "pseudo-background processing", or delay processing stuff to after the |
1467 | "pseudo-background processing", or delay processing stuff to after the |
1406 | event loop has handled all outstanding events. |
1468 | event loop has handled all outstanding events. |
1407 | |
1469 | |
|
|
1470 | =head3 Watcher-Specific Functions and Data Members |
|
|
1471 | |
1408 | =over 4 |
1472 | =over 4 |
1409 | |
1473 | |
1410 | =item ev_idle_init (ev_signal *, callback) |
1474 | =item ev_idle_init (ev_signal *, callback) |
1411 | |
1475 | |
1412 | Initialises and configures the idle watcher - it has no parameters of any |
1476 | Initialises and configures the idle watcher - it has no parameters of any |
… | |
… | |
1469 | with priority higher than or equal to the event loop and one coroutine |
1533 | with priority higher than or equal to the event loop and one coroutine |
1470 | of lower priority, but only once, using idle watchers to keep the event |
1534 | of lower priority, but only once, using idle watchers to keep the event |
1471 | loop from blocking if lower-priority coroutines are active, thus mapping |
1535 | loop from blocking if lower-priority coroutines are active, thus mapping |
1472 | low-priority coroutines to idle/background tasks). |
1536 | low-priority coroutines to idle/background tasks). |
1473 | |
1537 | |
|
|
1538 | It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>) |
|
|
1539 | priority, to ensure that they are being run before any other watchers |
|
|
1540 | after the poll. Also, C<ev_check> watchers (and C<ev_prepare> watchers, |
|
|
1541 | too) should not activate ("feed") events into libev. While libev fully |
|
|
1542 | supports this, they will be called before other C<ev_check> watchers did |
|
|
1543 | their job. As C<ev_check> watchers are often used to embed other event |
|
|
1544 | loops those other event loops might be in an unusable state until their |
|
|
1545 | C<ev_check> watcher ran (always remind yourself to coexist peacefully with |
|
|
1546 | others). |
|
|
1547 | |
|
|
1548 | =head3 Watcher-Specific Functions and Data Members |
|
|
1549 | |
1474 | =over 4 |
1550 | =over 4 |
1475 | |
1551 | |
1476 | =item ev_prepare_init (ev_prepare *, callback) |
1552 | =item ev_prepare_init (ev_prepare *, callback) |
1477 | |
1553 | |
1478 | =item ev_check_init (ev_check *, callback) |
1554 | =item ev_check_init (ev_check *, callback) |
… | |
… | |
1481 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
1557 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
1482 | macros, but using them is utterly, utterly and completely pointless. |
1558 | macros, but using them is utterly, utterly and completely pointless. |
1483 | |
1559 | |
1484 | =back |
1560 | =back |
1485 | |
1561 | |
1486 | Example: To include a library such as adns, you would add IO watchers |
1562 | There are a number of principal ways to embed other event loops or modules |
1487 | and a timeout watcher in a prepare handler, as required by libadns, and |
1563 | into libev. Here are some ideas on how to include libadns into libev |
|
|
1564 | (there is a Perl module named C<EV::ADNS> that does this, which you could |
|
|
1565 | use for an actually working example. Another Perl module named C<EV::Glib> |
|
|
1566 | embeds a Glib main context into libev, and finally, C<Glib::EV> embeds EV |
|
|
1567 | into the Glib event loop). |
|
|
1568 | |
|
|
1569 | Method 1: Add IO watchers and a timeout watcher in a prepare handler, |
1488 | in a check watcher, destroy them and call into libadns. What follows is |
1570 | and in a check watcher, destroy them and call into libadns. What follows |
1489 | pseudo-code only of course: |
1571 | is pseudo-code only of course. This requires you to either use a low |
|
|
1572 | priority for the check watcher or use C<ev_clear_pending> explicitly, as |
|
|
1573 | the callbacks for the IO/timeout watchers might not have been called yet. |
1490 | |
1574 | |
1491 | static ev_io iow [nfd]; |
1575 | static ev_io iow [nfd]; |
1492 | static ev_timer tw; |
1576 | static ev_timer tw; |
1493 | |
1577 | |
1494 | static void |
1578 | static void |
1495 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1579 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1496 | { |
1580 | { |
1497 | // set the relevant poll flags |
|
|
1498 | // could also call adns_processreadable etc. here |
|
|
1499 | struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1500 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1501 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1502 | } |
1581 | } |
1503 | |
1582 | |
1504 | // create io watchers for each fd and a timer before blocking |
1583 | // create io watchers for each fd and a timer before blocking |
1505 | static void |
1584 | static void |
1506 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1585 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
… | |
… | |
1512 | |
1591 | |
1513 | /* the callback is illegal, but won't be called as we stop during check */ |
1592 | /* the callback is illegal, but won't be called as we stop during check */ |
1514 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1593 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1515 | ev_timer_start (loop, &tw); |
1594 | ev_timer_start (loop, &tw); |
1516 | |
1595 | |
1517 | // create on ev_io per pollfd |
1596 | // create one ev_io per pollfd |
1518 | for (int i = 0; i < nfd; ++i) |
1597 | for (int i = 0; i < nfd; ++i) |
1519 | { |
1598 | { |
1520 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1599 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1521 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1600 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1522 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1601 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1523 | |
1602 | |
1524 | fds [i].revents = 0; |
1603 | fds [i].revents = 0; |
1525 | iow [i].data = fds + i; |
|
|
1526 | ev_io_start (loop, iow + i); |
1604 | ev_io_start (loop, iow + i); |
1527 | } |
1605 | } |
1528 | } |
1606 | } |
1529 | |
1607 | |
1530 | // stop all watchers after blocking |
1608 | // stop all watchers after blocking |
… | |
… | |
1532 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1610 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1533 | { |
1611 | { |
1534 | ev_timer_stop (loop, &tw); |
1612 | ev_timer_stop (loop, &tw); |
1535 | |
1613 | |
1536 | for (int i = 0; i < nfd; ++i) |
1614 | for (int i = 0; i < nfd; ++i) |
|
|
1615 | { |
|
|
1616 | // set the relevant poll flags |
|
|
1617 | // could also call adns_processreadable etc. here |
|
|
1618 | struct pollfd *fd = fds + i; |
|
|
1619 | int revents = ev_clear_pending (iow + i); |
|
|
1620 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1621 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1622 | |
|
|
1623 | // now stop the watcher |
1537 | ev_io_stop (loop, iow + i); |
1624 | ev_io_stop (loop, iow + i); |
|
|
1625 | } |
1538 | |
1626 | |
1539 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
1627 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1628 | } |
|
|
1629 | |
|
|
1630 | Method 2: This would be just like method 1, but you run C<adns_afterpoll> |
|
|
1631 | in the prepare watcher and would dispose of the check watcher. |
|
|
1632 | |
|
|
1633 | Method 3: If the module to be embedded supports explicit event |
|
|
1634 | notification (adns does), you can also make use of the actual watcher |
|
|
1635 | callbacks, and only destroy/create the watchers in the prepare watcher. |
|
|
1636 | |
|
|
1637 | static void |
|
|
1638 | timer_cb (EV_P_ ev_timer *w, int revents) |
|
|
1639 | { |
|
|
1640 | adns_state ads = (adns_state)w->data; |
|
|
1641 | update_now (EV_A); |
|
|
1642 | |
|
|
1643 | adns_processtimeouts (ads, &tv_now); |
|
|
1644 | } |
|
|
1645 | |
|
|
1646 | static void |
|
|
1647 | io_cb (EV_P_ ev_io *w, int revents) |
|
|
1648 | { |
|
|
1649 | adns_state ads = (adns_state)w->data; |
|
|
1650 | update_now (EV_A); |
|
|
1651 | |
|
|
1652 | if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now); |
|
|
1653 | if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now); |
|
|
1654 | } |
|
|
1655 | |
|
|
1656 | // do not ever call adns_afterpoll |
|
|
1657 | |
|
|
1658 | Method 4: Do not use a prepare or check watcher because the module you |
|
|
1659 | want to embed is too inflexible to support it. Instead, youc na override |
|
|
1660 | their poll function. The drawback with this solution is that the main |
|
|
1661 | loop is now no longer controllable by EV. The C<Glib::EV> module does |
|
|
1662 | this. |
|
|
1663 | |
|
|
1664 | static gint |
|
|
1665 | event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
|
|
1666 | { |
|
|
1667 | int got_events = 0; |
|
|
1668 | |
|
|
1669 | for (n = 0; n < nfds; ++n) |
|
|
1670 | // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
|
|
1671 | |
|
|
1672 | if (timeout >= 0) |
|
|
1673 | // create/start timer |
|
|
1674 | |
|
|
1675 | // poll |
|
|
1676 | ev_loop (EV_A_ 0); |
|
|
1677 | |
|
|
1678 | // stop timer again |
|
|
1679 | if (timeout >= 0) |
|
|
1680 | ev_timer_stop (EV_A_ &to); |
|
|
1681 | |
|
|
1682 | // stop io watchers again - their callbacks should have set |
|
|
1683 | for (n = 0; n < nfds; ++n) |
|
|
1684 | ev_io_stop (EV_A_ iow [n]); |
|
|
1685 | |
|
|
1686 | return got_events; |
1540 | } |
1687 | } |
1541 | |
1688 | |
1542 | |
1689 | |
1543 | =head2 C<ev_embed> - when one backend isn't enough... |
1690 | =head2 C<ev_embed> - when one backend isn't enough... |
1544 | |
1691 | |
… | |
… | |
1608 | ev_embed_start (loop_hi, &embed); |
1755 | ev_embed_start (loop_hi, &embed); |
1609 | } |
1756 | } |
1610 | else |
1757 | else |
1611 | loop_lo = loop_hi; |
1758 | loop_lo = loop_hi; |
1612 | |
1759 | |
|
|
1760 | =head3 Watcher-Specific Functions and Data Members |
|
|
1761 | |
1613 | =over 4 |
1762 | =over 4 |
1614 | |
1763 | |
1615 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop) |
1764 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop) |
1616 | |
1765 | |
1617 | =item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop) |
1766 | =item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop) |
… | |
… | |
1643 | event loop blocks next and before C<ev_check> watchers are being called, |
1792 | event loop blocks next and before C<ev_check> watchers are being called, |
1644 | and only in the child after the fork. If whoever good citizen calling |
1793 | and only in the child after the fork. If whoever good citizen calling |
1645 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
1794 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
1646 | handlers will be invoked, too, of course. |
1795 | handlers will be invoked, too, of course. |
1647 | |
1796 | |
|
|
1797 | =head3 Watcher-Specific Functions and Data Members |
|
|
1798 | |
1648 | =over 4 |
1799 | =over 4 |
1649 | |
1800 | |
1650 | =item ev_fork_init (ev_signal *, callback) |
1801 | =item ev_fork_init (ev_signal *, callback) |
1651 | |
1802 | |
1652 | Initialises and configures the fork watcher - it has no parameters of any |
1803 | Initialises and configures the fork watcher - it has no parameters of any |
… | |
… | |
1832 | |
1983 | |
1833 | myclass obj; |
1984 | myclass obj; |
1834 | ev::io iow; |
1985 | ev::io iow; |
1835 | iow.set <myclass, &myclass::io_cb> (&obj); |
1986 | iow.set <myclass, &myclass::io_cb> (&obj); |
1836 | |
1987 | |
1837 | =item w->set (void (*function)(watcher &w, int), void *data = 0) |
1988 | =item w->set<function> (void *data = 0) |
1838 | |
1989 | |
1839 | Also sets a callback, but uses a static method or plain function as |
1990 | Also sets a callback, but uses a static method or plain function as |
1840 | callback. The optional C<data> argument will be stored in the watcher's |
1991 | callback. The optional C<data> argument will be stored in the watcher's |
1841 | C<data> member and is free for you to use. |
1992 | C<data> member and is free for you to use. |
1842 | |
1993 | |
|
|
1994 | The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>. |
|
|
1995 | |
1843 | See the method-C<set> above for more details. |
1996 | See the method-C<set> above for more details. |
|
|
1997 | |
|
|
1998 | Example: |
|
|
1999 | |
|
|
2000 | static void io_cb (ev::io &w, int revents) { } |
|
|
2001 | iow.set <io_cb> (); |
1844 | |
2002 | |
1845 | =item w->set (struct ev_loop *) |
2003 | =item w->set (struct ev_loop *) |
1846 | |
2004 | |
1847 | Associates a different C<struct ev_loop> with this watcher. You can only |
2005 | Associates a different C<struct ev_loop> with this watcher. You can only |
1848 | do this when the watcher is inactive (and not pending either). |
2006 | do this when the watcher is inactive (and not pending either). |