ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.3
(Generate patch)

Comparing libev/ev.3 (file contents):
Revision 1.118 by root, Sat Dec 21 16:11:51 2019 UTC vs.
Revision 1.124 by root, Sun May 9 18:41:06 2021 UTC

… …
131.\} 131.\}
132.rm #[ #] #H #V #F C 132.rm #[ #] #H #V #F C
133.\" ======================================================================== 133.\" ========================================================================
134.\" 134.\"
135.IX Title "LIBEV 3" 135.IX Title "LIBEV 3"
136.TH LIBEV 3 "2019-12-21" "libev-4.31" "libev - high performance full featured event loop" 136.TH LIBEV 3 "2021-01-11" "libev-4.33" "libev - high performance full featured event loop"
137.\" For nroff, turn off justification. Always turn off hyphenation; it makes 137.\" For nroff, turn off justification. Always turn off hyphenation; it makes
138.\" way too many mistakes in technical documents. 138.\" way too many mistakes in technical documents.
139.if n .ad l 139.if n .ad l
140.nh 140.nh
141.SH "NAME" 141.SH "NAME"
… …
1087\& \- Queue all expired timers. 1087\& \- Queue all expired timers.
1088\& \- Queue all expired periodics. 1088\& \- Queue all expired periodics.
1089\& \- Queue all idle watchers with priority higher than that of pending events. 1089\& \- Queue all idle watchers with priority higher than that of pending events.
1090\& \- Queue all check watchers. 1090\& \- Queue all check watchers.
1091\& \- Call all queued watchers in reverse order (i.e. check watchers first). 1091\& \- Call all queued watchers in reverse order (i.e. check watchers first).
1092\& Signals and child watchers are implemented as I/O watchers, and will 1092\& Signals, async and child watchers are implemented as I/O watchers, and
1093\& be handled here by queueing them when their watcher gets executed. 1093\& will be handled here by queueing them when their watcher gets executed.
1094\& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT 1094\& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT
1095\& were used, or there are no active watchers, goto FINISH, otherwise 1095\& were used, or there are no active watchers, goto FINISH, otherwise
1096\& continue with step LOOP. 1096\& continue with step LOOP.
1097\& FINISH: 1097\& FINISH:
1098\& \- Reset the ev_break status iff it was EVBREAK_ONE. 1098\& \- Reset the ev_break status iff it was EVBREAK_ONE.
… …
1349with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher 1349with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher
1350*)\*(C'\fR), and you can stop watching for events at any time by calling the 1350*)\*(C'\fR), and you can stop watching for events at any time by calling the
1351corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR. 1351corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR.
1352.PP 1352.PP
1353As long as your watcher is active (has been started but not stopped) you 1353As long as your watcher is active (has been started but not stopped) you
1354must not touch the values stored in it. Most specifically you must never 1354must not touch the values stored in it except when explicitly documented
1355reinitialise it or call its \f(CW\*(C`ev_TYPE_set\*(C'\fR macro. 1355otherwise. Most specifically you must never reinitialise it or call its
1356\&\f(CW\*(C`ev_TYPE_set\*(C'\fR macro.
1356.PP 1357.PP
1357Each and every callback receives the event loop pointer as first, the 1358Each and every callback receives the event loop pointer as first, the
1358registered watcher structure as second, and a bitset of received events as 1359registered watcher structure as second, and a bitset of received events as
1359third argument. 1360third argument.
1360.PP 1361.PP
… …
1531therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. 1532therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function.
1532.IP "bool ev_is_active (ev_TYPE *watcher)" 4 1533.IP "bool ev_is_active (ev_TYPE *watcher)" 4
1533.IX Item "bool ev_is_active (ev_TYPE *watcher)" 1534.IX Item "bool ev_is_active (ev_TYPE *watcher)"
1534Returns a true value iff the watcher is active (i.e. it has been started 1535Returns a true value iff the watcher is active (i.e. it has been started
1535and not yet been stopped). As long as a watcher is active you must not modify 1536and not yet been stopped). As long as a watcher is active you must not modify
1536it. 1537it unless documented otherwise.
1537.IP "bool ev_is_pending (ev_TYPE *watcher)" 4 1538.IP "bool ev_is_pending (ev_TYPE *watcher)" 4
1538.IX Item "bool ev_is_pending (ev_TYPE *watcher)" 1539.IX Item "bool ev_is_pending (ev_TYPE *watcher)"
1539Returns a true value iff the watcher is pending, (i.e. it has outstanding 1540Returns a true value iff the watcher is pending, (i.e. it has outstanding
1540events but its callback has not yet been invoked). As long as a watcher 1541events but its callback has not yet been invoked). As long as a watcher
1541is pending (but not active) you must not call an init function on it (but 1542is pending (but not active) you must not call an init function on it (but
… …
1767.IX Header "WATCHER TYPES" 1768.IX Header "WATCHER TYPES"
1768This section describes each watcher in detail, but will not repeat 1769This section describes each watcher in detail, but will not repeat
1769information given in the last section. Any initialisation/set macros, 1770information given in the last section. Any initialisation/set macros,
1770functions and members specific to the watcher type are explained. 1771functions and members specific to the watcher type are explained.
1771.PP 1772.PP
1772Members are additionally marked with either \fI[read\-only]\fR, meaning that, 1773Most members are additionally marked with either \fI[read\-only]\fR, meaning
1773while the watcher is active, you can look at the member and expect some 1774that, while the watcher is active, you can look at the member and expect
1774sensible content, but you must not modify it (you can modify it while the 1775some sensible content, but you must not modify it (you can modify it while
1775watcher is stopped to your hearts content), or \fI[read\-write]\fR, which 1776the watcher is stopped to your hearts content), or \fI[read\-write]\fR, which
1776means you can expect it to have some sensible content while the watcher 1777means you can expect it to have some sensible content while the watcher is
1777is active, but you can also modify it. Modifying it may not do something 1778active, but you can also modify it (within the same thread as the event
1779loop, i.e. without creating data races). Modifying it may not do something
1778sensible or take immediate effect (or do anything at all), but libev will 1780sensible or take immediate effect (or do anything at all), but libev will
1779not crash or malfunction in any way. 1781not crash or malfunction in any way.
1782.PP
1783In any case, the documentation for each member will explain what the
1784effects are, and if there are any additional access restrictions.
1780.ie n .SS """ev_io"" \- is this file descriptor readable or writable?" 1785.ie n .SS """ev_io"" \- is this file descriptor readable or writable?"
1781.el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?" 1786.el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?"
1782.IX Subsection "ev_io - is this file descriptor readable or writable?" 1787.IX Subsection "ev_io - is this file descriptor readable or writable?"
1783I/O watchers check whether a file descriptor is readable or writable 1788I/O watchers check whether a file descriptor is readable or writable
1784in each iteration of the event loop, or, more precisely, when reading 1789in each iteration of the event loop, or, more precisely, when reading
… …
1950.PD 0 1955.PD 0
1951.IP "ev_io_set (ev_io *, int fd, int events)" 4 1956.IP "ev_io_set (ev_io *, int fd, int events)" 4
1952.IX Item "ev_io_set (ev_io *, int fd, int events)" 1957.IX Item "ev_io_set (ev_io *, int fd, int events)"
1953.PD 1958.PD
1954Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to 1959Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to
1955receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or 1960receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR, both
1956\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR, to express the desire to receive the given events. 1961\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR or \f(CW0\fR, to express the desire to receive the given
1962events.
1963.Sp
1964Note that setting the \f(CW\*(C`events\*(C'\fR to \f(CW0\fR and starting the watcher is
1965supported, but not specially optimized \- if your program sometimes happens
1966to generate this combination this is fine, but if it is easy to avoid
1967starting an io watcher watching for no events you should do so.
1968.IP "ev_io_modify (ev_io *, int events)" 4
1969.IX Item "ev_io_modify (ev_io *, int events)"
1970Similar to \f(CW\*(C`ev_io_set\*(C'\fR, but only changes the requested events. Using this
1971might be faster with some backends, as libev can assume that the \f(CW\*(C`fd\*(C'\fR
1972still refers to the same underlying file description, something it cannot
1973do when using \f(CW\*(C`ev_io_set\*(C'\fR.
1957.IP "int fd [read\-only]" 4 1974.IP "int fd [no\-modify]" 4
1958.IX Item "int fd [read-only]" 1975.IX Item "int fd [no-modify]"
1959The file descriptor being watched. 1976The file descriptor being watched. While it can be read at any time, you
1977must not modify this member even when the watcher is stopped \- always use
1978\&\f(CW\*(C`ev_io_set\*(C'\fR for that.
1960.IP "int events [read\-only]" 4 1979.IP "int events [no\-modify]" 4
1961.IX Item "int events [read-only]" 1980.IX Item "int events [no-modify]"
1962The events being watched. 1981The set of events the fd is being watched for, among other flags. Remember
1982that this is a bit set \- to test for \f(CW\*(C`EV_READ\*(C'\fR, use \f(CW\*(C`w\->events &
1983EV_READ\*(C'\fR, and similarly for \f(CW\*(C`EV_WRITE\*(C'\fR.
1984.Sp
1985As with \f(CW\*(C`fd\*(C'\fR, you must not modify this member even when the watcher is
1986stopped, always use \f(CW\*(C`ev_io_set\*(C'\fR or \f(CW\*(C`ev_io_modify\*(C'\fR for that.
1963.PP 1987.PP
1964\fIExamples\fR 1988\fIExamples\fR
1965.IX Subsection "Examples" 1989.IX Subsection "Examples"
1966.PP 1990.PP
1967Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well 1991Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well
… …
3978.PP 4002.PP
3979First, you need to associate some data with the event loop: 4003First, you need to associate some data with the event loop:
3980.PP 4004.PP
3981.Vb 6 4005.Vb 6
3982\& typedef struct { 4006\& typedef struct {
3983\& mutex_t lock; /* global loop lock */ 4007\& pthread_mutex_t lock; /* global loop lock */
4008\& pthread_t tid;
4009\& pthread_cond_t invoke_cv;
3984\& ev_async async_w; 4010\& ev_async async_w;
3985\& thread_t tid;
3986\& cond_t invoke_cv;
3987\& } userdata; 4011\& } userdata;
3988\& 4012\&
3989\& void prepare_loop (EV_P) 4013\& void prepare_loop (EV_P)
3990\& { 4014\& {
3991\& // for simplicity, we use a static userdata struct. 4015\& // for simplicity, we use a static userdata struct.
3992\& static userdata u; 4016\& static userdata u;
3993\& 4017\&
3994\& ev_async_init (&u\->async_w, async_cb); 4018\& ev_async_init (&u.async_w, async_cb);
3995\& ev_async_start (EV_A_ &u\->async_w); 4019\& ev_async_start (EV_A_ &u.async_w);
3996\& 4020\&
3997\& pthread_mutex_init (&u\->lock, 0); 4021\& pthread_mutex_init (&u.lock, 0);
3998\& pthread_cond_init (&u\->invoke_cv, 0); 4022\& pthread_cond_init (&u.invoke_cv, 0);
3999\& 4023\&
4000\& // now associate this with the loop 4024\& // now associate this with the loop
4001\& ev_set_userdata (EV_A_ u); 4025\& ev_set_userdata (EV_A_ &u);
4002\& ev_set_invoke_pending_cb (EV_A_ l_invoke); 4026\& ev_set_invoke_pending_cb (EV_A_ l_invoke);
4003\& ev_set_loop_release_cb (EV_A_ l_release, l_acquire); 4027\& ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
4004\& 4028\&
4005\& // then create the thread running ev_run 4029\& // then create the thread running ev_run
4006\& pthread_create (&u\->tid, 0, l_run, EV_A); 4030\& pthread_create (&u.tid, 0, l_run, EV_A);
4007\& } 4031\& }
4008.Ve 4032.Ve
4009.PP 4033.PP
4010The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used 4034The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used
4011solely to wake up the event loop so it takes notice of any new watchers 4035solely to wake up the event loop so it takes notice of any new watchers
… …
4395gets automatically stopped and restarted when reconfiguring it with this 4419gets automatically stopped and restarted when reconfiguring it with this
4396method. 4420method.
4397.Sp 4421.Sp
4398For \f(CW\*(C`ev::embed\*(C'\fR watchers this method is called \f(CW\*(C`set_embed\*(C'\fR, to avoid 4422For \f(CW\*(C`ev::embed\*(C'\fR watchers this method is called \f(CW\*(C`set_embed\*(C'\fR, to avoid
4399clashing with the \f(CW\*(C`set (loop)\*(C'\fR method. 4423clashing with the \f(CW\*(C`set (loop)\*(C'\fR method.
4424.Sp
4425For \f(CW\*(C`ev::io\*(C'\fR watchers there is an additional \f(CW\*(C`set\*(C'\fR method that acepts a
4426new event mask only, and internally calls \f(CW\*(C`ev_io_modfify\*(C'\fR.
4400.IP "w\->start ()" 4 4427.IP "w\->start ()" 4
4401.IX Item "w->start ()" 4428.IX Item "w->start ()"
4402Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the 4429Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the
4403constructor already stores the event loop. 4430constructor already stores the event loop.
4404.IP "w\->start ([arguments])" 4 4431.IP "w\->start ([arguments])" 4

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines