… | |
… | |
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="Fri Dec 7 20:07:44 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 --> |
… | |
… | |
529 | 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 |
530 | external event in conjunction with something not expressible using other |
530 | 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 |
531 | 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> |
532 | 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> |
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. |
534 | <pre> * If there are no active watchers (reference count is zero), return. |
535 | * If there are no active watchers (reference count is zero), return. |
535 | - Queue prepare watchers and then call all outstanding watchers. |
536 | - Queue all prepare watchers and then call all outstanding watchers. |
536 | - If we have been forked, recreate the kernel state. |
537 | - If we have been forked, recreate the kernel state. |
537 | - Update the kernel state with all outstanding changes. |
538 | - Update the kernel state with all outstanding changes. |
538 | - Update the "event loop time". |
539 | - Update the "event loop time". |
539 | - Calculate for how long to block. |
540 | - Calculate for how long to block. |
540 | - Block the process, waiting for any events. |
541 | - Block the process, waiting for any events. |
… | |
… | |
769 | <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> |
770 | <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> |
770 | <dd> |
771 | <dd> |
771 | <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 |
772 | 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 |
773 | 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 |
774 | <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 |
775 | 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> |
776 | </dd> |
778 | </dd> |
777 | <dt>callback ev_cb (ev_TYPE *watcher)</dt> |
779 | <dt>callback ev_cb (ev_TYPE *watcher)</dt> |
778 | <dd> |
780 | <dd> |
779 | <p>Returns the callback currently set on the watcher.</p> |
781 | <p>Returns the callback currently set on the watcher.</p> |
780 | </dd> |
782 | </dd> |
… | |
… | |
795 | invocation after new events have been received. This is useful, for |
797 | invocation after new events have been received. This is useful, for |
796 | example, to reduce latency after idling, or more often, to bind two |
798 | example, to reduce latency after idling, or more often, to bind two |
797 | watchers on the same event and make sure one is called first.</p> |
799 | watchers on the same event and make sure one is called first.</p> |
798 | <p>If you need to suppress invocation when higher priority events are pending |
800 | <p>If you need to suppress invocation when higher priority events are pending |
799 | you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p> |
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> |
800 | <p>The default priority used by watchers when no priority has been set is |
804 | <p>The default priority used by watchers when no priority has been set is |
801 | always <code>0</code>, which is supposed to not be too high and not be too low :).</p> |
805 | always <code>0</code>, which is supposed to not be too high and not be too low :).</p> |
802 | <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is |
806 | <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is |
803 | fine, as long as you do not mind that the priority value you query might |
807 | fine, as long as you do not mind that the priority value you query might |
804 | or might not have been adjusted to be within valid range.</p> |
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> |
805 | </dd> |
821 | </dd> |
806 | </dl> |
822 | </dl> |
807 | |
823 | |
808 | |
824 | |
809 | |
825 | |
… | |
… | |
1468 | 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 |
1469 | 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 |
1470 | 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 |
1471 | loop from blocking if lower-priority coroutines are active, thus mapping |
1487 | loop from blocking if lower-priority coroutines are active, thus mapping |
1472 | 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> |
1473 | <dl> |
1498 | <dl> |
1474 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1499 | <dt>ev_prepare_init (ev_prepare *, callback)</dt> |
1475 | <dt>ev_check_init (ev_check *, callback)</dt> |
1500 | <dt>ev_check_init (ev_check *, callback)</dt> |
1476 | <dd> |
1501 | <dd> |
1477 | <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 |
1478 | 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> |
1479 | macros, but using them is utterly, utterly and completely pointless.</p> |
1504 | macros, but using them is utterly, utterly and completely pointless.</p> |
1480 | </dd> |
1505 | </dd> |
1481 | </dl> |
1506 | </dl> |
1482 | <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 |
1483 | 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, |
1484 | 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 |
1485 | 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> |
1486 | <pre> static ev_io iow [nfd]; |
1518 | <pre> static ev_io iow [nfd]; |
1487 | static ev_timer tw; |
1519 | static ev_timer tw; |
1488 | |
1520 | |
1489 | static void |
1521 | static void |
1490 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1522 | io_cb (ev_loop *loop, ev_io *w, int revents) |
1491 | { |
1523 | { |
1492 | // set the relevant poll flags |
|
|
1493 | // could also call adns_processreadable etc. here |
|
|
1494 | struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1495 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1496 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1497 | } |
1524 | } |
1498 | |
1525 | |
1499 | // create io watchers for each fd and a timer before blocking |
1526 | // create io watchers for each fd and a timer before blocking |
1500 | static void |
1527 | static void |
1501 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1528 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
… | |
… | |
1507 | |
1534 | |
1508 | /* 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 */ |
1509 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1536 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1510 | ev_timer_start (loop, &tw); |
1537 | ev_timer_start (loop, &tw); |
1511 | |
1538 | |
1512 | // create on ev_io per pollfd |
1539 | // create one ev_io per pollfd |
1513 | for (int i = 0; i < nfd; ++i) |
1540 | for (int i = 0; i < nfd; ++i) |
1514 | { |
1541 | { |
1515 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1542 | ev_io_init (iow + i, io_cb, fds [i].fd, |
1516 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1543 | ((fds [i].events & POLLIN ? EV_READ : 0) |
1517 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1544 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1518 | |
1545 | |
1519 | fds [i].revents = 0; |
1546 | fds [i].revents = 0; |
1520 | iow [i].data = fds + i; |
|
|
1521 | ev_io_start (loop, iow + i); |
1547 | ev_io_start (loop, iow + i); |
1522 | } |
1548 | } |
1523 | } |
1549 | } |
1524 | |
1550 | |
1525 | // stop all watchers after blocking |
1551 | // stop all watchers after blocking |
… | |
… | |
1527 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1553 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1528 | { |
1554 | { |
1529 | ev_timer_stop (loop, &tw); |
1555 | ev_timer_stop (loop, &tw); |
1530 | |
1556 | |
1531 | 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 |
1532 | ev_io_stop (loop, iow + i); |
1567 | ev_io_stop (loop, iow + i); |
|
|
1568 | } |
1533 | |
1569 | |
1534 | 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; |
1535 | } |
1629 | } |
1536 | |
1630 | |
1537 | |
1631 | |
1538 | |
1632 | |
1539 | |
1633 | |
… | |
… | |
1736 | 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> |
1737 | <p>To use it,</p> |
1831 | <p>To use it,</p> |
1738 | <pre> #include <ev++.h> |
1832 | <pre> #include <ev++.h> |
1739 | |
1833 | |
1740 | </pre> |
1834 | </pre> |
1741 | <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 |
1742 | 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 |
1743 | 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 |
1744 | <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> |
1745 | <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> |
1746 | <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> |
1747 | <dl> |
1849 | <dl> |
1748 | <dt><code>ev::READ</code>, <code>ev::WRITE</code> etc.</dt> |
1850 | <dt><code>ev::READ</code>, <code>ev::WRITE</code> etc.</dt> |
1749 | <dd> |
1851 | <dd> |
1750 | <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. |
… | |
… | |
1761 | 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 |
1762 | defines by many implementations.</p> |
1864 | defines by many implementations.</p> |
1763 | <p>All of those classes have these methods:</p> |
1865 | <p>All of those classes have these methods:</p> |
1764 | <p> |
1866 | <p> |
1765 | <dl> |
1867 | <dl> |
1766 | <dt>ev::TYPE::TYPE (object *, object::method *)</dt> |
1868 | <dt>ev::TYPE::TYPE ()</dt> |
1767 | <dt>ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)</dt> |
1869 | <dt>ev::TYPE::TYPE (struct ev_loop *)</dt> |
1768 | <dt>ev::TYPE::~TYPE</dt> |
1870 | <dt>ev::TYPE::~TYPE</dt> |
1769 | <dd> |
1871 | <dd> |
1770 | <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 |
1771 | 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> |
1772 | <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 |
1773 | before starting it. If you do not specify a loop then the constructor |
1875 | <code>set</code> method before starting it.</p> |
1774 | 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> |
1775 | <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> |
1776 | </dd> |
1917 | </dd> |
1777 | <dt>w->set (struct ev_loop *)</dt> |
1918 | <dt>w->set (struct ev_loop *)</dt> |
1778 | <dd> |
1919 | <dd> |
1779 | <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 |
1780 | 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> |
1781 | </dd> |
1922 | </dd> |
1782 | <dt>w->set ([args])</dt> |
1923 | <dt>w->set ([args])</dt> |
1783 | <dd> |
1924 | <dd> |
1784 | <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 |
1785 | 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 |
1786 | automatically stopped and restarted.</p> |
1927 | automatically stopped and restarted when reconfiguring it with this |
|
|
1928 | method.</p> |
1787 | </dd> |
1929 | </dd> |
1788 | <dt>w->start ()</dt> |
1930 | <dt>w->start ()</dt> |
1789 | <dd> |
1931 | <dd> |
1790 | <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 |
1791 | constructor already takes the loop.</p> |
1933 | constructor already stores the event loop.</p> |
1792 | </dd> |
1934 | </dd> |
1793 | <dt>w->stop ()</dt> |
1935 | <dt>w->stop ()</dt> |
1794 | <dd> |
1936 | <dd> |
1795 | <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> |
1796 | </dd> |
1938 | </dd> |
… | |
… | |
1820 | |
1962 | |
1821 | myclass (); |
1963 | myclass (); |
1822 | } |
1964 | } |
1823 | |
1965 | |
1824 | myclass::myclass (int fd) |
1966 | myclass::myclass (int fd) |
1825 | : io (this, &myclass::io_cb), |
|
|
1826 | idle (this, &myclass::idle_cb) |
|
|
1827 | { |
1967 | { |
|
|
1968 | io .set <myclass, &myclass::io_cb > (this); |
|
|
1969 | idle.set <myclass, &myclass::idle_cb> (this); |
|
|
1970 | |
1828 | io.start (fd, ev::READ); |
1971 | io.start (fd, ev::READ); |
1829 | } |
1972 | } |
1830 | |
1973 | |
1831 | |
1974 | |
1832 | |
1975 | |
… | |
… | |
2239 | <h1 id="COMPLEXITIES">COMPLEXITIES</h1> |
2382 | <h1 id="COMPLEXITIES">COMPLEXITIES</h1> |
2240 | <div id="COMPLEXITIES_CONTENT"> |
2383 | <div id="COMPLEXITIES_CONTENT"> |
2241 | <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 |
2242 | libev will be explained. For complexity discussions about backends see the |
2385 | libev will be explained. For complexity discussions about backends see the |
2243 | 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> |
2244 | <p> |
2392 | <p> |
2245 | <dl> |
2393 | <dl> |
2246 | <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> |
2247 | <dd> |
2395 | <dd> |
2248 | <p>This means that, when you have a watcher that triggers in one hour and |
2396 | <p>This means that, when you have a watcher that triggers in one hour and |
… | |
… | |
2254 | <p>That means that for changing a timer costs less than removing/adding them |
2402 | <p>That means that for changing a timer costs less than removing/adding them |
2255 | as only the relative motion in the event queue has to be paid for.</p> |
2403 | as only the relative motion in the event queue has to be paid for.</p> |
2256 | </dd> |
2404 | </dd> |
2257 | <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> |
2258 | <dd> |
2406 | <dd> |
2259 | <p>These just add the watcher into an array or at the head of a list. If |
2407 | <p>These just add the watcher into an array or at the head of a list. |
2260 | the array needs to be extended libev needs to realloc and move the whole |
|
|
2261 | array, but this happen asymptotically less and less with more watchers, |
|
|
2262 | thus amortised O(1).</p> |
|
|
2263 | </dd> |
|
|
2264 | <dt>Stopping check/prepare/idle watchers: O(1)</dt> |
2408 | =item Stopping check/prepare/idle watchers: O(1)</p> |
|
|
2409 | </dd> |
2265 | <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> |
2266 | <dd> |
2411 | <dd> |
2267 | <p>These watchers are stored in lists then need to be walked to find the |
2412 | <p>These watchers are stored in lists then need to be walked to find the |
2268 | correct watcher to remove. The lists are usually short (you don't usually |
2413 | correct watcher to remove. The lists are usually short (you don't usually |
2269 | have many watchers waiting for the same fd or signal).</p> |
2414 | have many watchers waiting for the same fd or signal).</p> |