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

Comparing libev/ev.3 (file contents):
Revision 1.30 by root, Wed Nov 28 11:27:29 2007 UTC vs.
Revision 1.34 by root, Thu Nov 29 12:21:21 2007 UTC

… …
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title ""<STANDARD INPUT>" 1" 131.IX Title ""<STANDARD INPUT>" 1"
132.TH "<STANDARD INPUT>" 1 "2007-11-28" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-11-29" "perl v5.8.8" "User Contributed Perl Documentation"
133.SH "NAME" 133.SH "NAME"
134libev \- a high performance full\-featured event loop written in C 134libev \- a high performance full\-featured event loop written in C
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 1 137.Vb 1
… …
210watchers\fR, which are relatively small C structures you initialise with the 210watchers\fR, which are relatively small C structures you initialise with the
211details of the event, and then hand it over to libev by \fIstarting\fR the 211details of the event, and then hand it over to libev by \fIstarting\fR the
212watcher. 212watcher.
213.SH "FEATURES" 213.SH "FEATURES"
214.IX Header "FEATURES" 214.IX Header "FEATURES"
215Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the linux-specific \f(CW\*(C`epoll\*(C'\fR, the 215Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific \f(CW\*(C`epoll\*(C'\fR, the
216bsd-specific \f(CW\*(C`kqueue\*(C'\fR and the solaris-specific event port mechanisms 216BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms
217for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR), 217for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR interface
218(for \f(CW\*(C`ev_stat\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers
218absolute timers with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous 219with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals
219signals (\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and 220(\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and event
220event watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, 221watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR,
221\&\f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR watchers) as well as 222\&\f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR watchers) as well as
222file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events 223file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events
223(\f(CW\*(C`ev_fork\*(C'\fR). 224(\f(CW\*(C`ev_fork\*(C'\fR).
224.PP 225.PP
225It also is quite fast (see this 226It also is quite fast (see this
… …
304might be supported on the current system, you would need to look at 305might be supported on the current system, you would need to look at
305\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for 306\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for
306recommended ones. 307recommended ones.
307.Sp 308.Sp
308See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. 309See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info.
309.IP "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 4 310.IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4
310.IX Item "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 311.IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))"
311Sets the allocation function to use (the prototype and semantics are 312Sets the allocation function to use (the prototype is similar \- the
312identical to the realloc C function). It is used to allocate and free 313semantics is identical \- to the realloc C function). It is used to
313memory (no surprises here). If it returns zero when memory needs to be 314allocate and free memory (no surprises here). If it returns zero when
314allocated, the library might abort or take some potentially destructive 315memory needs to be allocated, the library might abort or take some
315action. The default is your system realloc function. 316potentially destructive action. The default is your system realloc
317function.
316.Sp 318.Sp
317You could override this function in high-availability programs to, say, 319You could override this function in high-availability programs to, say,
318free some memory if it cannot allocate memory, to use a special allocator, 320free some memory if it cannot allocate memory, to use a special allocator,
319or even to sleep a while and retry until some memory is available. 321or even to sleep a while and retry until some memory is available.
320.Sp 322.Sp
… …
1069.IP "ev_timer_again (loop)" 4 1071.IP "ev_timer_again (loop)" 4
1070.IX Item "ev_timer_again (loop)" 1072.IX Item "ev_timer_again (loop)"
1071This will act as if the timer timed out and restart it again if it is 1073This will act as if the timer timed out and restart it again if it is
1072repeating. The exact semantics are: 1074repeating. The exact semantics are:
1073.Sp 1075.Sp
1076If the timer is pending, its pending status is cleared.
1077.Sp
1074If the timer is started but nonrepeating, stop it. 1078If the timer is started but nonrepeating, stop it (as if it timed out).
1075.Sp 1079.Sp
1076If the timer is repeating, either start it if necessary (with the repeat 1080If the timer is repeating, either start it if necessary (with the
1077value), or reset the running timer to the repeat value. 1081\&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value.
1078.Sp 1082.Sp
1079This sounds a bit complicated, but here is a useful and typical 1083This sounds a bit complicated, but here is a useful and typical
1080example: Imagine you have a tcp connection and you want a so-called 1084example: Imagine you have a tcp connection and you want a so-called idle
1081idle timeout, that is, you want to be called when there have been, 1085timeout, that is, you want to be called when there have been, say, 60
1082say, 60 seconds of inactivity on the socket. The easiest way to do 1086seconds of inactivity on the socket. The easiest way to do this is to
1083this is to configure an \f(CW\*(C`ev_timer\*(C'\fR with \f(CW\*(C`after\*(C'\fR=\f(CW\*(C`repeat\*(C'\fR=\f(CW60\fR and calling 1087configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call
1084\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If 1088\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
1085you go into an idle state where you do not expect data to travel on the 1089you go into an idle state where you do not expect data to travel on the
1086socket, you can stop the timer, and again will automatically restart it if 1090socket, you can \f(CW\*(C`ev_timer_stop\*(C'\fR the timer, and \f(CW\*(C`ev_timer_again\*(C'\fR will
1087need be. 1091automatically restart it if need be.
1088.Sp 1092.Sp
1089You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether 1093That means you can ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR
1090and only ever use the \f(CW\*(C`repeat\*(C'\fR value: 1094altogether and only ever use the \f(CW\*(C`repeat\*(C'\fR value and \f(CW\*(C`ev_timer_again\*(C'\fR:
1091.Sp 1095.Sp
1092.Vb 8 1096.Vb 8
1093\& ev_timer_init (timer, callback, 0., 5.); 1097\& ev_timer_init (timer, callback, 0., 5.);
1094\& ev_timer_again (loop, timer); 1098\& ev_timer_again (loop, timer);
1095\& ... 1099\& ...
… …
1098\& ... 1102\& ...
1099\& timer->again = 10.; 1103\& timer->again = 10.;
1100\& ev_timer_again (loop, timer); 1104\& ev_timer_again (loop, timer);
1101.Ve 1105.Ve
1102.Sp 1106.Sp
1103This is more efficient then stopping/starting the timer eahc time you want 1107This is more slightly efficient then stopping/starting the timer each time
1104to modify its timeout value. 1108you want to modify its timeout value.
1105.IP "ev_tstamp repeat [read\-write]" 4 1109.IP "ev_tstamp repeat [read\-write]" 4
1106.IX Item "ev_tstamp repeat [read-write]" 1110.IX Item "ev_tstamp repeat [read-write]"
1107The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out 1111The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
1108or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), 1112or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
1109which is also when any modifications are taken into account. 1113which is also when any modifications are taken into account.
… …
1381The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does 1385The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does
1382not exist\*(R" is a status change like any other. The condition \*(L"path does 1386not exist\*(R" is a status change like any other. The condition \*(L"path does
1383not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is 1387not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is
1384otherwise always forced to be at least one) and all the other fields of 1388otherwise always forced to be at least one) and all the other fields of
1385the stat buffer having unspecified contents. 1389the stat buffer having unspecified contents.
1390.PP
1391The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is
1392relative and your working directory changes, the behaviour is undefined.
1386.PP 1393.PP
1387Since there is no standard to do this, the portable implementation simply 1394Since there is no standard to do this, the portable implementation simply
1388calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You 1395calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You
1389can specify a recommended polling interval for this case. If you specify 1396can specify a recommended polling interval for this case. If you specify
1390a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, 1397a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable,

Diff Legend

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