… | |
… | |
4 | <head> |
4 | <head> |
5 | <title>libev</title> |
5 | <title>libev</title> |
6 | <meta name="description" content="Pod documentation for libev" /> |
6 | <meta name="description" content="Pod documentation for libev" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
9 | <meta name="created" content="Sat Dec 8 15:27:35 2007" /> |
9 | <meta name="created" content="Wed Dec 12 05:53:55 2007" /> |
10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
10 | <meta name="generator" content="Pod::Xhtml 1.57" /> |
11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
11 | <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> |
12 | <body> |
12 | <body> |
13 | <div class="pod"> |
13 | <div class="pod"> |
14 | <!-- INDEX START --> |
14 | <!-- INDEX START --> |
… | |
… | |
27 | <ul><li><a href="#GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</a></li> |
27 | <ul><li><a href="#GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</a></li> |
28 | <li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> |
28 | <li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> |
29 | </ul> |
29 | </ul> |
30 | </li> |
30 | </li> |
31 | <li><a href="#WATCHER_TYPES">WATCHER TYPES</a> |
31 | <li><a href="#WATCHER_TYPES">WATCHER TYPES</a> |
32 | <ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable?</a></li> |
32 | <ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable?</a> |
|
|
33 | <ul><li><a href="#The_special_problem_of_disappearing_">The special problem of disappearing file descriptors</a></li> |
|
|
34 | </ul> |
|
|
35 | </li> |
33 | <li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</a></li> |
36 | <li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</a></li> |
34 | <li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</a></li> |
37 | <li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</a></li> |
35 | <li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</a></li> |
38 | <li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</a></li> |
36 | <li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li> |
39 | <li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li> |
37 | <li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li> |
40 | <li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li> |
… | |
… | |
185 | you actually want to know.</p> |
188 | you actually want to know.</p> |
186 | </dd> |
189 | </dd> |
187 | <dt>int ev_version_major ()</dt> |
190 | <dt>int ev_version_major ()</dt> |
188 | <dt>int ev_version_minor ()</dt> |
191 | <dt>int ev_version_minor ()</dt> |
189 | <dd> |
192 | <dd> |
190 | <p>You can find out the major and minor version numbers of the library |
193 | <p>You can find out the major and minor ABI version numbers of the library |
191 | you linked against by calling the functions <code>ev_version_major</code> and |
194 | you linked against by calling the functions <code>ev_version_major</code> and |
192 | <code>ev_version_minor</code>. If you want, you can compare against the global |
195 | <code>ev_version_minor</code>. If you want, you can compare against the global |
193 | symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the |
196 | symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the |
194 | version of the library your program was compiled against.</p> |
197 | version of the library your program was compiled against.</p> |
|
|
198 | <p>These version numbers refer to the ABI version of the library, not the |
|
|
199 | release version.</p> |
195 | <p>Usually, it's a good idea to terminate if the major versions mismatch, |
200 | <p>Usually, it's a good idea to terminate if the major versions mismatch, |
196 | as this indicates an incompatible change. Minor versions are usually |
201 | as this indicates an incompatible change. Minor versions are usually |
197 | compatible to older versions, so a larger minor version alone is usually |
202 | compatible to older versions, so a larger minor version alone is usually |
198 | not a problem.</p> |
203 | not a problem.</p> |
199 | <p>Example: Make sure we haven't accidentally been linked against the wrong |
204 | <p>Example: Make sure we haven't accidentally been linked against the wrong |
200 | version.</p> |
205 | version.</p> |
201 | <pre> assert (("libev version mismatch", |
206 | <pre> assert (("libev version mismatch", |
… | |
… | |
529 | one iteration of the loop. This is useful if you are waiting for some |
534 | one iteration of the loop. This is useful if you are waiting for some |
530 | external event in conjunction with something not expressible using other |
535 | external event in conjunction with something not expressible using other |
531 | libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is |
536 | libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is |
532 | usually a better approach for this kind of thing.</p> |
537 | usually a better approach for this kind of thing.</p> |
533 | <p>Here are the gory details of what <code>ev_loop</code> does:</p> |
538 | <p>Here are the gory details of what <code>ev_loop</code> does:</p> |
|
|
539 | <pre> - Before the first iteration, call any pending watchers. |
534 | <pre> * If there are no active watchers (reference count is zero), return. |
540 | * If there are no active watchers (reference count is zero), return. |
535 | - Queue prepare watchers and then call all outstanding watchers. |
541 | - Queue all prepare watchers and then call all outstanding watchers. |
536 | - If we have been forked, recreate the kernel state. |
542 | - If we have been forked, recreate the kernel state. |
537 | - Update the kernel state with all outstanding changes. |
543 | - Update the kernel state with all outstanding changes. |
538 | - Update the "event loop time". |
544 | - Update the "event loop time". |
539 | - Calculate for how long to block. |
545 | - Calculate for how long to block. |
540 | - Block the process, waiting for any events. |
546 | - Block the process, waiting for any events. |
… | |
… | |
938 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
944 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
939 | play around with an Xlib connection), then you have to seperately re-test |
945 | play around with an Xlib connection), then you have to seperately re-test |
940 | whether a file descriptor is really ready with a known-to-be good interface |
946 | whether a file descriptor is really ready with a known-to-be good interface |
941 | such as poll (fortunately in our Xlib example, Xlib already does this on |
947 | such as poll (fortunately in our Xlib example, Xlib already does this on |
942 | its own, so its quite safe to use).</p> |
948 | its own, so its quite safe to use).</p> |
|
|
949 | |
|
|
950 | </div> |
|
|
951 | <h3 id="The_special_problem_of_disappearing_">The special problem of disappearing file descriptors</h3> |
|
|
952 | <div id="The_special_problem_of_disappearing_-2"> |
|
|
953 | <p>Some backends (e.g kqueue, epoll) need to be told about closing a file |
|
|
954 | descriptor (either by calling <code>close</code> explicitly or by any other means, |
|
|
955 | such as <code>dup</code>). The reason is that you register interest in some file |
|
|
956 | descriptor, but when it goes away, the operating system will silently drop |
|
|
957 | this interest. If another file descriptor with the same number then is |
|
|
958 | registered with libev, there is no efficient way to see that this is, in |
|
|
959 | fact, a different file descriptor.</p> |
|
|
960 | <p>To avoid having to explicitly tell libev about such cases, libev follows |
|
|
961 | the following policy: Each time <code>ev_io_set</code> is being called, libev |
|
|
962 | will assume that this is potentially a new file descriptor, otherwise |
|
|
963 | it is assumed that the file descriptor stays the same. That means that |
|
|
964 | you <i>have</i> to call <code>ev_io_set</code> (or <code>ev_io_init</code>) when you change the |
|
|
965 | descriptor even if the file descriptor number itself did not change.</p> |
|
|
966 | <p>This is how one would do it normally anyway, the important point is that |
|
|
967 | the libev application should not optimise around libev but should leave |
|
|
968 | optimisations to libev.</p> |
|
|
969 | |
|
|
970 | |
|
|
971 | |
|
|
972 | |
943 | <dl> |
973 | <dl> |
944 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
974 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
945 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
975 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
946 | <dd> |
976 | <dd> |
947 | <p>Configures an <code>ev_io</code> watcher. The <code>fd</code> is the file descriptor to |
977 | <p>Configures an <code>ev_io</code> watcher. The <code>fd</code> is the file descriptor to |
… | |
… | |
1096 | but on wallclock time (absolute time). You can tell a periodic watcher |
1126 | but on wallclock time (absolute time). You can tell a periodic watcher |
1097 | to trigger "at" some specific point in time. For example, if you tell a |
1127 | to trigger "at" some specific point in time. For example, if you tell a |
1098 | periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now () |
1128 | periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now () |
1099 | + 10.</code>) and then reset your system clock to the last year, then it will |
1129 | + 10.</code>) and then reset your system clock to the last year, then it will |
1100 | take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger |
1130 | take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger |
1101 | roughly 10 seconds later and of course not if you reset your system time |
1131 | roughly 10 seconds later).</p> |
1102 | again).</p> |
|
|
1103 | <p>They can also be used to implement vastly more complex timers, such as |
1132 | <p>They can also be used to implement vastly more complex timers, such as |
1104 | triggering an event on eahc midnight, local time.</p> |
1133 | triggering an event on each midnight, local time or other, complicated, |
|
|
1134 | rules.</p> |
1105 | <p>As with timers, the callback is guarenteed to be invoked only when the |
1135 | <p>As with timers, the callback is guarenteed to be invoked only when the |
1106 | time (<code>at</code>) has been passed, but if multiple periodic timers become ready |
1136 | time (<code>at</code>) has been passed, but if multiple periodic timers become ready |
1107 | during the same loop iteration then order of execution is undefined.</p> |
1137 | during the same loop iteration then order of execution is undefined.</p> |
1108 | <dl> |
1138 | <dl> |
1109 | <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> |
1139 | <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> |
… | |
… | |
1111 | <dd> |
1141 | <dd> |
1112 | <p>Lots of arguments, lets sort it out... There are basically three modes of |
1142 | <p>Lots of arguments, lets sort it out... There are basically three modes of |
1113 | operation, and we will explain them from simplest to complex:</p> |
1143 | operation, and we will explain them from simplest to complex:</p> |
1114 | <p> |
1144 | <p> |
1115 | <dl> |
1145 | <dl> |
1116 | <dt>* absolute timer (interval = reschedule_cb = 0)</dt> |
1146 | <dt>* absolute timer (at = time, interval = reschedule_cb = 0)</dt> |
1117 | <dd> |
1147 | <dd> |
1118 | <p>In this configuration the watcher triggers an event at the wallclock time |
1148 | <p>In this configuration the watcher triggers an event at the wallclock time |
1119 | <code>at</code> and doesn't repeat. It will not adjust when a time jump occurs, |
1149 | <code>at</code> and doesn't repeat. It will not adjust when a time jump occurs, |
1120 | that is, if it is to be run at January 1st 2011 then it will run when the |
1150 | that is, if it is to be run at January 1st 2011 then it will run when the |
1121 | system time reaches or surpasses this time.</p> |
1151 | system time reaches or surpasses this time.</p> |
1122 | </dd> |
1152 | </dd> |
1123 | <dt>* non-repeating interval timer (interval > 0, reschedule_cb = 0)</dt> |
1153 | <dt>* non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)</dt> |
1124 | <dd> |
1154 | <dd> |
1125 | <p>In this mode the watcher will always be scheduled to time out at the next |
1155 | <p>In this mode the watcher will always be scheduled to time out at the next |
1126 | <code>at + N * interval</code> time (for some integer N) and then repeat, regardless |
1156 | <code>at + N * interval</code> time (for some integer N, which can also be negative) |
1127 | of any time jumps.</p> |
1157 | and then repeat, regardless of any time jumps.</p> |
1128 | <p>This can be used to create timers that do not drift with respect to system |
1158 | <p>This can be used to create timers that do not drift with respect to system |
1129 | time:</p> |
1159 | time:</p> |
1130 | <pre> ev_periodic_set (&periodic, 0., 3600., 0); |
1160 | <pre> ev_periodic_set (&periodic, 0., 3600., 0); |
1131 | |
1161 | |
1132 | </pre> |
1162 | </pre> |
… | |
… | |
1135 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1165 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1136 | by 3600.</p> |
1166 | by 3600.</p> |
1137 | <p>Another way to think about it (for the mathematically inclined) is that |
1167 | <p>Another way to think about it (for the mathematically inclined) is that |
1138 | <code>ev_periodic</code> will try to run the callback in this mode at the next possible |
1168 | <code>ev_periodic</code> will try to run the callback in this mode at the next possible |
1139 | time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> |
1169 | time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> |
|
|
1170 | <p>For numerical stability it is preferable that the <code>at</code> value is near |
|
|
1171 | <code>ev_now ()</code> (the current time), but there is no range requirement for |
|
|
1172 | this value.</p> |
1140 | </dd> |
1173 | </dd> |
1141 | <dt>* manual reschedule mode (reschedule_cb = callback)</dt> |
1174 | <dt>* manual reschedule mode (at and interval ignored, reschedule_cb = callback)</dt> |
1142 | <dd> |
1175 | <dd> |
1143 | <p>In this mode the values for <code>interval</code> and <code>at</code> are both being |
1176 | <p>In this mode the values for <code>interval</code> and <code>at</code> are both being |
1144 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1177 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1145 | reschedule callback will be called with the watcher as first, and the |
1178 | reschedule callback will be called with the watcher as first, and the |
1146 | current time as second argument.</p> |
1179 | current time as second argument.</p> |
1147 | <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher, |
1180 | <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher, |
1148 | ever, or make any event loop modifications</i>. If you need to stop it, |
1181 | ever, or make any event loop modifications</i>. If you need to stop it, |
1149 | return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by |
1182 | return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by |
1150 | starting a prepare watcher).</p> |
1183 | starting an <code>ev_prepare</code> watcher, which is legal).</p> |
1151 | <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1184 | <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1152 | ev_tstamp now)</code>, e.g.:</p> |
1185 | ev_tstamp now)</code>, e.g.:</p> |
1153 | <pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1186 | <pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1154 | { |
1187 | { |
1155 | return now + 60.; |
1188 | return now + 60.; |
… | |
… | |
1175 | <dd> |
1208 | <dd> |
1176 | <p>Simply stops and restarts the periodic watcher again. This is only useful |
1209 | <p>Simply stops and restarts the periodic watcher again. This is only useful |
1177 | when you changed some parameters or the reschedule callback would return |
1210 | when you changed some parameters or the reschedule callback would return |
1178 | a different time than the last time it was called (e.g. in a crond like |
1211 | a different time than the last time it was called (e.g. in a crond like |
1179 | program when the crontabs have changed).</p> |
1212 | program when the crontabs have changed).</p> |
|
|
1213 | </dd> |
|
|
1214 | <dt>ev_tstamp offset [read-write]</dt> |
|
|
1215 | <dd> |
|
|
1216 | <p>When repeating, this contains the offset value, otherwise this is the |
|
|
1217 | absolute point in time (the <code>at</code> value passed to <code>ev_periodic_set</code>).</p> |
|
|
1218 | <p>Can be modified any time, but changes only take effect when the periodic |
|
|
1219 | timer fires or <code>ev_periodic_again</code> is being called.</p> |
1180 | </dd> |
1220 | </dd> |
1181 | <dt>ev_tstamp interval [read-write]</dt> |
1221 | <dt>ev_tstamp interval [read-write]</dt> |
1182 | <dd> |
1222 | <dd> |
1183 | <p>The current interval value. Can be modified any time, but changes only |
1223 | <p>The current interval value. Can be modified any time, but changes only |
1184 | take effect when the periodic timer fires or <code>ev_periodic_again</code> is being |
1224 | take effect when the periodic timer fires or <code>ev_periodic_again</code> is being |
… | |
… | |
1483 | are ready to run (it's actually more complicated: it only runs coroutines |
1523 | are ready to run (it's actually more complicated: it only runs coroutines |
1484 | with priority higher than or equal to the event loop and one coroutine |
1524 | with priority higher than or equal to the event loop and one coroutine |
1485 | of lower priority, but only once, using idle watchers to keep the event |
1525 | of lower priority, but only once, using idle watchers to keep the event |
1486 | loop from blocking if lower-priority coroutines are active, thus mapping |
1526 | loop from blocking if lower-priority coroutines are active, thus mapping |
1487 | low-priority coroutines to idle/background tasks).</p> |
1527 | low-priority coroutines to idle/background tasks).</p> |
|
|
1528 | <p>It is recommended to give <code>ev_check</code> watchers highest (<code>EV_MAXPRI</code>) |
|
|
1529 | priority, to ensure that they are being run before any other watchers |
|
|
1530 | after the poll. Also, <code>ev_check</code> watchers (and <code>ev_prepare</code> watchers, |
|
|
1531 | too) should not activate ("feed") events into libev. While libev fully |
|
|
1532 | supports this, they will be called before other <code>ev_check</code> watchers did |
|
|
1533 | their job. As <code>ev_check</code> watchers are often used to embed other event |
|
|
1534 | loops those other event loops might be in an unusable state until their |
|
|
1535 | <code>ev_check</code> watcher ran (always remind yourself to coexist peacefully with |
|
|
1536 | others).</p> |
1488 | <dl> |
1537 | <dl> |
1489 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1538 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1490 | <dt>ev_check_init (ev_check *, callback)</dt> |
1539 | <dt>ev_check_init (ev_check *, callback)</dt> |
1491 | <dd> |
1540 | <dd> |
1492 | <p>Initialises and configures the prepare or check watcher - they have no |
1541 | <p>Initialises and configures the prepare or check watcher - they have no |
1493 | parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> |
1542 | parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> |
1494 | macros, but using them is utterly, utterly and completely pointless.</p> |
1543 | macros, but using them is utterly, utterly and completely pointless.</p> |
1495 | </dd> |
1544 | </dd> |
1496 | </dl> |
1545 | </dl> |
1497 | <p>Example: To include a library such as adns, you would add IO watchers |
1546 | <p>There are a number of principal ways to embed other event loops or modules |
1498 | and a timeout watcher in a prepare handler, as required by libadns, and |
1547 | into libev. Here are some ideas on how to include libadns into libev |
|
|
1548 | (there is a Perl module named <code>EV::ADNS</code> that does this, which you could |
|
|
1549 | use for an actually working example. Another Perl module named <code>EV::Glib</code> |
|
|
1550 | embeds a Glib main context into libev, and finally, <code>Glib::EV</code> embeds EV |
|
|
1551 | into the Glib event loop).</p> |
|
|
1552 | <p>Method 1: Add IO watchers and a timeout watcher in a prepare handler, |
1499 | in a check watcher, destroy them and call into libadns. What follows is |
1553 | and in a check watcher, destroy them and call into libadns. What follows |
1500 | pseudo-code only of course:</p> |
1554 | is pseudo-code only of course. This requires you to either use a low |
|
|
1555 | priority for the check watcher or use <code>ev_clear_pending</code> explicitly, as |
|
|
1556 | the callbacks for the IO/timeout watchers might not have been called yet.</p> |
1501 | <pre> static ev_io iow [nfd]; |
1557 | <pre> static ev_io iow [nfd]; |
1502 | static ev_timer tw; |
1558 | static ev_timer tw; |
1503 | |
1559 | |
1504 | static void |
1560 | static void |
1505 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1561 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1506 | { |
1562 | { |
1507 | // set the relevant poll flags |
|
|
1508 | // could also call adns_processreadable etc. here |
|
|
1509 | struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1510 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1511 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1512 | } |
1563 | } |
1513 | |
1564 | |
1514 | // create io watchers for each fd and a timer before blocking |
1565 | // create io watchers for each fd and a timer before blocking |
1515 | static void |
1566 | static void |
1516 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1567 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
… | |
… | |
1522 | |
1573 | |
1523 | /* the callback is illegal, but won't be called as we stop during check */ |
1574 | /* the callback is illegal, but won't be called as we stop during check */ |
1524 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1575 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1525 | ev_timer_start (loop, &tw); |
1576 | ev_timer_start (loop, &tw); |
1526 | |
1577 | |
1527 | // create on ev_io per pollfd |
1578 | // create one ev_io per pollfd |
1528 | for (int i = 0; i < nfd; ++i) |
1579 | for (int i = 0; i < nfd; ++i) |
1529 | { |
1580 | { |
1530 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1581 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1531 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1582 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1532 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1583 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1533 | |
1584 | |
1534 | fds [i].revents = 0; |
1585 | fds [i].revents = 0; |
1535 | iow [i].data = fds + i; |
|
|
1536 | ev_io_start (loop, iow + i); |
1586 | ev_io_start (loop, iow + i); |
1537 | } |
1587 | } |
1538 | } |
1588 | } |
1539 | |
1589 | |
1540 | // stop all watchers after blocking |
1590 | // stop all watchers after blocking |
… | |
… | |
1542 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1592 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1543 | { |
1593 | { |
1544 | ev_timer_stop (loop, &tw); |
1594 | ev_timer_stop (loop, &tw); |
1545 | |
1595 | |
1546 | for (int i = 0; i < nfd; ++i) |
1596 | for (int i = 0; i < nfd; ++i) |
|
|
1597 | { |
|
|
1598 | // set the relevant poll flags |
|
|
1599 | // could also call adns_processreadable etc. here |
|
|
1600 | struct pollfd *fd = fds + i; |
|
|
1601 | int revents = ev_clear_pending (iow + i); |
|
|
1602 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1603 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1604 | |
|
|
1605 | // now stop the watcher |
1547 | ev_io_stop (loop, iow + i); |
1606 | ev_io_stop (loop, iow + i); |
|
|
1607 | } |
1548 | |
1608 | |
1549 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
1609 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1610 | } |
|
|
1611 | |
|
|
1612 | </pre> |
|
|
1613 | <p>Method 2: This would be just like method 1, but you run <code>adns_afterpoll</code> |
|
|
1614 | in the prepare watcher and would dispose of the check watcher.</p> |
|
|
1615 | <p>Method 3: If the module to be embedded supports explicit event |
|
|
1616 | notification (adns does), you can also make use of the actual watcher |
|
|
1617 | callbacks, and only destroy/create the watchers in the prepare watcher.</p> |
|
|
1618 | <pre> static void |
|
|
1619 | timer_cb (EV_P_ ev_timer *w, int revents) |
|
|
1620 | { |
|
|
1621 | adns_state ads = (adns_state)w->data; |
|
|
1622 | update_now (EV_A); |
|
|
1623 | |
|
|
1624 | adns_processtimeouts (ads, &tv_now); |
|
|
1625 | } |
|
|
1626 | |
|
|
1627 | static void |
|
|
1628 | io_cb (EV_P_ ev_io *w, int revents) |
|
|
1629 | { |
|
|
1630 | adns_state ads = (adns_state)w->data; |
|
|
1631 | update_now (EV_A); |
|
|
1632 | |
|
|
1633 | if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now); |
|
|
1634 | if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now); |
|
|
1635 | } |
|
|
1636 | |
|
|
1637 | // do not ever call adns_afterpoll |
|
|
1638 | |
|
|
1639 | </pre> |
|
|
1640 | <p>Method 4: Do not use a prepare or check watcher because the module you |
|
|
1641 | want to embed is too inflexible to support it. Instead, youc na override |
|
|
1642 | their poll function. The drawback with this solution is that the main |
|
|
1643 | loop is now no longer controllable by EV. The <code>Glib::EV</code> module does |
|
|
1644 | this.</p> |
|
|
1645 | <pre> static gint |
|
|
1646 | event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
|
|
1647 | { |
|
|
1648 | int got_events = 0; |
|
|
1649 | |
|
|
1650 | for (n = 0; n < nfds; ++n) |
|
|
1651 | // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
|
|
1652 | |
|
|
1653 | if (timeout >= 0) |
|
|
1654 | // create/start timer |
|
|
1655 | |
|
|
1656 | // poll |
|
|
1657 | ev_loop (EV_A_ 0); |
|
|
1658 | |
|
|
1659 | // stop timer again |
|
|
1660 | if (timeout >= 0) |
|
|
1661 | ev_timer_stop (EV_A_ &to); |
|
|
1662 | |
|
|
1663 | // stop io watchers again - their callbacks should have set |
|
|
1664 | for (n = 0; n < nfds; ++n) |
|
|
1665 | ev_io_stop (EV_A_ iow [n]); |
|
|
1666 | |
|
|
1667 | return got_events; |
1550 | } |
1668 | } |
1551 | |
1669 | |
1552 | |
1670 | |
1553 | |
1671 | |
1554 | |
1672 | |