… | |
… | |
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="Thu Nov 29 18:28:02 2007" /> |
9 | <meta name="created" content="Sat Dec 8 23:11:11 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 --> |
… | |
… | |
119 | </pre> |
119 | </pre> |
120 | |
120 | |
121 | </div> |
121 | </div> |
122 | <h1 id="DESCRIPTION">DESCRIPTION</h1> |
122 | <h1 id="DESCRIPTION">DESCRIPTION</h1> |
123 | <div id="DESCRIPTION_CONTENT"> |
123 | <div id="DESCRIPTION_CONTENT"> |
|
|
124 | <p>The newest version of this document is also available as a html-formatted |
|
|
125 | web page you might find easier to navigate when reading it for the first |
|
|
126 | time: <a href="http://cvs.schmorp.de/libev/ev.html">http://cvs.schmorp.de/libev/ev.html</a>.</p> |
124 | <p>Libev is an event loop: you register interest in certain events (such as a |
127 | <p>Libev is an event loop: you register interest in certain events (such as a |
125 | file descriptor being readable or a timeout occuring), and it will manage |
128 | file descriptor being readable or a timeout occuring), and it will manage |
126 | these event sources and provide your program with events.</p> |
129 | these event sources and provide your program with events.</p> |
127 | <p>To do this, it must take more or less complete control over your process |
130 | <p>To do this, it must take more or less complete control over your process |
128 | (or thread) by executing the <i>event loop</i> handler, and will then |
131 | (or thread) by executing the <i>event loop</i> handler, and will then |
… | |
… | |
333 | <p>Instead of calling <code>ev_default_fork</code> or <code>ev_loop_fork</code> manually after |
336 | <p>Instead of calling <code>ev_default_fork</code> or <code>ev_loop_fork</code> manually after |
334 | a fork, you can also make libev check for a fork in each iteration by |
337 | a fork, you can also make libev check for a fork in each iteration by |
335 | enabling this flag.</p> |
338 | enabling this flag.</p> |
336 | <p>This works by calling <code>getpid ()</code> on every iteration of the loop, |
339 | <p>This works by calling <code>getpid ()</code> on every iteration of the loop, |
337 | and thus this might slow down your event loop if you do a lot of loop |
340 | and thus this might slow down your event loop if you do a lot of loop |
338 | iterations and little real work, but is usually not noticable (on my |
341 | iterations and little real work, but is usually not noticeable (on my |
339 | Linux system for example, <code>getpid</code> is actually a simple 5-insn sequence |
342 | Linux system for example, <code>getpid</code> is actually a simple 5-insn sequence |
340 | without a syscall and thus <i>very</i> fast, but my Linux system also has |
343 | without a syscall and thus <i>very</i> fast, but my Linux system also has |
341 | <code>pthread_atfork</code> which is even faster).</p> |
344 | <code>pthread_atfork</code> which is even faster).</p> |
342 | <p>The big advantage of this flag is that you can forget about fork (and |
345 | <p>The big advantage of this flag is that you can forget about fork (and |
343 | forget about forgetting to tell libev about forking) when you use this |
346 | forget about forgetting to tell libev about forking) when you use this |
… | |
… | |
480 | <dt>ev_loop_fork (loop)</dt> |
483 | <dt>ev_loop_fork (loop)</dt> |
481 | <dd> |
484 | <dd> |
482 | <p>Like <code>ev_default_fork</code>, but acts on an event loop created by |
485 | <p>Like <code>ev_default_fork</code>, but acts on an event loop created by |
483 | <code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop |
486 | <code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop |
484 | after fork, and how you do this is entirely your own problem.</p> |
487 | after fork, and how you do this is entirely your own problem.</p> |
|
|
488 | </dd> |
|
|
489 | <dt>unsigned int ev_loop_count (loop)</dt> |
|
|
490 | <dd> |
|
|
491 | <p>Returns the count of loop iterations for the loop, which is identical to |
|
|
492 | the number of times libev did poll for new events. It starts at <code>0</code> and |
|
|
493 | happily wraps around with enough iterations.</p> |
|
|
494 | <p>This value can sometimes be useful as a generation counter of sorts (it |
|
|
495 | "ticks" the number of loop iterations), as it roughly corresponds with |
|
|
496 | <code>ev_prepare</code> and <code>ev_check</code> calls.</p> |
485 | </dd> |
497 | </dd> |
486 | <dt>unsigned int ev_backend (loop)</dt> |
498 | <dt>unsigned int ev_backend (loop)</dt> |
487 | <dd> |
499 | <dd> |
488 | <p>Returns one of the <code>EVBACKEND_*</code> flags indicating the event backend in |
500 | <p>Returns one of the <code>EVBACKEND_*</code> flags indicating the event backend in |
489 | use.</p> |
501 | use.</p> |
… | |
… | |
517 | one iteration of the loop. This is useful if you are waiting for some |
529 | one iteration of the loop. This is useful if you are waiting for some |
518 | external event in conjunction with something not expressible using other |
530 | external event in conjunction with something not expressible using other |
519 | libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is |
531 | libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is |
520 | usually a better approach for this kind of thing.</p> |
532 | usually a better approach for this kind of thing.</p> |
521 | <p>Here are the gory details of what <code>ev_loop</code> does:</p> |
533 | <p>Here are the gory details of what <code>ev_loop</code> does:</p> |
|
|
534 | <pre> - Before the first iteration, call any pending watchers. |
522 | <pre> * If there are no active watchers (reference count is zero), return. |
535 | * If there are no active watchers (reference count is zero), return. |
523 | - Queue prepare watchers and then call all outstanding watchers. |
536 | - Queue all prepare watchers and then call all outstanding watchers. |
524 | - If we have been forked, recreate the kernel state. |
537 | - If we have been forked, recreate the kernel state. |
525 | - Update the kernel state with all outstanding changes. |
538 | - Update the kernel state with all outstanding changes. |
526 | - Update the "event loop time". |
539 | - Update the "event loop time". |
527 | - Calculate for how long to block. |
540 | - Calculate for how long to block. |
528 | - Block the process, waiting for any events. |
541 | - Block the process, waiting for any events. |
… | |
… | |
757 | <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> |
770 | <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> |
758 | <dd> |
771 | <dd> |
759 | <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding |
772 | <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding |
760 | events but its callback has not yet been invoked). As long as a watcher |
773 | events but its callback has not yet been invoked). As long as a watcher |
761 | is pending (but not active) you must not call an init function on it (but |
774 | is pending (but not active) you must not call an init function on it (but |
762 | <code>ev_TYPE_set</code> is safe) and you must make sure the watcher is available to |
775 | <code>ev_TYPE_set</code> is safe), you must not change its priority, and you must |
763 | libev (e.g. you cnanot <code>free ()</code> it).</p> |
776 | make sure the watcher is available to libev (e.g. you cannot <code>free ()</code> |
|
|
777 | it).</p> |
764 | </dd> |
778 | </dd> |
765 | <dt>callback ev_cb (ev_TYPE *watcher)</dt> |
779 | <dt>callback ev_cb (ev_TYPE *watcher)</dt> |
766 | <dd> |
780 | <dd> |
767 | <p>Returns the callback currently set on the watcher.</p> |
781 | <p>Returns the callback currently set on the watcher.</p> |
768 | </dd> |
782 | </dd> |
769 | <dt>ev_cb_set (ev_TYPE *watcher, callback)</dt> |
783 | <dt>ev_cb_set (ev_TYPE *watcher, callback)</dt> |
770 | <dd> |
784 | <dd> |
771 | <p>Change the callback. You can change the callback at virtually any time |
785 | <p>Change the callback. You can change the callback at virtually any time |
772 | (modulo threads).</p> |
786 | (modulo threads).</p> |
|
|
787 | </dd> |
|
|
788 | <dt>ev_set_priority (ev_TYPE *watcher, priority)</dt> |
|
|
789 | <dt>int ev_priority (ev_TYPE *watcher)</dt> |
|
|
790 | <dd> |
|
|
791 | <p>Set and query the priority of the watcher. The priority is a small |
|
|
792 | integer between <code>EV_MAXPRI</code> (default: <code>2</code>) and <code>EV_MINPRI</code> |
|
|
793 | (default: <code>-2</code>). Pending watchers with higher priority will be invoked |
|
|
794 | before watchers with lower priority, but priority will not keep watchers |
|
|
795 | from being executed (except for <code>ev_idle</code> watchers).</p> |
|
|
796 | <p>This means that priorities are <i>only</i> used for ordering callback |
|
|
797 | invocation after new events have been received. This is useful, for |
|
|
798 | example, to reduce latency after idling, or more often, to bind two |
|
|
799 | watchers on the same event and make sure one is called first.</p> |
|
|
800 | <p>If you need to suppress invocation when higher priority events are pending |
|
|
801 | you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p> |
|
|
802 | <p>You <i>must not</i> change the priority of a watcher as long as it is active or |
|
|
803 | pending.</p> |
|
|
804 | <p>The default priority used by watchers when no priority has been set is |
|
|
805 | always <code>0</code>, which is supposed to not be too high and not be too low :).</p> |
|
|
806 | <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is |
|
|
807 | fine, as long as you do not mind that the priority value you query might |
|
|
808 | or might not have been adjusted to be within valid range.</p> |
|
|
809 | </dd> |
|
|
810 | <dt>ev_invoke (loop, ev_TYPE *watcher, int revents)</dt> |
|
|
811 | <dd> |
|
|
812 | <p>Invoke the <code>watcher</code> with the given <code>loop</code> and <code>revents</code>. Neither |
|
|
813 | <code>loop</code> nor <code>revents</code> need to be valid as long as the watcher callback |
|
|
814 | can deal with that fact.</p> |
|
|
815 | </dd> |
|
|
816 | <dt>int ev_clear_pending (loop, ev_TYPE *watcher)</dt> |
|
|
817 | <dd> |
|
|
818 | <p>If the watcher is pending, this function returns clears its pending status |
|
|
819 | and returns its <code>revents</code> bitset (as if its callback was invoked). If the |
|
|
820 | watcher isn't pending it does nothing and returns <code>0</code>.</p> |
773 | </dd> |
821 | </dd> |
774 | </dl> |
822 | </dl> |
775 | |
823 | |
776 | |
824 | |
777 | |
825 | |
… | |
… | |
888 | this situation even with a relatively standard program structure. Thus |
936 | this situation even with a relatively standard program structure. Thus |
889 | it is best to always use non-blocking I/O: An extra <code>read</code>(2) returning |
937 | it is best to always use non-blocking I/O: An extra <code>read</code>(2) returning |
890 | <code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p> |
938 | <code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p> |
891 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
939 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
892 | play around with an Xlib connection), then you have to seperately re-test |
940 | play around with an Xlib connection), then you have to seperately re-test |
893 | wether a file descriptor is really ready with a known-to-be good interface |
941 | whether a file descriptor is really ready with a known-to-be good interface |
894 | such as poll (fortunately in our Xlib example, Xlib already does this on |
942 | such as poll (fortunately in our Xlib example, Xlib already does this on |
895 | its own, so its quite safe to use).</p> |
943 | its own, so its quite safe to use).</p> |
896 | <dl> |
944 | <dl> |
897 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
945 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
898 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
946 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
… | |
… | |
1358 | </pre> |
1406 | </pre> |
1359 | |
1407 | |
1360 | </div> |
1408 | </div> |
1361 | <h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</h2> |
1409 | <h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</h2> |
1362 | <div id="code_ev_idle_code_when_you_ve_got_no-2"> |
1410 | <div id="code_ev_idle_code_when_you_ve_got_no-2"> |
1363 | <p>Idle watchers trigger events when there are no other events are pending |
1411 | <p>Idle watchers trigger events when no other events of the same or higher |
1364 | (prepare, check and other idle watchers do not count). That is, as long |
1412 | priority are pending (prepare, check and other idle watchers do not |
1365 | as your process is busy handling sockets or timeouts (or even signals, |
1413 | count).</p> |
1366 | imagine) it will not be triggered. But when your process is idle all idle |
1414 | <p>That is, as long as your process is busy handling sockets or timeouts |
1367 | watchers are being called again and again, once per event loop iteration - |
1415 | (or even signals, imagine) of the same or higher priority it will not be |
|
|
1416 | triggered. But when your process is idle (or only lower-priority watchers |
|
|
1417 | are pending), the idle watchers are being called once per event loop |
1368 | until stopped, that is, or your process receives more events and becomes |
1418 | iteration - until stopped, that is, or your process receives more events |
1369 | busy.</p> |
1419 | and becomes busy again with higher priority stuff.</p> |
1370 | <p>The most noteworthy effect is that as long as any idle watchers are |
1420 | <p>The most noteworthy effect is that as long as any idle watchers are |
1371 | active, the process will not block when waiting for new events.</p> |
1421 | active, the process will not block when waiting for new events.</p> |
1372 | <p>Apart from keeping your process non-blocking (which is a useful |
1422 | <p>Apart from keeping your process non-blocking (which is a useful |
1373 | effect on its own sometimes), idle watchers are a good place to do |
1423 | effect on its own sometimes), idle watchers are a good place to do |
1374 | "pseudo-background processing", or delay processing stuff to after the |
1424 | "pseudo-background processing", or delay processing stuff to after the |
… | |
… | |
1434 | are ready to run (it's actually more complicated: it only runs coroutines |
1484 | are ready to run (it's actually more complicated: it only runs coroutines |
1435 | with priority higher than or equal to the event loop and one coroutine |
1485 | with priority higher than or equal to the event loop and one coroutine |
1436 | of lower priority, but only once, using idle watchers to keep the event |
1486 | of lower priority, but only once, using idle watchers to keep the event |
1437 | loop from blocking if lower-priority coroutines are active, thus mapping |
1487 | loop from blocking if lower-priority coroutines are active, thus mapping |
1438 | low-priority coroutines to idle/background tasks).</p> |
1488 | low-priority coroutines to idle/background tasks).</p> |
|
|
1489 | <p>It is recommended to give <code>ev_check</code> watchers highest (<code>EV_MAXPRI</code>) |
|
|
1490 | priority, to ensure that they are being run before any other watchers |
|
|
1491 | after the poll. Also, <code>ev_check</code> watchers (and <code>ev_prepare</code> watchers, |
|
|
1492 | too) should not activate ("feed") events into libev. While libev fully |
|
|
1493 | supports this, they will be called before other <code>ev_check</code> watchers did |
|
|
1494 | their job. As <code>ev_check</code> watchers are often used to embed other event |
|
|
1495 | loops those other event loops might be in an unusable state until their |
|
|
1496 | <code>ev_check</code> watcher ran (always remind yourself to coexist peacefully with |
|
|
1497 | others).</p> |
1439 | <dl> |
1498 | <dl> |
1440 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1499 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1441 | <dt>ev_check_init (ev_check *, callback)</dt> |
1500 | <dt>ev_check_init (ev_check *, callback)</dt> |
1442 | <dd> |
1501 | <dd> |
1443 | <p>Initialises and configures the prepare or check watcher - they have no |
1502 | <p>Initialises and configures the prepare or check watcher - they have no |
1444 | parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> |
1503 | parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> |
1445 | macros, but using them is utterly, utterly and completely pointless.</p> |
1504 | macros, but using them is utterly, utterly and completely pointless.</p> |
1446 | </dd> |
1505 | </dd> |
1447 | </dl> |
1506 | </dl> |
1448 | <p>Example: To include a library such as adns, you would add IO watchers |
1507 | <p>There are a number of principal ways to embed other event loops or modules |
1449 | and a timeout watcher in a prepare handler, as required by libadns, and |
1508 | into libev. Here are some ideas on how to include libadns into libev |
|
|
1509 | (there is a Perl module named <code>EV::ADNS</code> that does this, which you could |
|
|
1510 | use for an actually working example. Another Perl module named <code>EV::Glib</code> |
|
|
1511 | embeds a Glib main context into libev, and finally, <code>Glib::EV</code> embeds EV |
|
|
1512 | into the Glib event loop).</p> |
|
|
1513 | <p>Method 1: Add IO watchers and a timeout watcher in a prepare handler, |
1450 | in a check watcher, destroy them and call into libadns. What follows is |
1514 | and in a check watcher, destroy them and call into libadns. What follows |
1451 | pseudo-code only of course:</p> |
1515 | is pseudo-code only of course. This requires you to either use a low |
|
|
1516 | priority for the check watcher or use <code>ev_clear_pending</code> explicitly, as |
|
|
1517 | the callbacks for the IO/timeout watchers might not have been called yet.</p> |
1452 | <pre> static ev_io iow [nfd]; |
1518 | <pre> static ev_io iow [nfd]; |
1453 | static ev_timer tw; |
1519 | static ev_timer tw; |
1454 | |
1520 | |
1455 | static void |
1521 | static void |
1456 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1522 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1457 | { |
1523 | { |
1458 | // set the relevant poll flags |
|
|
1459 | // could also call adns_processreadable etc. here |
|
|
1460 | struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1461 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1462 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1463 | } |
1524 | } |
1464 | |
1525 | |
1465 | // create io watchers for each fd and a timer before blocking |
1526 | // create io watchers for each fd and a timer before blocking |
1466 | static void |
1527 | static void |
1467 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1528 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1468 | { |
1529 | { |
1469 | int timeout = 3600000;truct pollfd fds [nfd]; |
1530 | int timeout = 3600000; |
|
|
1531 | struct pollfd fds [nfd]; |
1470 | // actual code will need to loop here and realloc etc. |
1532 | // actual code will need to loop here and realloc etc. |
1471 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1533 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1472 | |
1534 | |
1473 | /* the callback is illegal, but won't be called as we stop during check */ |
1535 | /* the callback is illegal, but won't be called as we stop during check */ |
1474 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1536 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1475 | ev_timer_start (loop, &tw); |
1537 | ev_timer_start (loop, &tw); |
1476 | |
1538 | |
1477 | // create on ev_io per pollfd |
1539 | // create one ev_io per pollfd |
1478 | for (int i = 0; i < nfd; ++i) |
1540 | for (int i = 0; i < nfd; ++i) |
1479 | { |
1541 | { |
1480 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1542 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1481 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1543 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1482 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1544 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1483 | |
1545 | |
1484 | fds [i].revents = 0; |
1546 | fds [i].revents = 0; |
1485 | iow [i].data = fds + i; |
|
|
1486 | ev_io_start (loop, iow + i); |
1547 | ev_io_start (loop, iow + i); |
1487 | } |
1548 | } |
1488 | } |
1549 | } |
1489 | |
1550 | |
1490 | // stop all watchers after blocking |
1551 | // stop all watchers after blocking |
… | |
… | |
1492 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1553 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1493 | { |
1554 | { |
1494 | ev_timer_stop (loop, &tw); |
1555 | ev_timer_stop (loop, &tw); |
1495 | |
1556 | |
1496 | for (int i = 0; i < nfd; ++i) |
1557 | for (int i = 0; i < nfd; ++i) |
|
|
1558 | { |
|
|
1559 | // set the relevant poll flags |
|
|
1560 | // could also call adns_processreadable etc. here |
|
|
1561 | struct pollfd *fd = fds + i; |
|
|
1562 | int revents = ev_clear_pending (iow + i); |
|
|
1563 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1564 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1565 | |
|
|
1566 | // now stop the watcher |
1497 | ev_io_stop (loop, iow + i); |
1567 | ev_io_stop (loop, iow + i); |
|
|
1568 | } |
1498 | |
1569 | |
1499 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
1570 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1571 | } |
|
|
1572 | |
|
|
1573 | </pre> |
|
|
1574 | <p>Method 2: This would be just like method 1, but you run <code>adns_afterpoll</code> |
|
|
1575 | in the prepare watcher and would dispose of the check watcher.</p> |
|
|
1576 | <p>Method 3: If the module to be embedded supports explicit event |
|
|
1577 | notification (adns does), you can also make use of the actual watcher |
|
|
1578 | callbacks, and only destroy/create the watchers in the prepare watcher.</p> |
|
|
1579 | <pre> static void |
|
|
1580 | timer_cb (EV_P_ ev_timer *w, int revents) |
|
|
1581 | { |
|
|
1582 | adns_state ads = (adns_state)w->data; |
|
|
1583 | update_now (EV_A); |
|
|
1584 | |
|
|
1585 | adns_processtimeouts (ads, &tv_now); |
|
|
1586 | } |
|
|
1587 | |
|
|
1588 | static void |
|
|
1589 | io_cb (EV_P_ ev_io *w, int revents) |
|
|
1590 | { |
|
|
1591 | adns_state ads = (adns_state)w->data; |
|
|
1592 | update_now (EV_A); |
|
|
1593 | |
|
|
1594 | if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now); |
|
|
1595 | if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now); |
|
|
1596 | } |
|
|
1597 | |
|
|
1598 | // do not ever call adns_afterpoll |
|
|
1599 | |
|
|
1600 | </pre> |
|
|
1601 | <p>Method 4: Do not use a prepare or check watcher because the module you |
|
|
1602 | want to embed is too inflexible to support it. Instead, youc na override |
|
|
1603 | their poll function. The drawback with this solution is that the main |
|
|
1604 | loop is now no longer controllable by EV. The <code>Glib::EV</code> module does |
|
|
1605 | this.</p> |
|
|
1606 | <pre> static gint |
|
|
1607 | event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
|
|
1608 | { |
|
|
1609 | int got_events = 0; |
|
|
1610 | |
|
|
1611 | for (n = 0; n < nfds; ++n) |
|
|
1612 | // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
|
|
1613 | |
|
|
1614 | if (timeout >= 0) |
|
|
1615 | // create/start timer |
|
|
1616 | |
|
|
1617 | // poll |
|
|
1618 | ev_loop (EV_A_ 0); |
|
|
1619 | |
|
|
1620 | // stop timer again |
|
|
1621 | if (timeout >= 0) |
|
|
1622 | ev_timer_stop (EV_A_ &to); |
|
|
1623 | |
|
|
1624 | // stop io watchers again - their callbacks should have set |
|
|
1625 | for (n = 0; n < nfds; ++n) |
|
|
1626 | ev_io_stop (EV_A_ iow [n]); |
|
|
1627 | |
|
|
1628 | return got_events; |
1500 | } |
1629 | } |
1501 | |
1630 | |
1502 | |
1631 | |
1503 | |
1632 | |
1504 | |
1633 | |
… | |
… | |
1701 | the callback model to a model using method callbacks on objects.</p> |
1830 | the callback model to a model using method callbacks on objects.</p> |
1702 | <p>To use it,</p> |
1831 | <p>To use it,</p> |
1703 | <pre> #include <ev++.h> |
1832 | <pre> #include <ev++.h> |
1704 | |
1833 | |
1705 | </pre> |
1834 | </pre> |
1706 | <p>(it is not installed by default). This automatically includes <cite>ev.h</cite> |
1835 | <p>This automatically includes <cite>ev.h</cite> and puts all of its definitions (many |
1707 | and puts all of its definitions (many of them macros) into the global |
1836 | of them macros) into the global namespace. All C++ specific things are |
1708 | namespace. All C++ specific things are put into the <code>ev</code> namespace.</p> |
1837 | put into the <code>ev</code> namespace. It should support all the same embedding |
1709 | <p>It should support all the same embedding options as <cite>ev.h</cite>, most notably |
1838 | options as <cite>ev.h</cite>, most notably <code>EV_MULTIPLICITY</code>.</p> |
1710 | <code>EV_MULTIPLICITY</code>.</p> |
1839 | <p>Care has been taken to keep the overhead low. The only data member the C++ |
|
|
1840 | classes add (compared to plain C-style watchers) is the event loop pointer |
|
|
1841 | that the watcher is associated with (or no additional members at all if |
|
|
1842 | you disable <code>EV_MULTIPLICITY</code> when embedding libev).</p> |
|
|
1843 | <p>Currently, functions, and static and non-static member functions can be |
|
|
1844 | used as callbacks. Other types should be easy to add as long as they only |
|
|
1845 | need one additional pointer for context. If you need support for other |
|
|
1846 | types of functors please contact the author (preferably after implementing |
|
|
1847 | it).</p> |
1711 | <p>Here is a list of things available in the <code>ev</code> namespace:</p> |
1848 | <p>Here is a list of things available in the <code>ev</code> namespace:</p> |
1712 | <dl> |
1849 | <dl> |
1713 | <dt><code>ev::READ</code>, <code>ev::WRITE</code> etc.</dt> |
1850 | <dt><code>ev::READ</code>, <code>ev::WRITE</code> etc.</dt> |
1714 | <dd> |
1851 | <dd> |
1715 | <p>These are just enum values with the same values as the <code>EV_READ</code> etc. |
1852 | <p>These are just enum values with the same values as the <code>EV_READ</code> etc. |
… | |
… | |
1726 | which is called <code>ev::sig</code> to avoid clashes with the <code>signal</code> macro |
1863 | which is called <code>ev::sig</code> to avoid clashes with the <code>signal</code> macro |
1727 | defines by many implementations.</p> |
1864 | defines by many implementations.</p> |
1728 | <p>All of those classes have these methods:</p> |
1865 | <p>All of those classes have these methods:</p> |
1729 | <p> |
1866 | <p> |
1730 | <dl> |
1867 | <dl> |
1731 | <dt>ev::TYPE::TYPE (object *, object::method *)</dt> |
1868 | <dt>ev::TYPE::TYPE ()</dt> |
1732 | <dt>ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)</dt> |
1869 | <dt>ev::TYPE::TYPE (struct ev_loop *)</dt> |
1733 | <dt>ev::TYPE::~TYPE</dt> |
1870 | <dt>ev::TYPE::~TYPE</dt> |
1734 | <dd> |
1871 | <dd> |
1735 | <p>The constructor takes a pointer to an object and a method pointer to |
1872 | <p>The constructor (optionally) takes an event loop to associate the watcher |
1736 | the event handler callback to call in this class. The constructor calls |
1873 | with. If it is omitted, it will use <code>EV_DEFAULT</code>.</p> |
1737 | <code>ev_init</code> for you, which means you have to call the <code>set</code> method |
1874 | <p>The constructor calls <code>ev_init</code> for you, which means you have to call the |
1738 | before starting it. If you do not specify a loop then the constructor |
1875 | <code>set</code> method before starting it.</p> |
1739 | automatically associates the default loop with this watcher.</p> |
1876 | <p>It will not set a callback, however: You have to call the templated <code>set</code> |
|
|
1877 | method to set a callback before you can start the watcher.</p> |
|
|
1878 | <p>(The reason why you have to use a method is a limitation in C++ which does |
|
|
1879 | not allow explicit template arguments for constructors).</p> |
1740 | <p>The destructor automatically stops the watcher if it is active.</p> |
1880 | <p>The destructor automatically stops the watcher if it is active.</p> |
|
|
1881 | </dd> |
|
|
1882 | <dt>w->set<class, &class::method> (object *)</dt> |
|
|
1883 | <dd> |
|
|
1884 | <p>This method sets the callback method to call. The method has to have a |
|
|
1885 | signature of <code>void (*)(ev_TYPE &, int)</code>, it receives the watcher as |
|
|
1886 | first argument and the <code>revents</code> as second. The object must be given as |
|
|
1887 | parameter and is stored in the <code>data</code> member of the watcher.</p> |
|
|
1888 | <p>This method synthesizes efficient thunking code to call your method from |
|
|
1889 | the C callback that libev requires. If your compiler can inline your |
|
|
1890 | callback (i.e. it is visible to it at the place of the <code>set</code> call and |
|
|
1891 | your compiler is good :), then the method will be fully inlined into the |
|
|
1892 | thunking function, making it as fast as a direct C callback.</p> |
|
|
1893 | <p>Example: simple class declaration and watcher initialisation</p> |
|
|
1894 | <pre> struct myclass |
|
|
1895 | { |
|
|
1896 | void io_cb (ev::io &w, int revents) { } |
|
|
1897 | } |
|
|
1898 | |
|
|
1899 | myclass obj; |
|
|
1900 | ev::io iow; |
|
|
1901 | iow.set <myclass, &myclass::io_cb> (&obj); |
|
|
1902 | |
|
|
1903 | </pre> |
|
|
1904 | </dd> |
|
|
1905 | <dt>w->set<function> (void *data = 0)</dt> |
|
|
1906 | <dd> |
|
|
1907 | <p>Also sets a callback, but uses a static method or plain function as |
|
|
1908 | callback. The optional <code>data</code> argument will be stored in the watcher's |
|
|
1909 | <code>data</code> member and is free for you to use.</p> |
|
|
1910 | <p>The prototype of the <code>function</code> must be <code>void (*)(ev::TYPE &w, int)</code>.</p> |
|
|
1911 | <p>See the method-<code>set</code> above for more details.</p> |
|
|
1912 | <p>Example:</p> |
|
|
1913 | <pre> static void io_cb (ev::io &w, int revents) { } |
|
|
1914 | iow.set <io_cb> (); |
|
|
1915 | |
|
|
1916 | </pre> |
1741 | </dd> |
1917 | </dd> |
1742 | <dt>w->set (struct ev_loop *)</dt> |
1918 | <dt>w->set (struct ev_loop *)</dt> |
1743 | <dd> |
1919 | <dd> |
1744 | <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only |
1920 | <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only |
1745 | do this when the watcher is inactive (and not pending either).</p> |
1921 | do this when the watcher is inactive (and not pending either).</p> |
1746 | </dd> |
1922 | </dd> |
1747 | <dt>w->set ([args])</dt> |
1923 | <dt>w->set ([args])</dt> |
1748 | <dd> |
1924 | <dd> |
1749 | <p>Basically the same as <code>ev_TYPE_set</code>, with the same args. Must be |
1925 | <p>Basically the same as <code>ev_TYPE_set</code>, with the same args. Must be |
1750 | called at least once. Unlike the C counterpart, an active watcher gets |
1926 | called at least once. Unlike the C counterpart, an active watcher gets |
1751 | automatically stopped and restarted.</p> |
1927 | automatically stopped and restarted when reconfiguring it with this |
|
|
1928 | method.</p> |
1752 | </dd> |
1929 | </dd> |
1753 | <dt>w->start ()</dt> |
1930 | <dt>w->start ()</dt> |
1754 | <dd> |
1931 | <dd> |
1755 | <p>Starts the watcher. Note that there is no <code>loop</code> argument as the |
1932 | <p>Starts the watcher. Note that there is no <code>loop</code> argument, as the |
1756 | constructor already takes the loop.</p> |
1933 | constructor already stores the event loop.</p> |
1757 | </dd> |
1934 | </dd> |
1758 | <dt>w->stop ()</dt> |
1935 | <dt>w->stop ()</dt> |
1759 | <dd> |
1936 | <dd> |
1760 | <p>Stops the watcher if it is active. Again, no <code>loop</code> argument.</p> |
1937 | <p>Stops the watcher if it is active. Again, no <code>loop</code> argument.</p> |
1761 | </dd> |
1938 | </dd> |
… | |
… | |
1785 | |
1962 | |
1786 | myclass (); |
1963 | myclass (); |
1787 | } |
1964 | } |
1788 | |
1965 | |
1789 | myclass::myclass (int fd) |
1966 | myclass::myclass (int fd) |
1790 | : io (this, &myclass::io_cb), |
|
|
1791 | idle (this, &myclass::idle_cb) |
|
|
1792 | { |
1967 | { |
|
|
1968 | io .set <myclass, &myclass::io_cb > (this); |
|
|
1969 | idle.set <myclass, &myclass::idle_cb> (this); |
|
|
1970 | |
1793 | io.start (fd, ev::READ); |
1971 | io.start (fd, ev::READ); |
1794 | } |
1972 | } |
1795 | |
1973 | |
1796 | |
1974 | |
1797 | |
1975 | |
… | |
… | |
1800 | |
1978 | |
1801 | </div> |
1979 | </div> |
1802 | <h1 id="MACRO_MAGIC">MACRO MAGIC</h1> |
1980 | <h1 id="MACRO_MAGIC">MACRO MAGIC</h1> |
1803 | <div id="MACRO_MAGIC_CONTENT"> |
1981 | <div id="MACRO_MAGIC_CONTENT"> |
1804 | <p>Libev can be compiled with a variety of options, the most fundemantal is |
1982 | <p>Libev can be compiled with a variety of options, the most fundemantal is |
1805 | <code>EV_MULTIPLICITY</code>. This option determines wether (most) functions and |
1983 | <code>EV_MULTIPLICITY</code>. This option determines whether (most) functions and |
1806 | callbacks have an initial <code>struct ev_loop *</code> argument.</p> |
1984 | callbacks have an initial <code>struct ev_loop *</code> argument.</p> |
1807 | <p>To make it easier to write programs that cope with either variant, the |
1985 | <p>To make it easier to write programs that cope with either variant, the |
1808 | following macros are defined:</p> |
1986 | following macros are defined:</p> |
1809 | <dl> |
1987 | <dl> |
1810 | <dt><code>EV_A</code>, <code>EV_A_</code></dt> |
1988 | <dt><code>EV_A</code>, <code>EV_A_</code></dt> |
… | |
… | |
1839 | <dd> |
2017 | <dd> |
1840 | <p>Similar to the other two macros, this gives you the value of the default |
2018 | <p>Similar to the other two macros, this gives you the value of the default |
1841 | loop, if multiple loops are supported ("ev loop default").</p> |
2019 | loop, if multiple loops are supported ("ev loop default").</p> |
1842 | </dd> |
2020 | </dd> |
1843 | </dl> |
2021 | </dl> |
1844 | <p>Example: Declare and initialise a check watcher, working regardless of |
2022 | <p>Example: Declare and initialise a check watcher, utilising the above |
1845 | wether multiple loops are supported or not.</p> |
2023 | macros so it will work regardless of whether multiple loops are supported |
|
|
2024 | or not.</p> |
1846 | <pre> static void |
2025 | <pre> static void |
1847 | check_cb (EV_P_ ev_timer *w, int revents) |
2026 | check_cb (EV_P_ ev_timer *w, int revents) |
1848 | { |
2027 | { |
1849 | ev_check_stop (EV_A_ w); |
2028 | ev_check_stop (EV_A_ w); |
1850 | } |
2029 | } |
1851 | |
2030 | |
1852 | ev_check check; |
2031 | ev_check check; |
1853 | ev_check_init (&check, check_cb); |
2032 | ev_check_init (&check, check_cb); |
1854 | ev_check_start (EV_DEFAULT_ &check); |
2033 | ev_check_start (EV_DEFAULT_ &check); |
1855 | ev_loop (EV_DEFAULT_ 0); |
2034 | ev_loop (EV_DEFAULT_ 0); |
1856 | |
|
|
1857 | |
|
|
1858 | |
|
|
1859 | |
2035 | |
1860 | </pre> |
2036 | </pre> |
1861 | |
2037 | |
1862 | </div> |
2038 | </div> |
1863 | <h1 id="EMBEDDING">EMBEDDING</h1> |
2039 | <h1 id="EMBEDDING">EMBEDDING</h1> |
… | |
… | |
1905 | ev_vars.h |
2081 | ev_vars.h |
1906 | ev_wrap.h |
2082 | ev_wrap.h |
1907 | |
2083 | |
1908 | ev_win32.c required on win32 platforms only |
2084 | ev_win32.c required on win32 platforms only |
1909 | |
2085 | |
1910 | ev_select.c only when select backend is enabled (which is by default) |
2086 | ev_select.c only when select backend is enabled (which is enabled by default) |
1911 | ev_poll.c only when poll backend is enabled (disabled by default) |
2087 | ev_poll.c only when poll backend is enabled (disabled by default) |
1912 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
2088 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
1913 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
2089 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
1914 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
2090 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
1915 | |
2091 | |
… | |
… | |
2080 | will have the <code>struct ev_loop *</code> as first argument, and you can create |
2256 | will have the <code>struct ev_loop *</code> as first argument, and you can create |
2081 | additional independent event loops. Otherwise there will be no support |
2257 | additional independent event loops. Otherwise there will be no support |
2082 | for multiple event loops and there is no first event loop pointer |
2258 | for multiple event loops and there is no first event loop pointer |
2083 | argument. Instead, all functions act on the single default loop.</p> |
2259 | argument. Instead, all functions act on the single default loop.</p> |
2084 | </dd> |
2260 | </dd> |
|
|
2261 | <dt>EV_MINPRI</dt> |
|
|
2262 | <dt>EV_MAXPRI</dt> |
|
|
2263 | <dd> |
|
|
2264 | <p>The range of allowed priorities. <code>EV_MINPRI</code> must be smaller or equal to |
|
|
2265 | <code>EV_MAXPRI</code>, but otherwise there are no non-obvious limitations. You can |
|
|
2266 | provide for more priorities by overriding those symbols (usually defined |
|
|
2267 | to be <code>-2</code> and <code>2</code>, respectively).</p> |
|
|
2268 | <p>When doing priority-based operations, libev usually has to linearly search |
|
|
2269 | all the priorities, so having many of them (hundreds) uses a lot of space |
|
|
2270 | and time, so using the defaults of five priorities (-2 .. +2) is usually |
|
|
2271 | fine.</p> |
|
|
2272 | <p>If your embedding app does not need any priorities, defining these both to |
|
|
2273 | <code>0</code> will save some memory and cpu.</p> |
|
|
2274 | </dd> |
2085 | <dt>EV_PERIODIC_ENABLE</dt> |
2275 | <dt>EV_PERIODIC_ENABLE</dt> |
2086 | <dd> |
2276 | <dd> |
2087 | <p>If undefined or defined to be <code>1</code>, then periodic timers are supported. If |
2277 | <p>If undefined or defined to be <code>1</code>, then periodic timers are supported. If |
|
|
2278 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
|
|
2279 | code.</p> |
|
|
2280 | </dd> |
|
|
2281 | <dt>EV_IDLE_ENABLE</dt> |
|
|
2282 | <dd> |
|
|
2283 | <p>If undefined or defined to be <code>1</code>, then idle watchers are supported. If |
2088 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
2284 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
2089 | code.</p> |
2285 | code.</p> |
2090 | </dd> |
2286 | </dd> |
2091 | <dt>EV_EMBED_ENABLE</dt> |
2287 | <dt>EV_EMBED_ENABLE</dt> |
2092 | <dd> |
2288 | <dd> |
… | |
… | |
2157 | the <cite>libev/</cite> subdirectory and includes them in the <cite>EV/EVAPI.h</cite> (public |
2353 | the <cite>libev/</cite> subdirectory and includes them in the <cite>EV/EVAPI.h</cite> (public |
2158 | interface) and <cite>EV.xs</cite> (implementation) files. Only the <cite>EV.xs</cite> file |
2354 | interface) and <cite>EV.xs</cite> (implementation) files. Only the <cite>EV.xs</cite> file |
2159 | will be compiled. It is pretty complex because it provides its own header |
2355 | will be compiled. It is pretty complex because it provides its own header |
2160 | file.</p> |
2356 | file.</p> |
2161 | <p>The usage in rxvt-unicode is simpler. It has a <cite>ev_cpp.h</cite> header file |
2357 | <p>The usage in rxvt-unicode is simpler. It has a <cite>ev_cpp.h</cite> header file |
2162 | that everybody includes and which overrides some autoconf choices:</p> |
2358 | that everybody includes and which overrides some configure choices:</p> |
|
|
2359 | <pre> #define EV_MINIMAL 1 |
2163 | <pre> #define EV_USE_POLL 0 |
2360 | #define EV_USE_POLL 0 |
2164 | #define EV_MULTIPLICITY 0 |
2361 | #define EV_MULTIPLICITY 0 |
2165 | #define EV_PERIODICS 0 |
2362 | #define EV_PERIODIC_ENABLE 0 |
|
|
2363 | #define EV_STAT_ENABLE 0 |
|
|
2364 | #define EV_FORK_ENABLE 0 |
2166 | #define EV_CONFIG_H <config.h> |
2365 | #define EV_CONFIG_H <config.h> |
|
|
2366 | #define EV_MINPRI 0 |
|
|
2367 | #define EV_MAXPRI 0 |
2167 | |
2368 | |
2168 | #include "ev++.h" |
2369 | #include "ev++.h" |
2169 | |
2370 | |
2170 | </pre> |
2371 | </pre> |
2171 | <p>And a <cite>ev_cpp.C</cite> implementation file that contains libev proper and is compiled:</p> |
2372 | <p>And a <cite>ev_cpp.C</cite> implementation file that contains libev proper and is compiled:</p> |
… | |
… | |
2181 | <h1 id="COMPLEXITIES">COMPLEXITIES</h1> |
2382 | <h1 id="COMPLEXITIES">COMPLEXITIES</h1> |
2182 | <div id="COMPLEXITIES_CONTENT"> |
2383 | <div id="COMPLEXITIES_CONTENT"> |
2183 | <p>In this section the complexities of (many of) the algorithms used inside |
2384 | <p>In this section the complexities of (many of) the algorithms used inside |
2184 | libev will be explained. For complexity discussions about backends see the |
2385 | libev will be explained. For complexity discussions about backends see the |
2185 | documentation for <code>ev_default_init</code>.</p> |
2386 | documentation for <code>ev_default_init</code>.</p> |
|
|
2387 | <p>All of the following are about amortised time: If an array needs to be |
|
|
2388 | extended, libev needs to realloc and move the whole array, but this |
|
|
2389 | happens asymptotically never with higher number of elements, so O(1) might |
|
|
2390 | mean it might do a lengthy realloc operation in rare cases, but on average |
|
|
2391 | it is much faster and asymptotically approaches constant time.</p> |
2186 | <p> |
2392 | <p> |
2187 | <dl> |
2393 | <dl> |
2188 | <dt>Starting and stopping timer/periodic watchers: O(log skipped_other_timers)</dt> |
2394 | <dt>Starting and stopping timer/periodic watchers: O(log skipped_other_timers)</dt> |
|
|
2395 | <dd> |
|
|
2396 | <p>This means that, when you have a watcher that triggers in one hour and |
|
|
2397 | there are 100 watchers that would trigger before that then inserting will |
|
|
2398 | have to skip those 100 watchers.</p> |
|
|
2399 | </dd> |
2189 | <dt>Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)</dt> |
2400 | <dt>Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)</dt> |
|
|
2401 | <dd> |
|
|
2402 | <p>That means that for changing a timer costs less than removing/adding them |
|
|
2403 | as only the relative motion in the event queue has to be paid for.</p> |
|
|
2404 | </dd> |
2190 | <dt>Starting io/check/prepare/idle/signal/child watchers: O(1)</dt> |
2405 | <dt>Starting io/check/prepare/idle/signal/child watchers: O(1)</dt> |
|
|
2406 | <dd> |
|
|
2407 | <p>These just add the watcher into an array or at the head of a list. |
2191 | <dt>Stopping check/prepare/idle watchers: O(1)</dt> |
2408 | =item Stopping check/prepare/idle watchers: O(1)</p> |
|
|
2409 | </dd> |
2192 | <dt>Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))</dt> |
2410 | <dt>Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))</dt> |
|
|
2411 | <dd> |
|
|
2412 | <p>These watchers are stored in lists then need to be walked to find the |
|
|
2413 | correct watcher to remove. The lists are usually short (you don't usually |
|
|
2414 | have many watchers waiting for the same fd or signal).</p> |
|
|
2415 | </dd> |
2193 | <dt>Finding the next timer per loop iteration: O(1)</dt> |
2416 | <dt>Finding the next timer per loop iteration: O(1)</dt> |
2194 | <dt>Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)</dt> |
2417 | <dt>Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)</dt> |
|
|
2418 | <dd> |
|
|
2419 | <p>A change means an I/O watcher gets started or stopped, which requires |
|
|
2420 | libev to recalculate its status (and possibly tell the kernel).</p> |
|
|
2421 | </dd> |
2195 | <dt>Activating one watcher: O(1)</dt> |
2422 | <dt>Activating one watcher: O(1)</dt> |
|
|
2423 | <dt>Priority handling: O(number_of_priorities)</dt> |
|
|
2424 | <dd> |
|
|
2425 | <p>Priorities are implemented by allocating some space for each |
|
|
2426 | priority. When doing priority-based operations, libev usually has to |
|
|
2427 | linearly search all the priorities.</p> |
|
|
2428 | </dd> |
2196 | </dl> |
2429 | </dl> |
2197 | </p> |
2430 | </p> |
2198 | |
2431 | |
2199 | |
2432 | |
2200 | |
2433 | |