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

Comparing libev/ev.3 (file contents):
Revision 1.21 by root, Mon Nov 26 10:20:42 2007 UTC vs.
Revision 1.22 by root, Tue Nov 27 08:11:52 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-26" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-11-27" "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
684The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread. 684The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread.
685.ie n .IP """EV_CHILD""" 4 685.ie n .IP """EV_CHILD""" 4
686.el .IP "\f(CWEV_CHILD\fR" 4 686.el .IP "\f(CWEV_CHILD\fR" 4
687.IX Item "EV_CHILD" 687.IX Item "EV_CHILD"
688The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change. 688The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change.
689.ie n .IP """EV_STAT""" 4
690.el .IP "\f(CWEV_STAT\fR" 4
691.IX Item "EV_STAT"
692The path specified in the \f(CW\*(C`ev_stat\*(C'\fR watcher changed its attributes somehow.
689.ie n .IP """EV_IDLE""" 4 693.ie n .IP """EV_IDLE""" 4
690.el .IP "\f(CWEV_IDLE\fR" 4 694.el .IP "\f(CWEV_IDLE\fR" 4
691.IX Item "EV_IDLE" 695.IX Item "EV_IDLE"
692The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do. 696The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do.
693.ie n .IP """EV_PREPARE""" 4 697.ie n .IP """EV_PREPARE""" 4
821More interesting and less C\-conformant ways of catsing your callback type 825More interesting and less C\-conformant ways of catsing your callback type
822have been omitted.... 826have been omitted....
823.SH "WATCHER TYPES" 827.SH "WATCHER TYPES"
824.IX Header "WATCHER TYPES" 828.IX Header "WATCHER TYPES"
825This section describes each watcher in detail, but will not repeat 829This section describes each watcher in detail, but will not repeat
826information given in the last section. 830information given in the last section. Any initialisation/set macros,
831functions and members specific to the watcher type are explained.
832.PP
833Members are additionally marked with either \fI[read\-only]\fR, meaning that,
834while the watcher is active, you can look at the member and expect some
835sensible content, but you must not modify it (you can modify it while the
836watcher is stopped to your hearts content), or \fI[read\-write]\fR, which
837means you can expect it to have some sensible content while the watcher
838is active, but you can also modify it. Modifying it may not do something
839sensible or take immediate effect (or do anything at all), but libev will
840not crash or malfunction in any way.
827.ie n .Sh """ev_io"" \- is this file descriptor readable or writable?" 841.ie n .Sh """ev_io"" \- is this file descriptor readable or writable?"
828.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable?" 842.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable?"
829.IX Subsection "ev_io - is this file descriptor readable or writable?" 843.IX Subsection "ev_io - is this file descriptor readable or writable?"
830I/O watchers check whether a file descriptor is readable or writable 844I/O watchers check whether a file descriptor is readable or writable
831in each iteration of the event loop, or, more precisely, when reading 845in each iteration of the event loop, or, more precisely, when reading
871.IX Item "ev_io_set (ev_io *, int fd, int events)" 885.IX Item "ev_io_set (ev_io *, int fd, int events)"
872.PD 886.PD
873Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to 887Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to
874rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or 888rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or
875\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events. 889\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events.
890.IP "int fd [read\-only]" 4
891.IX Item "int fd [read-only]"
892The file descriptor being watched.
893.IP "int events [read\-only]" 4
894.IX Item "int events [read-only]"
895The events being watched.
876.PP 896.PP
877Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well 897Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well
878readable, but only once. Since it is likely line\-buffered, you could 898readable, but only once. Since it is likely line\-buffered, you could
879attempt to read a whole line in the callback: 899attempt to read a whole line in the callback:
880.PP 900.PP
945.Sp 965.Sp
946If the timer is repeating, either start it if necessary (with the repeat 966If the timer is repeating, either start it if necessary (with the repeat
947value), or reset the running timer to the repeat value. 967value), or reset the running timer to the repeat value.
948.Sp 968.Sp
949This sounds a bit complicated, but here is a useful and typical 969This sounds a bit complicated, but here is a useful and typical
950example: Imagine you have a tcp connection and you want a so-called idle 970example: Imagine you have a tcp connection and you want a so-called
951timeout, that is, you want to be called when there have been, say, 60 971idle timeout, that is, you want to be called when there have been,
952seconds of inactivity on the socket. The easiest way to do this is to 972say, 60 seconds of inactivity on the socket. The easiest way to do
953configure an \f(CW\*(C`ev_timer\*(C'\fR with after=repeat=60 and calling ev_timer_again each 973this 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
954time you successfully read or write some data. If you go into an idle 974\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
955state where you do not expect data to travel on the socket, you can stop 975you go into an idle state where you do not expect data to travel on the
956the timer, and again will automatically restart it if need be. 976socket, you can stop the timer, and again will automatically restart it if
977need be.
978.Sp
979You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether
980and only ever use the \f(CW\*(C`repeat\*(C'\fR value:
981.Sp
982.Vb 8
983\& ev_timer_init (timer, callback, 0., 5.);
984\& ev_timer_again (loop, timer);
985\& ...
986\& timer->again = 17.;
987\& ev_timer_again (loop, timer);
988\& ...
989\& timer->again = 10.;
990\& ev_timer_again (loop, timer);
991.Ve
992.Sp
993This is more efficient then stopping/starting the timer eahc time you want
994to modify its timeout value.
995.IP "ev_tstamp repeat [read\-write]" 4
996.IX Item "ev_tstamp repeat [read-write]"
997The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
998or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
999which is also when any modifications are taken into account.
957.PP 1000.PP
958Example: create a timer that fires after 60 seconds. 1001Example: create a timer that fires after 60 seconds.
959.PP 1002.PP
960.Vb 5 1003.Vb 5
961\& static void 1004\& static void
1093.IX Item "ev_periodic_again (loop, ev_periodic *)" 1136.IX Item "ev_periodic_again (loop, ev_periodic *)"
1094Simply stops and restarts the periodic watcher again. This is only useful 1137Simply stops and restarts the periodic watcher again. This is only useful
1095when you changed some parameters or the reschedule callback would return 1138when you changed some parameters or the reschedule callback would return
1096a different time than the last time it was called (e.g. in a crond like 1139a different time than the last time it was called (e.g. in a crond like
1097program when the crontabs have changed). 1140program when the crontabs have changed).
1141.IP "ev_tstamp interval [read\-write]" 4
1142.IX Item "ev_tstamp interval [read-write]"
1143The current interval value. Can be modified any time, but changes only
1144take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being
1145called.
1146.IP "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read\-write]" 4
1147.IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]"
1148The current reschedule callback, or \f(CW0\fR, if this functionality is
1149switched off. Can be changed any time, but changes only take effect when
1150the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1098.PP 1151.PP
1099Example: call a callback every hour, or, more precisely, whenever the 1152Example: call a callback every hour, or, more precisely, whenever the
1100system clock is divisible by 3600. The callback invocation times have 1153system clock is divisible by 3600. The callback invocation times have
1101potentially a lot of jittering, but good long-term stability. 1154potentially a lot of jittering, but good long-term stability.
1102.PP 1155.PP
1160.IP "ev_signal_set (ev_signal *, int signum)" 4 1213.IP "ev_signal_set (ev_signal *, int signum)" 4
1161.IX Item "ev_signal_set (ev_signal *, int signum)" 1214.IX Item "ev_signal_set (ev_signal *, int signum)"
1162.PD 1215.PD
1163Configures the watcher to trigger on the given signal number (usually one 1216Configures the watcher to trigger on the given signal number (usually one
1164of the \f(CW\*(C`SIGxxx\*(C'\fR constants). 1217of the \f(CW\*(C`SIGxxx\*(C'\fR constants).
1218.IP "int signum [read\-only]" 4
1219.IX Item "int signum [read-only]"
1220The signal the watcher watches out for.
1165.ie n .Sh """ev_child"" \- watch out for process status changes" 1221.ie n .Sh """ev_child"" \- watch out for process status changes"
1166.el .Sh "\f(CWev_child\fP \- watch out for process status changes" 1222.el .Sh "\f(CWev_child\fP \- watch out for process status changes"
1167.IX Subsection "ev_child - watch out for process status changes" 1223.IX Subsection "ev_child - watch out for process status changes"
1168Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to 1224Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to
1169some child status changes (most typically when a child of yours dies). 1225some child status changes (most typically when a child of yours dies).
1177\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look 1233\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look
1178at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see 1234at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see
1179the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems 1235the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems
1180\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the 1236\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the
1181process causing the status change. 1237process causing the status change.
1238.IP "int pid [read\-only]" 4
1239.IX Item "int pid [read-only]"
1240The process id this watcher watches out for, or \f(CW0\fR, meaning any process id.
1241.IP "int rpid [read\-write]" 4
1242.IX Item "int rpid [read-write]"
1243The process id that detected a status change.
1244.IP "int rstatus [read\-write]" 4
1245.IX Item "int rstatus [read-write]"
1246The process exit/trace status caused by \f(CW\*(C`rpid\*(C'\fR (see your systems
1247\&\f(CW\*(C`waitpid\*(C'\fR and \f(CW\*(C`sys/wait.h\*(C'\fR documentation for details).
1182.PP 1248.PP
1183Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. 1249Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0.
1184.PP 1250.PP
1185.Vb 5 1251.Vb 5
1186\& static void 1252\& static void
1192.PP 1258.PP
1193.Vb 3 1259.Vb 3
1194\& struct ev_signal signal_watcher; 1260\& struct ev_signal signal_watcher;
1195\& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); 1261\& ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1196\& ev_signal_start (loop, &sigint_cb); 1262\& ev_signal_start (loop, &sigint_cb);
1263.Ve
1264.ie n .Sh """ev_stat"" \- did the file attributes just change?"
1265.el .Sh "\f(CWev_stat\fP \- did the file attributes just change?"
1266.IX Subsection "ev_stat - did the file attributes just change?"
1267This watches a filesystem path for attribute changes. That is, it calls
1268\&\f(CW\*(C`stat\*(C'\fR regularly (or when the \s-1OS\s0 says it changed) and sees if it changed
1269compared to the last time, invoking the callback if it did.
1270.PP
1271The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does
1272not exist\*(R" is a status change like any other. The condition \*(L"path does
1273not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is
1274otherwise always forced to be at least one) and all the other fields of
1275the stat buffer having unspecified contents.
1276.PP
1277Since there is no standard to do this, the portable implementation simply
1278calls \f(CW\*(C`stat (2)\*(C'\fR regulalry on the path to see if it changed somehow. You
1279can specify a recommended polling interval for this case. If you specify
1280a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable,
1281unspecified default\fR value will be used (which you can expect to be around
1282five seconds, although this might change dynamically). Libev will also
1283impose a minimum interval which is currently around \f(CW0.1\fR, but thats
1284usually overkill.
1285.PP
1286This watcher type is not meant for massive numbers of stat watchers,
1287as even with OS-supported change notifications, this can be
1288resource\-intensive.
1289.PP
1290At the time of this writing, no specific \s-1OS\s0 backends are implemented, but
1291if demand increases, at least a kqueue and inotify backend will be added.
1292.IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4
1293.IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)"
1294.PD 0
1295.IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4
1296.IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)"
1297.PD
1298Configures the watcher to wait for status changes of the given
1299\&\f(CW\*(C`path\*(C'\fR. The \f(CW\*(C`interval\*(C'\fR is a hint on how quickly a change is expected to
1300be detected and should normally be specified as \f(CW0\fR to let libev choose
1301a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same
1302path for as long as the watcher is active.
1303.Sp
1304The callback will be receive \f(CW\*(C`EV_STAT\*(C'\fR when a change was detected,
1305relative to the attributes at the time the watcher was started (or the
1306last change was detected).
1307.IP "ev_stat_stat (ev_stat *)" 4
1308.IX Item "ev_stat_stat (ev_stat *)"
1309Updates the stat buffer immediately with new values. If you change the
1310watched path in your callback, you could call this fucntion to avoid
1311detecting this change (while introducing a race condition). Can also be
1312useful simply to find out the new values.
1313.IP "ev_statdata attr [read\-only]" 4
1314.IX Item "ev_statdata attr [read-only]"
1315The most-recently detected attributes of the file. Although the type is of
1316\&\f(CW\*(C`ev_statdata\*(C'\fR, this is usually the (or one of the) \f(CW\*(C`struct stat\*(C'\fR types
1317suitable for your system. If the \f(CW\*(C`st_nlink\*(C'\fR member is \f(CW0\fR, then there
1318was some error while \f(CW\*(C`stat\*(C'\fRing the file.
1319.IP "ev_statdata prev [read\-only]" 4
1320.IX Item "ev_statdata prev [read-only]"
1321The previous attributes of the file. The callback gets invoked whenever
1322\&\f(CW\*(C`prev\*(C'\fR != \f(CW\*(C`attr\*(C'\fR.
1323.IP "ev_tstamp interval [read\-only]" 4
1324.IX Item "ev_tstamp interval [read-only]"
1325The specified interval.
1326.IP "const char *path [read\-only]" 4
1327.IX Item "const char *path [read-only]"
1328The filesystem path that is being watched.
1329.PP
1330Example: Watch \f(CW\*(C`/etc/passwd\*(C'\fR for attribute changes.
1331.PP
1332.Vb 15
1333\& static void
1334\& passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
1335\& {
1336\& /* /etc/passwd changed in some way */
1337\& if (w->attr.st_nlink)
1338\& {
1339\& printf ("passwd current size %ld\en", (long)w->attr.st_size);
1340\& printf ("passwd current atime %ld\en", (long)w->attr.st_mtime);
1341\& printf ("passwd current mtime %ld\en", (long)w->attr.st_mtime);
1342\& }
1343\& else
1344\& /* you shalt not abuse printf for puts */
1345\& puts ("wow, /etc/passwd is not there, expect problems. "
1346\& "if this is windows, they already arrived\en");
1347\& }
1348.Ve
1349.PP
1350.Vb 2
1351\& ...
1352\& ev_stat passwd;
1353.Ve
1354.PP
1355.Vb 2
1356\& ev_stat_init (&passwd, passwd_cb, "/etc/passwd");
1357\& ev_stat_start (loop, &passwd);
1197.Ve 1358.Ve
1198.ie n .Sh """ev_idle"" \- when you've got nothing better to do..." 1359.ie n .Sh """ev_idle"" \- when you've got nothing better to do..."
1199.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." 1360.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..."
1200.IX Subsection "ev_idle - when you've got nothing better to do..." 1361.IX Subsection "ev_idle - when you've got nothing better to do..."
1201Idle watchers trigger events when there are no other events are pending 1362Idle watchers trigger events when there are no other events are pending
1449.IP "ev_embed_sweep (loop, ev_embed *)" 4 1610.IP "ev_embed_sweep (loop, ev_embed *)" 4
1450.IX Item "ev_embed_sweep (loop, ev_embed *)" 1611.IX Item "ev_embed_sweep (loop, ev_embed *)"
1451Make a single, non-blocking sweep over the embedded loop. This works 1612Make a single, non-blocking sweep over the embedded loop. This works
1452similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most 1613similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most
1453apropriate way for embedded loops. 1614apropriate way for embedded loops.
1615.IP "struct ev_loop *loop [read\-only]" 4
1616.IX Item "struct ev_loop *loop [read-only]"
1617The embedded event loop.
1454.SH "OTHER FUNCTIONS" 1618.SH "OTHER FUNCTIONS"
1455.IX Header "OTHER FUNCTIONS" 1619.IX Header "OTHER FUNCTIONS"
1456There are some other functions of possible interest. Described. Here. Now. 1620There are some other functions of possible interest. Described. Here. Now.
1457.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 1621.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4
1458.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 1622.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)"
1839If undefined or defined to \f(CW1\fR, then all event-loop-specific functions 2003If undefined or defined to \f(CW1\fR, then all event-loop-specific functions
1840will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create 2004will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create
1841additional independent event loops. Otherwise there will be no support 2005additional independent event loops. Otherwise there will be no support
1842for multiple event loops and there is no first event loop pointer 2006for multiple event loops and there is no first event loop pointer
1843argument. Instead, all functions act on the single default loop. 2007argument. Instead, all functions act on the single default loop.
1844.IP "\s-1EV_PERIODICS\s0" 4 2008.IP "\s-1EV_PERIODIC_ENABLE\s0" 4
1845.IX Item "EV_PERIODICS" 2009.IX Item "EV_PERIODIC_ENABLE"
1846If undefined or defined to be \f(CW1\fR, then periodic timers are supported, 2010If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If
1847otherwise not. This saves a few kb of code. 2011defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2012code.
2013.IP "\s-1EV_EMBED_ENABLE\s0" 4
2014.IX Item "EV_EMBED_ENABLE"
2015If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If
2016defined to be \f(CW0\fR, then they are not.
2017.IP "\s-1EV_STAT_ENABLE\s0" 4
2018.IX Item "EV_STAT_ENABLE"
2019If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If
2020defined to be \f(CW0\fR, then they are not.
2021.IP "\s-1EV_MINIMAL\s0" 4
2022.IX Item "EV_MINIMAL"
2023If you need to shave off some kilobytes of code at the expense of some
2024speed, define this symbol to \f(CW1\fR. Currently only used for gcc to override
2025some inlining decisions, saves roughly 30% codesize of amd64.
1848.IP "\s-1EV_COMMON\s0" 4 2026.IP "\s-1EV_COMMON\s0" 4
1849.IX Item "EV_COMMON" 2027.IX Item "EV_COMMON"
1850By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining 2028By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining
1851this macro to a something else you can include more and other types of 2029this macro to a something else you can include more and other types of
1852members. You have to define it each time you include one of the files, 2030members. You have to define it each time you include one of the files,

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines