| … | |
… | |
| 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-24" "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" |
| 134 | libev \- a high performance full\-featured event loop written in C |
134 | libev \- 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 |
| … | |
… | |
| 684 | The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread. |
684 | The 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" |
| 688 | The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change. |
688 | The 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" |
|
|
692 | The 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" |
| 692 | The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do. |
696 | The \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 |
| … | |
… | |
| 717 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, |
721 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, |
| 718 | for example it might indicate that a fd is readable or writable, and if |
722 | for example it might indicate that a fd is readable or writable, and if |
| 719 | your callbacks is well-written it can just attempt the operation and cope |
723 | your callbacks is well-written it can just attempt the operation and cope |
| 720 | with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded |
724 | with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded |
| 721 | programs, though, so beware. |
725 | programs, though, so beware. |
| 722 | .Sh "\s-1SUMMARY\s0 \s-1OF\s0 \s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
726 | .Sh "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
| 723 | .IX Subsection "SUMMARY OF GENERIC WATCHER FUNCTIONS" |
727 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
| 724 | In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type, |
728 | In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type, |
| 725 | e.g. \f(CW\*(C`timer\*(C'\fR for \f(CW\*(C`ev_timer\*(C'\fR watchers and \f(CW\*(C`io\*(C'\fR for \f(CW\*(C`ev_io\*(C'\fR watchers. |
729 | e.g. \f(CW\*(C`timer\*(C'\fR for \f(CW\*(C`ev_timer\*(C'\fR watchers and \f(CW\*(C`io\*(C'\fR for \f(CW\*(C`ev_io\*(C'\fR watchers. |
| 726 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
730 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
| 727 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
731 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
| 728 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
732 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
| … | |
… | |
| 734 | which rolls both calls into one. |
738 | which rolls both calls into one. |
| 735 | .Sp |
739 | .Sp |
| 736 | You can reinitialise a watcher at any time as long as it has been stopped |
740 | You can reinitialise a watcher at any time as long as it has been stopped |
| 737 | (or never started) and there are no pending events outstanding. |
741 | (or never started) and there are no pending events outstanding. |
| 738 | .Sp |
742 | .Sp |
| 739 | The callbakc is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher, |
743 | The callback is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher, |
| 740 | int revents)\*(C'\fR. |
744 | int revents)\*(C'\fR. |
| 741 | .ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4 |
745 | .ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4 |
| 742 | .el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4 |
746 | .el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4 |
| 743 | .IX Item "ev_TYPE_set (ev_TYPE *, [args])" |
747 | .IX Item "ev_TYPE_set (ev_TYPE *, [args])" |
| 744 | This macro initialises the type-specific parts of a watcher. You need to |
748 | This macro initialises the type-specific parts of a watcher. You need to |
| … | |
… | |
| 821 | More interesting and less C\-conformant ways of catsing your callback type |
825 | More interesting and less C\-conformant ways of catsing your callback type |
| 822 | have been omitted.... |
826 | have been omitted.... |
| 823 | .SH "WATCHER TYPES" |
827 | .SH "WATCHER TYPES" |
| 824 | .IX Header "WATCHER TYPES" |
828 | .IX Header "WATCHER TYPES" |
| 825 | This section describes each watcher in detail, but will not repeat |
829 | This section describes each watcher in detail, but will not repeat |
| 826 | information given in the last section. |
830 | information given in the last section. Any initialisation/set macros, |
|
|
831 | functions and members specific to the watcher type are explained. |
|
|
832 | .PP |
|
|
833 | Members are additionally marked with either \fI[read\-only]\fR, meaning that, |
|
|
834 | while the watcher is active, you can look at the member and expect some |
|
|
835 | sensible content, but you must not modify it (you can modify it while the |
|
|
836 | watcher is stopped to your hearts content), or \fI[read\-write]\fR, which |
|
|
837 | means you can expect it to have some sensible content while the watcher |
|
|
838 | is active, but you can also modify it. Modifying it may not do something |
|
|
839 | sensible or take immediate effect (or do anything at all), but libev will |
|
|
840 | not 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?" |
| 830 | I/O watchers check whether a file descriptor is readable or writable |
844 | I/O watchers check whether a file descriptor is readable or writable |
| 831 | in each iteration of the event loop (This behaviour is called |
845 | in each iteration of the event loop, or, more precisely, when reading |
| 832 | level-triggering because you keep receiving events as long as the |
846 | would not block the process and writing would at least be able to write |
| 833 | condition persists. Remember you can stop the watcher if you don't want to |
847 | some data. This behaviour is called level-triggering because you keep |
| 834 | act on the event and neither want to receive future events). |
848 | receiving events as long as the condition persists. Remember you can stop |
|
|
849 | the watcher if you don't want to act on the event and neither want to |
|
|
850 | receive future events. |
| 835 | .PP |
851 | .PP |
| 836 | In general you can register as many read and/or write event watchers per |
852 | In general you can register as many read and/or write event watchers per |
| 837 | fd as you want (as long as you don't confuse yourself). Setting all file |
853 | fd as you want (as long as you don't confuse yourself). Setting all file |
| 838 | descriptors to non-blocking mode is also usually a good idea (but not |
854 | descriptors to non-blocking mode is also usually a good idea (but not |
| 839 | required if you know what you are doing). |
855 | required if you know what you are doing). |
| 840 | .PP |
856 | .PP |
| 841 | You have to be careful with dup'ed file descriptors, though. Some backends |
857 | You have to be careful with dup'ed file descriptors, though. Some backends |
| 842 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
858 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
| 843 | descriptors correctly if you register interest in two or more fds pointing |
859 | descriptors correctly if you register interest in two or more fds pointing |
| 844 | to the same underlying file/socket etc. description (that is, they share |
860 | to the same underlying file/socket/etc. description (that is, they share |
| 845 | the same underlying \*(L"file open\*(R"). |
861 | the same underlying \*(L"file open\*(R"). |
| 846 | .PP |
862 | .PP |
| 847 | If you must do this, then force the use of a known-to-be-good backend |
863 | If you must do this, then force the use of a known-to-be-good backend |
| 848 | (at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and |
864 | (at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and |
| 849 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR). |
865 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR). |
|
|
866 | .PP |
|
|
867 | Another thing you have to watch out for is that it is quite easy to |
|
|
868 | receive \*(L"spurious\*(R" readyness notifications, that is your callback might |
|
|
869 | be called with \f(CW\*(C`EV_READ\*(C'\fR but a subsequent \f(CW\*(C`read\*(C'\fR(2) will actually block |
|
|
870 | because there is no data. Not only are some backends known to create a |
|
|
871 | lot of those (for example solaris ports), it is very easy to get into |
|
|
872 | this situation even with a relatively standard program structure. Thus |
|
|
873 | it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning |
|
|
874 | \&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. |
|
|
875 | .PP |
|
|
876 | If you cannot run the fd in non-blocking mode (for example you should not |
|
|
877 | play around with an Xlib connection), then you have to seperately re-test |
|
|
878 | wether a file descriptor is really ready with a known-to-be good interface |
|
|
879 | such as poll (fortunately in our Xlib example, Xlib already does this on |
|
|
880 | its own, so its quite safe to use). |
| 850 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
881 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
| 851 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
882 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
| 852 | .PD 0 |
883 | .PD 0 |
| 853 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
884 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
| 854 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
885 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
| 855 | .PD |
886 | .PD |
| 856 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The fd is the file descriptor to rceeive |
887 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
| 857 | events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_READ | |
888 | rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or |
| 858 | EV_WRITE\*(C'\fR to receive the given events. |
889 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events. |
| 859 | .Sp |
890 | .IP "int fd [read\-only]" 4 |
| 860 | Please note that most of the more scalable backend mechanisms (for example |
891 | .IX Item "int fd [read-only]" |
| 861 | epoll and solaris ports) can result in spurious readyness notifications |
892 | The file descriptor being watched. |
| 862 | for file descriptors, so you practically need to use non-blocking I/O (and |
893 | .IP "int events [read\-only]" 4 |
| 863 | treat callback invocation as hint only), or retest separately with a safe |
894 | .IX Item "int events [read-only]" |
| 864 | interface before doing I/O (XLib can do this), or force the use of either |
895 | The events being watched. |
| 865 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR, which don't suffer from this |
|
|
| 866 | problem. Also note that it is quite easy to have your callback invoked |
|
|
| 867 | when the readyness condition is no longer valid even when employing |
|
|
| 868 | typical ways of handling events, so its a good idea to use non-blocking |
|
|
| 869 | I/O unconditionally. |
|
|
| 870 | .PP |
896 | .PP |
| 871 | Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
897 | Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
| 872 | readable, but only once. Since it is likely line\-buffered, you could |
898 | readable, but only once. Since it is likely line\-buffered, you could |
| 873 | attempt to read a whole line in the callback: |
899 | attempt to read a whole line in the callback: |
| 874 | .PP |
900 | .PP |
| … | |
… | |
| 887 | \& struct ev_io stdin_readable; |
913 | \& struct ev_io stdin_readable; |
| 888 | \& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
914 | \& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
| 889 | \& ev_io_start (loop, &stdin_readable); |
915 | \& ev_io_start (loop, &stdin_readable); |
| 890 | \& ev_loop (loop, 0); |
916 | \& ev_loop (loop, 0); |
| 891 | .Ve |
917 | .Ve |
| 892 | .ie n .Sh """ev_timer"" \- relative and optionally recurring timeouts" |
918 | .ie n .Sh """ev_timer"" \- relative and optionally repeating timeouts" |
| 893 | .el .Sh "\f(CWev_timer\fP \- relative and optionally recurring timeouts" |
919 | .el .Sh "\f(CWev_timer\fP \- relative and optionally repeating timeouts" |
| 894 | .IX Subsection "ev_timer - relative and optionally recurring timeouts" |
920 | .IX Subsection "ev_timer - relative and optionally repeating timeouts" |
| 895 | Timer watchers are simple relative timers that generate an event after a |
921 | Timer watchers are simple relative timers that generate an event after a |
| 896 | given time, and optionally repeating in regular intervals after that. |
922 | given time, and optionally repeating in regular intervals after that. |
| 897 | .PP |
923 | .PP |
| 898 | The timers are based on real time, that is, if you register an event that |
924 | The timers are based on real time, that is, if you register an event that |
| 899 | times out after an hour and you reset your system clock to last years |
925 | times out after an hour and you reset your system clock to last years |
| … | |
… | |
| 939 | .Sp |
965 | .Sp |
| 940 | If the timer is repeating, either start it if necessary (with the repeat |
966 | If the timer is repeating, either start it if necessary (with the repeat |
| 941 | value), or reset the running timer to the repeat value. |
967 | value), or reset the running timer to the repeat value. |
| 942 | .Sp |
968 | .Sp |
| 943 | This sounds a bit complicated, but here is a useful and typical |
969 | This sounds a bit complicated, but here is a useful and typical |
| 944 | example: Imagine you have a tcp connection and you want a so-called idle |
970 | example: Imagine you have a tcp connection and you want a so-called |
| 945 | timeout, that is, you want to be called when there have been, say, 60 |
971 | idle timeout, that is, you want to be called when there have been, |
| 946 | seconds of inactivity on the socket. The easiest way to do this is to |
972 | say, 60 seconds of inactivity on the socket. The easiest way to do |
| 947 | configure an \f(CW\*(C`ev_timer\*(C'\fR with after=repeat=60 and calling ev_timer_again each |
973 | this 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 |
| 948 | time 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 |
| 949 | state where you do not expect data to travel on the socket, you can stop |
975 | you go into an idle state where you do not expect data to travel on the |
| 950 | the timer, and again will automatically restart it if need be. |
976 | socket, you can stop the timer, and again will automatically restart it if |
|
|
977 | need be. |
|
|
978 | .Sp |
|
|
979 | You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether |
|
|
980 | and 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 |
|
|
993 | This is more efficient then stopping/starting the timer eahc time you want |
|
|
994 | to modify its timeout value. |
|
|
995 | .IP "ev_tstamp repeat [read\-write]" 4 |
|
|
996 | .IX Item "ev_tstamp repeat [read-write]" |
|
|
997 | The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out |
|
|
998 | or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), |
|
|
999 | which is also when any modifications are taken into account. |
| 951 | .PP |
1000 | .PP |
| 952 | Example: create a timer that fires after 60 seconds. |
1001 | Example: create a timer that fires after 60 seconds. |
| 953 | .PP |
1002 | .PP |
| 954 | .Vb 5 |
1003 | .Vb 5 |
| 955 | \& static void |
1004 | \& static void |
| … | |
… | |
| 986 | .Vb 3 |
1035 | .Vb 3 |
| 987 | \& // and in some piece of code that gets executed on any "activity": |
1036 | \& // and in some piece of code that gets executed on any "activity": |
| 988 | \& // reset the timeout to start ticking again at 10 seconds |
1037 | \& // reset the timeout to start ticking again at 10 seconds |
| 989 | \& ev_timer_again (&mytimer); |
1038 | \& ev_timer_again (&mytimer); |
| 990 | .Ve |
1039 | .Ve |
| 991 | .ie n .Sh """ev_periodic"" \- to cron or not to cron" |
1040 | .ie n .Sh """ev_periodic"" \- to cron or not to cron?" |
| 992 | .el .Sh "\f(CWev_periodic\fP \- to cron or not to cron" |
1041 | .el .Sh "\f(CWev_periodic\fP \- to cron or not to cron?" |
| 993 | .IX Subsection "ev_periodic - to cron or not to cron" |
1042 | .IX Subsection "ev_periodic - to cron or not to cron?" |
| 994 | Periodic watchers are also timers of a kind, but they are very versatile |
1043 | Periodic watchers are also timers of a kind, but they are very versatile |
| 995 | (and unfortunately a bit complex). |
1044 | (and unfortunately a bit complex). |
| 996 | .PP |
1045 | .PP |
| 997 | Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) |
1046 | Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) |
| 998 | but on wallclock time (absolute time). You can tell a periodic watcher |
1047 | but on wallclock time (absolute time). You can tell a periodic watcher |
| … | |
… | |
| 1087 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
1136 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
| 1088 | Simply stops and restarts the periodic watcher again. This is only useful |
1137 | Simply stops and restarts the periodic watcher again. This is only useful |
| 1089 | when you changed some parameters or the reschedule callback would return |
1138 | when you changed some parameters or the reschedule callback would return |
| 1090 | a different time than the last time it was called (e.g. in a crond like |
1139 | a different time than the last time it was called (e.g. in a crond like |
| 1091 | program when the crontabs have changed). |
1140 | program when the crontabs have changed). |
|
|
1141 | .IP "ev_tstamp interval [read\-write]" 4 |
|
|
1142 | .IX Item "ev_tstamp interval [read-write]" |
|
|
1143 | The current interval value. Can be modified any time, but changes only |
|
|
1144 | take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being |
|
|
1145 | called. |
|
|
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]" |
|
|
1148 | The current reschedule callback, or \f(CW0\fR, if this functionality is |
|
|
1149 | switched off. Can be changed any time, but changes only take effect when |
|
|
1150 | the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called. |
| 1092 | .PP |
1151 | .PP |
| 1093 | Example: call a callback every hour, or, more precisely, whenever the |
1152 | Example: call a callback every hour, or, more precisely, whenever the |
| 1094 | system clock is divisible by 3600. The callback invocation times have |
1153 | system clock is divisible by 3600. The callback invocation times have |
| 1095 | potentially a lot of jittering, but good long-term stability. |
1154 | potentially a lot of jittering, but good long-term stability. |
| 1096 | .PP |
1155 | .PP |
| … | |
… | |
| 1132 | \& struct ev_periodic hourly_tick; |
1191 | \& struct ev_periodic hourly_tick; |
| 1133 | \& ev_periodic_init (&hourly_tick, clock_cb, |
1192 | \& ev_periodic_init (&hourly_tick, clock_cb, |
| 1134 | \& fmod (ev_now (loop), 3600.), 3600., 0); |
1193 | \& fmod (ev_now (loop), 3600.), 3600., 0); |
| 1135 | \& ev_periodic_start (loop, &hourly_tick); |
1194 | \& ev_periodic_start (loop, &hourly_tick); |
| 1136 | .Ve |
1195 | .Ve |
| 1137 | .ie n .Sh """ev_signal"" \- signal me when a signal gets signalled" |
1196 | .ie n .Sh """ev_signal"" \- signal me when a signal gets signalled!" |
| 1138 | .el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled" |
1197 | .el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled!" |
| 1139 | .IX Subsection "ev_signal - signal me when a signal gets signalled" |
1198 | .IX Subsection "ev_signal - signal me when a signal gets signalled!" |
| 1140 | Signal watchers will trigger an event when the process receives a specific |
1199 | Signal watchers will trigger an event when the process receives a specific |
| 1141 | signal one or more times. Even though signals are very asynchronous, libev |
1200 | signal one or more times. Even though signals are very asynchronous, libev |
| 1142 | will try it's best to deliver signals synchronously, i.e. as part of the |
1201 | will try it's best to deliver signals synchronously, i.e. as part of the |
| 1143 | normal event processing, like any other event. |
1202 | normal event processing, like any other event. |
| 1144 | .PP |
1203 | .PP |
| … | |
… | |
| 1154 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
1213 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
| 1155 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
1214 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
| 1156 | .PD |
1215 | .PD |
| 1157 | Configures the watcher to trigger on the given signal number (usually one |
1216 | Configures the watcher to trigger on the given signal number (usually one |
| 1158 | of the \f(CW\*(C`SIGxxx\*(C'\fR constants). |
1217 | of the \f(CW\*(C`SIGxxx\*(C'\fR constants). |
|
|
1218 | .IP "int signum [read\-only]" 4 |
|
|
1219 | .IX Item "int signum [read-only]" |
|
|
1220 | The signal the watcher watches out for. |
| 1159 | .ie n .Sh """ev_child"" \- wait for pid status changes" |
1221 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
| 1160 | .el .Sh "\f(CWev_child\fP \- wait for pid status changes" |
1222 | .el .Sh "\f(CWev_child\fP \- watch out for process status changes" |
| 1161 | .IX Subsection "ev_child - wait for pid status changes" |
1223 | .IX Subsection "ev_child - watch out for process status changes" |
| 1162 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
1224 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
| 1163 | some child status changes (most typically when a child of yours dies). |
1225 | some child status changes (most typically when a child of yours dies). |
| 1164 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
1226 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
| 1165 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
1227 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
| 1166 | .PD 0 |
1228 | .PD 0 |
| … | |
… | |
| 1171 | \&\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 |
| 1172 | at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see |
1234 | at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see |
| 1173 | the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems |
1235 | the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems |
| 1174 | \&\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 |
| 1175 | process causing the status change. |
1237 | process causing the status change. |
|
|
1238 | .IP "int pid [read\-only]" 4 |
|
|
1239 | .IX Item "int pid [read-only]" |
|
|
1240 | The 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]" |
|
|
1243 | The process id that detected a status change. |
|
|
1244 | .IP "int rstatus [read\-write]" 4 |
|
|
1245 | .IX Item "int rstatus [read-write]" |
|
|
1246 | The 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). |
| 1176 | .PP |
1248 | .PP |
| 1177 | Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. |
1249 | Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. |
| 1178 | .PP |
1250 | .PP |
| 1179 | .Vb 5 |
1251 | .Vb 5 |
| 1180 | \& static void |
1252 | \& static void |
| … | |
… | |
| 1187 | .Vb 3 |
1259 | .Vb 3 |
| 1188 | \& struct ev_signal signal_watcher; |
1260 | \& struct ev_signal signal_watcher; |
| 1189 | \& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1261 | \& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
| 1190 | \& ev_signal_start (loop, &sigint_cb); |
1262 | \& ev_signal_start (loop, &sigint_cb); |
| 1191 | .Ve |
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?" |
|
|
1267 | This 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 |
|
|
1269 | compared to the last time, invoking the callback if it did. |
|
|
1270 | .PP |
|
|
1271 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
|
|
1272 | not exist\*(R" is a status change like any other. The condition \*(L"path does |
|
|
1273 | not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is |
|
|
1274 | otherwise always forced to be at least one) and all the other fields of |
|
|
1275 | the stat buffer having unspecified contents. |
|
|
1276 | .PP |
|
|
1277 | Since there is no standard to do this, the portable implementation simply |
|
|
1278 | calls \f(CW\*(C`stat (2)\*(C'\fR regulalry on the path to see if it changed somehow. You |
|
|
1279 | can specify a recommended polling interval for this case. If you specify |
|
|
1280 | a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, |
|
|
1281 | unspecified default\fR value will be used (which you can expect to be around |
|
|
1282 | five seconds, although this might change dynamically). Libev will also |
|
|
1283 | impose a minimum interval which is currently around \f(CW0.1\fR, but thats |
|
|
1284 | usually overkill. |
|
|
1285 | .PP |
|
|
1286 | This watcher type is not meant for massive numbers of stat watchers, |
|
|
1287 | as even with OS-supported change notifications, this can be |
|
|
1288 | resource\-intensive. |
|
|
1289 | .PP |
|
|
1290 | At the time of this writing, no specific \s-1OS\s0 backends are implemented, but |
|
|
1291 | if 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 |
|
|
1298 | Configures 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 |
|
|
1300 | be detected and should normally be specified as \f(CW0\fR to let libev choose |
|
|
1301 | a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same |
|
|
1302 | path for as long as the watcher is active. |
|
|
1303 | .Sp |
|
|
1304 | The callback will be receive \f(CW\*(C`EV_STAT\*(C'\fR when a change was detected, |
|
|
1305 | relative to the attributes at the time the watcher was started (or the |
|
|
1306 | last change was detected). |
|
|
1307 | .IP "ev_stat_stat (ev_stat *)" 4 |
|
|
1308 | .IX Item "ev_stat_stat (ev_stat *)" |
|
|
1309 | Updates the stat buffer immediately with new values. If you change the |
|
|
1310 | watched path in your callback, you could call this fucntion to avoid |
|
|
1311 | detecting this change (while introducing a race condition). Can also be |
|
|
1312 | useful simply to find out the new values. |
|
|
1313 | .IP "ev_statdata attr [read\-only]" 4 |
|
|
1314 | .IX Item "ev_statdata attr [read-only]" |
|
|
1315 | The 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 |
|
|
1317 | suitable for your system. If the \f(CW\*(C`st_nlink\*(C'\fR member is \f(CW0\fR, then there |
|
|
1318 | was 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]" |
|
|
1321 | The 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]" |
|
|
1325 | The specified interval. |
|
|
1326 | .IP "const char *path [read\-only]" 4 |
|
|
1327 | .IX Item "const char *path [read-only]" |
|
|
1328 | The filesystem path that is being watched. |
|
|
1329 | .PP |
|
|
1330 | Example: 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); |
|
|
1358 | .Ve |
| 1192 | .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..." |
| 1193 | .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..." |
| 1194 | .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..." |
| 1195 | Idle watchers trigger events when there are no other events are pending |
1362 | Idle watchers trigger events when there are no other events are pending |
| 1196 | (prepare, check and other idle watchers do not count). That is, as long |
1363 | (prepare, check and other idle watchers do not count). That is, as long |
| 1197 | as your process is busy handling sockets or timeouts (or even signals, |
1364 | as your process is busy handling sockets or timeouts (or even signals, |
| 1198 | imagine) it will not be triggered. But when your process is idle all idle |
1365 | imagine) it will not be triggered. But when your process is idle all idle |
| 1199 | watchers are being called again and again, once per event loop iteration \- |
1366 | watchers are being called again and again, once per event loop iteration \- |
| … | |
… | |
| 1229 | .Vb 3 |
1396 | .Vb 3 |
| 1230 | \& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1397 | \& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
| 1231 | \& ev_idle_init (idle_watcher, idle_cb); |
1398 | \& ev_idle_init (idle_watcher, idle_cb); |
| 1232 | \& ev_idle_start (loop, idle_cb); |
1399 | \& ev_idle_start (loop, idle_cb); |
| 1233 | .Ve |
1400 | .Ve |
| 1234 | .ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop" |
1401 | .ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop!" |
| 1235 | .el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop" |
1402 | .el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!" |
| 1236 | .IX Subsection "ev_prepare and ev_check - customise your event loop" |
1403 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
| 1237 | Prepare and check watchers are usually (but not always) used in tandem: |
1404 | Prepare and check watchers are usually (but not always) used in tandem: |
| 1238 | prepare watchers get invoked before the process blocks and check watchers |
1405 | prepare watchers get invoked before the process blocks and check watchers |
| 1239 | afterwards. |
1406 | afterwards. |
| 1240 | .PP |
1407 | .PP |
|
|
1408 | You \fImust not\fR call \f(CW\*(C`ev_loop\*(C'\fR or similar functions that enter |
|
|
1409 | the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR |
|
|
1410 | watchers. Other loops than the current one are fine, however. The |
|
|
1411 | rationale behind this is that you do not need to check for recursion in |
|
|
1412 | those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, |
|
|
1413 | \&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be |
|
|
1414 | called in pairs bracketing the blocking call. |
|
|
1415 | .PP |
| 1241 | Their main purpose is to integrate other event mechanisms into libev and |
1416 | Their main purpose is to integrate other event mechanisms into libev and |
| 1242 | their use is somewhat advanced. This could be used, for example, to track |
1417 | their use is somewhat advanced. This could be used, for example, to track |
| 1243 | variable changes, implement your own watchers, integrate net-snmp or a |
1418 | variable changes, implement your own watchers, integrate net-snmp or a |
| 1244 | coroutine library and lots more. |
1419 | coroutine library and lots more. They are also occasionally useful if |
|
|
1420 | you cache some data and want to flush it before blocking (for example, |
|
|
1421 | in X programs you might want to do an \f(CW\*(C`XFlush ()\*(C'\fR in an \f(CW\*(C`ev_prepare\*(C'\fR |
|
|
1422 | watcher). |
| 1245 | .PP |
1423 | .PP |
| 1246 | This is done by examining in each prepare call which file descriptors need |
1424 | This is done by examining in each prepare call which file descriptors need |
| 1247 | to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for |
1425 | to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for |
| 1248 | them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries |
1426 | them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries |
| 1249 | provide just this functionality). Then, in the check watcher you check for |
1427 | provide just this functionality). Then, in the check watcher you check for |
| … | |
… | |
| 1268 | .PD |
1446 | .PD |
| 1269 | Initialises and configures the prepare or check watcher \- they have no |
1447 | Initialises and configures the prepare or check watcher \- they have no |
| 1270 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
1448 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
| 1271 | macros, but using them is utterly, utterly and completely pointless. |
1449 | macros, but using them is utterly, utterly and completely pointless. |
| 1272 | .PP |
1450 | .PP |
| 1273 | Example: *TODO*. |
1451 | Example: To include a library such as adns, you would add \s-1IO\s0 watchers |
|
|
1452 | and a timeout watcher in a prepare handler, as required by libadns, and |
|
|
1453 | in a check watcher, destroy them and call into libadns. What follows is |
|
|
1454 | pseudo-code only of course: |
|
|
1455 | .PP |
|
|
1456 | .Vb 2 |
|
|
1457 | \& static ev_io iow [nfd]; |
|
|
1458 | \& static ev_timer tw; |
|
|
1459 | .Ve |
|
|
1460 | .PP |
|
|
1461 | .Vb 9 |
|
|
1462 | \& static void |
|
|
1463 | \& io_cb (ev_loop *loop, ev_io *w, int revents) |
|
|
1464 | \& { |
|
|
1465 | \& // set the relevant poll flags |
|
|
1466 | \& // could also call adns_processreadable etc. here |
|
|
1467 | \& struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1468 | \& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1469 | \& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1470 | \& } |
|
|
1471 | .Ve |
|
|
1472 | .PP |
|
|
1473 | .Vb 7 |
|
|
1474 | \& // create io watchers for each fd and a timer before blocking |
|
|
1475 | \& static void |
|
|
1476 | \& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
|
|
1477 | \& { |
|
|
1478 | \& int timeout = 3600000;truct pollfd fds [nfd]; |
|
|
1479 | \& // actual code will need to loop here and realloc etc. |
|
|
1480 | \& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
|
|
1481 | .Ve |
|
|
1482 | .PP |
|
|
1483 | .Vb 3 |
|
|
1484 | \& /* the callback is illegal, but won't be called as we stop during check */ |
|
|
1485 | \& ev_timer_init (&tw, 0, timeout * 1e-3); |
|
|
1486 | \& ev_timer_start (loop, &tw); |
|
|
1487 | .Ve |
|
|
1488 | .PP |
|
|
1489 | .Vb 6 |
|
|
1490 | \& // create on ev_io per pollfd |
|
|
1491 | \& for (int i = 0; i < nfd; ++i) |
|
|
1492 | \& { |
|
|
1493 | \& ev_io_init (iow + i, io_cb, fds [i].fd, |
|
|
1494 | \& ((fds [i].events & POLLIN ? EV_READ : 0) |
|
|
1495 | \& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
|
|
1496 | .Ve |
|
|
1497 | .PP |
|
|
1498 | .Vb 5 |
|
|
1499 | \& fds [i].revents = 0; |
|
|
1500 | \& iow [i].data = fds + i; |
|
|
1501 | \& ev_io_start (loop, iow + i); |
|
|
1502 | \& } |
|
|
1503 | \& } |
|
|
1504 | .Ve |
|
|
1505 | .PP |
|
|
1506 | .Vb 5 |
|
|
1507 | \& // stop all watchers after blocking |
|
|
1508 | \& static void |
|
|
1509 | \& adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
|
|
1510 | \& { |
|
|
1511 | \& ev_timer_stop (loop, &tw); |
|
|
1512 | .Ve |
|
|
1513 | .PP |
|
|
1514 | .Vb 2 |
|
|
1515 | \& for (int i = 0; i < nfd; ++i) |
|
|
1516 | \& ev_io_stop (loop, iow + i); |
|
|
1517 | .Ve |
|
|
1518 | .PP |
|
|
1519 | .Vb 2 |
|
|
1520 | \& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1521 | \& } |
|
|
1522 | .Ve |
| 1274 | .ie n .Sh """ev_embed"" \- when one backend isn't enough" |
1523 | .ie n .Sh """ev_embed"" \- when one backend isn't enough..." |
| 1275 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough" |
1524 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." |
| 1276 | .IX Subsection "ev_embed - when one backend isn't enough" |
1525 | .IX Subsection "ev_embed - when one backend isn't enough..." |
| 1277 | This is a rather advanced watcher type that lets you embed one event loop |
1526 | This is a rather advanced watcher type that lets you embed one event loop |
| 1278 | into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded |
1527 | into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded |
| 1279 | loop, other types of watchers might be handled in a delayed or incorrect |
1528 | loop, other types of watchers might be handled in a delayed or incorrect |
| 1280 | fashion and must not be used). |
1529 | fashion and must not be used). |
| 1281 | .PP |
1530 | .PP |
| … | |
… | |
| 1361 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
1610 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
| 1362 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
1611 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
| 1363 | Make a single, non-blocking sweep over the embedded loop. This works |
1612 | Make a single, non-blocking sweep over the embedded loop. This works |
| 1364 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
1613 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
| 1365 | apropriate way for embedded loops. |
1614 | apropriate way for embedded loops. |
|
|
1615 | .IP "struct ev_loop *loop [read\-only]" 4 |
|
|
1616 | .IX Item "struct ev_loop *loop [read-only]" |
|
|
1617 | The embedded event loop. |
| 1366 | .SH "OTHER FUNCTIONS" |
1618 | .SH "OTHER FUNCTIONS" |
| 1367 | .IX Header "OTHER FUNCTIONS" |
1619 | .IX Header "OTHER FUNCTIONS" |
| 1368 | There are some other functions of possible interest. Described. Here. Now. |
1620 | There are some other functions of possible interest. Described. Here. Now. |
| 1369 | .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 |
| 1370 | .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)" |
| … | |
… | |
| 1536 | \& idle (this, &myclass::idle_cb) |
1788 | \& idle (this, &myclass::idle_cb) |
| 1537 | \& { |
1789 | \& { |
| 1538 | \& io.start (fd, ev::READ); |
1790 | \& io.start (fd, ev::READ); |
| 1539 | \& } |
1791 | \& } |
| 1540 | .Ve |
1792 | .Ve |
|
|
1793 | .SH "EMBEDDING" |
|
|
1794 | .IX Header "EMBEDDING" |
|
|
1795 | Libev can (and often is) directly embedded into host |
|
|
1796 | applications. Examples of applications that embed it include the Deliantra |
|
|
1797 | Game Server, the \s-1EV\s0 perl module, the \s-1GNU\s0 Virtual Private Ethernet (gvpe) |
|
|
1798 | and rxvt\-unicode. |
|
|
1799 | .PP |
|
|
1800 | The goal is to enable you to just copy the neecssary files into your |
|
|
1801 | source directory without having to change even a single line in them, so |
|
|
1802 | you can easily upgrade by simply copying (or having a checked-out copy of |
|
|
1803 | libev somewhere in your source tree). |
|
|
1804 | .Sh "\s-1FILESETS\s0" |
|
|
1805 | .IX Subsection "FILESETS" |
|
|
1806 | Depending on what features you need you need to include one or more sets of files |
|
|
1807 | in your app. |
|
|
1808 | .PP |
|
|
1809 | \fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR |
|
|
1810 | .IX Subsection "CORE EVENT LOOP" |
|
|
1811 | .PP |
|
|
1812 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
|
|
1813 | configuration (no autoconf): |
|
|
1814 | .PP |
|
|
1815 | .Vb 2 |
|
|
1816 | \& #define EV_STANDALONE 1 |
|
|
1817 | \& #include "ev.c" |
|
|
1818 | .Ve |
|
|
1819 | .PP |
|
|
1820 | This will automatically include \fIev.h\fR, too, and should be done in a |
|
|
1821 | single C source file only to provide the function implementations. To use |
|
|
1822 | it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best |
|
|
1823 | done by writing a wrapper around \fIev.h\fR that you can include instead and |
|
|
1824 | where you can put other configuration options): |
|
|
1825 | .PP |
|
|
1826 | .Vb 2 |
|
|
1827 | \& #define EV_STANDALONE 1 |
|
|
1828 | \& #include "ev.h" |
|
|
1829 | .Ve |
|
|
1830 | .PP |
|
|
1831 | Both header files and implementation files can be compiled with a \*(C+ |
|
|
1832 | compiler (at least, thats a stated goal, and breakage will be treated |
|
|
1833 | as a bug). |
|
|
1834 | .PP |
|
|
1835 | You need the following files in your source tree, or in a directory |
|
|
1836 | in your include path (e.g. in libev/ when using \-Ilibev): |
|
|
1837 | .PP |
|
|
1838 | .Vb 4 |
|
|
1839 | \& ev.h |
|
|
1840 | \& ev.c |
|
|
1841 | \& ev_vars.h |
|
|
1842 | \& ev_wrap.h |
|
|
1843 | .Ve |
|
|
1844 | .PP |
|
|
1845 | .Vb 1 |
|
|
1846 | \& ev_win32.c required on win32 platforms only |
|
|
1847 | .Ve |
|
|
1848 | .PP |
|
|
1849 | .Vb 5 |
|
|
1850 | \& ev_select.c only when select backend is enabled (which is by default) |
|
|
1851 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
|
|
1852 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
|
|
1853 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
|
|
1854 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
|
|
1855 | .Ve |
|
|
1856 | .PP |
|
|
1857 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
|
|
1858 | to compile this single file. |
|
|
1859 | .PP |
|
|
1860 | \fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR |
|
|
1861 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
|
|
1862 | .PP |
|
|
1863 | To include the libevent compatibility \s-1API\s0, also include: |
|
|
1864 | .PP |
|
|
1865 | .Vb 1 |
|
|
1866 | \& #include "event.c" |
|
|
1867 | .Ve |
|
|
1868 | .PP |
|
|
1869 | in the file including \fIev.c\fR, and: |
|
|
1870 | .PP |
|
|
1871 | .Vb 1 |
|
|
1872 | \& #include "event.h" |
|
|
1873 | .Ve |
|
|
1874 | .PP |
|
|
1875 | in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. |
|
|
1876 | .PP |
|
|
1877 | You need the following additional files for this: |
|
|
1878 | .PP |
|
|
1879 | .Vb 2 |
|
|
1880 | \& event.h |
|
|
1881 | \& event.c |
|
|
1882 | .Ve |
|
|
1883 | .PP |
|
|
1884 | \fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR |
|
|
1885 | .IX Subsection "AUTOCONF SUPPORT" |
|
|
1886 | .PP |
|
|
1887 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your config in |
|
|
1888 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
|
|
1889 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
|
|
1890 | include \fIconfig.h\fR and configure itself accordingly. |
|
|
1891 | .PP |
|
|
1892 | For this of course you need the m4 file: |
|
|
1893 | .PP |
|
|
1894 | .Vb 1 |
|
|
1895 | \& libev.m4 |
|
|
1896 | .Ve |
|
|
1897 | .Sh "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" |
|
|
1898 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
|
|
1899 | Libev can be configured via a variety of preprocessor symbols you have to define |
|
|
1900 | before including any of its files. The default is not to build for multiplicity |
|
|
1901 | and only include the select backend. |
|
|
1902 | .IP "\s-1EV_STANDALONE\s0" 4 |
|
|
1903 | .IX Item "EV_STANDALONE" |
|
|
1904 | Must always be \f(CW1\fR if you do not use autoconf configuration, which |
|
|
1905 | keeps libev from including \fIconfig.h\fR, and it also defines dummy |
|
|
1906 | implementations for some libevent functions (such as logging, which is not |
|
|
1907 | supported). It will also not define any of the structs usually found in |
|
|
1908 | \&\fIevent.h\fR that are not directly supported by the libev core alone. |
|
|
1909 | .IP "\s-1EV_USE_MONOTONIC\s0" 4 |
|
|
1910 | .IX Item "EV_USE_MONOTONIC" |
|
|
1911 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
|
|
1912 | monotonic clock option at both compiletime and runtime. Otherwise no use |
|
|
1913 | of the monotonic clock option will be attempted. If you enable this, you |
|
|
1914 | usually have to link against librt or something similar. Enabling it when |
|
|
1915 | the functionality isn't available is safe, though, althoguh you have |
|
|
1916 | to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR |
|
|
1917 | function is hiding in (often \fI\-lrt\fR). |
|
|
1918 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
|
|
1919 | .IX Item "EV_USE_REALTIME" |
|
|
1920 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
|
|
1921 | realtime clock option at compiletime (and assume its availability at |
|
|
1922 | runtime if successful). Otherwise no use of the realtime clock option will |
|
|
1923 | be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get |
|
|
1924 | (CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See tzhe note about libraries |
|
|
1925 | in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though. |
|
|
1926 | .IP "\s-1EV_USE_SELECT\s0" 4 |
|
|
1927 | .IX Item "EV_USE_SELECT" |
|
|
1928 | If undefined or defined to be \f(CW1\fR, libev will compile in support for the |
|
|
1929 | \&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no |
|
|
1930 | other method takes over, select will be it. Otherwise the select backend |
|
|
1931 | will not be compiled in. |
|
|
1932 | .IP "\s-1EV_SELECT_USE_FD_SET\s0" 4 |
|
|
1933 | .IX Item "EV_SELECT_USE_FD_SET" |
|
|
1934 | If defined to \f(CW1\fR, then the select backend will use the system \f(CW\*(C`fd_set\*(C'\fR |
|
|
1935 | structure. This is useful if libev doesn't compile due to a missing |
|
|
1936 | \&\f(CW\*(C`NFDBITS\*(C'\fR or \f(CW\*(C`fd_mask\*(C'\fR definition or it misguesses the bitset layout on |
|
|
1937 | exotic systems. This usually limits the range of file descriptors to some |
|
|
1938 | low limit such as 1024 or might have other limitations (winsocket only |
|
|
1939 | allows 64 sockets). The \f(CW\*(C`FD_SETSIZE\*(C'\fR macro, set before compilation, might |
|
|
1940 | influence the size of the \f(CW\*(C`fd_set\*(C'\fR used. |
|
|
1941 | .IP "\s-1EV_SELECT_IS_WINSOCKET\s0" 4 |
|
|
1942 | .IX Item "EV_SELECT_IS_WINSOCKET" |
|
|
1943 | When defined to \f(CW1\fR, the select backend will assume that |
|
|
1944 | select/socket/connect etc. don't understand file descriptors but |
|
|
1945 | wants osf handles on win32 (this is the case when the select to |
|
|
1946 | be used is the winsock select). This means that it will call |
|
|
1947 | \&\f(CW\*(C`_get_osfhandle\*(C'\fR on the fd to convert it to an \s-1OS\s0 handle. Otherwise, |
|
|
1948 | it is assumed that all these functions actually work on fds, even |
|
|
1949 | on win32. Should not be defined on non\-win32 platforms. |
|
|
1950 | .IP "\s-1EV_USE_POLL\s0" 4 |
|
|
1951 | .IX Item "EV_USE_POLL" |
|
|
1952 | If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2) |
|
|
1953 | backend. Otherwise it will be enabled on non\-win32 platforms. It |
|
|
1954 | takes precedence over select. |
|
|
1955 | .IP "\s-1EV_USE_EPOLL\s0" 4 |
|
|
1956 | .IX Item "EV_USE_EPOLL" |
|
|
1957 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
|
|
1958 | \&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime, |
|
|
1959 | otherwise another method will be used as fallback. This is the |
|
|
1960 | preferred backend for GNU/Linux systems. |
|
|
1961 | .IP "\s-1EV_USE_KQUEUE\s0" 4 |
|
|
1962 | .IX Item "EV_USE_KQUEUE" |
|
|
1963 | If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style |
|
|
1964 | \&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime, |
|
|
1965 | otherwise another method will be used as fallback. This is the preferred |
|
|
1966 | backend for \s-1BSD\s0 and BSD-like systems, although on most BSDs kqueue only |
|
|
1967 | supports some types of fds correctly (the only platform we found that |
|
|
1968 | supports ptys for example was NetBSD), so kqueue might be compiled in, but |
|
|
1969 | not be used unless explicitly requested. The best way to use it is to find |
|
|
1970 | out whether kqueue supports your type of fd properly and use an embedded |
|
|
1971 | kqueue loop. |
|
|
1972 | .IP "\s-1EV_USE_PORT\s0" 4 |
|
|
1973 | .IX Item "EV_USE_PORT" |
|
|
1974 | If defined to be \f(CW1\fR, libev will compile in support for the Solaris |
|
|
1975 | 10 port style backend. Its availability will be detected at runtime, |
|
|
1976 | otherwise another method will be used as fallback. This is the preferred |
|
|
1977 | backend for Solaris 10 systems. |
|
|
1978 | .IP "\s-1EV_USE_DEVPOLL\s0" 4 |
|
|
1979 | .IX Item "EV_USE_DEVPOLL" |
|
|
1980 | reserved for future expansion, works like the \s-1USE\s0 symbols above. |
|
|
1981 | .IP "\s-1EV_H\s0" 4 |
|
|
1982 | .IX Item "EV_H" |
|
|
1983 | The name of the \fIev.h\fR header file used to include it. The default if |
|
|
1984 | undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This |
|
|
1985 | can be used to virtually rename the \fIev.h\fR header file in case of conflicts. |
|
|
1986 | .IP "\s-1EV_CONFIG_H\s0" 4 |
|
|
1987 | .IX Item "EV_CONFIG_H" |
|
|
1988 | If \f(CW\*(C`EV_STANDALONE\*(C'\fR isn't \f(CW1\fR, this variable can be used to override |
|
|
1989 | \&\fIev.c\fR's idea of where to find the \fIconfig.h\fR file, similarly to |
|
|
1990 | \&\f(CW\*(C`EV_H\*(C'\fR, above. |
|
|
1991 | .IP "\s-1EV_EVENT_H\s0" 4 |
|
|
1992 | .IX Item "EV_EVENT_H" |
|
|
1993 | Similarly to \f(CW\*(C`EV_H\*(C'\fR, this macro can be used to override \fIevent.c\fR's idea |
|
|
1994 | of how the \fIevent.h\fR header can be found. |
|
|
1995 | .IP "\s-1EV_PROTOTYPES\s0" 4 |
|
|
1996 | .IX Item "EV_PROTOTYPES" |
|
|
1997 | If defined to be \f(CW0\fR, then \fIev.h\fR will not define any function |
|
|
1998 | prototypes, but still define all the structs and other symbols. This is |
|
|
1999 | occasionally useful if you want to provide your own wrapper functions |
|
|
2000 | around libev functions. |
|
|
2001 | .IP "\s-1EV_MULTIPLICITY\s0" 4 |
|
|
2002 | .IX Item "EV_MULTIPLICITY" |
|
|
2003 | If undefined or defined to \f(CW1\fR, then all event-loop-specific functions |
|
|
2004 | will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create |
|
|
2005 | additional independent event loops. Otherwise there will be no support |
|
|
2006 | for multiple event loops and there is no first event loop pointer |
|
|
2007 | argument. Instead, all functions act on the single default loop. |
|
|
2008 | .IP "\s-1EV_PERIODIC_ENABLE\s0" 4 |
|
|
2009 | .IX Item "EV_PERIODIC_ENABLE" |
|
|
2010 | If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If |
|
|
2011 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
|
|
2012 | code. |
|
|
2013 | .IP "\s-1EV_EMBED_ENABLE\s0" 4 |
|
|
2014 | .IX Item "EV_EMBED_ENABLE" |
|
|
2015 | If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If |
|
|
2016 | defined to be \f(CW0\fR, then they are not. |
|
|
2017 | .IP "\s-1EV_STAT_ENABLE\s0" 4 |
|
|
2018 | .IX Item "EV_STAT_ENABLE" |
|
|
2019 | If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If |
|
|
2020 | defined to be \f(CW0\fR, then they are not. |
|
|
2021 | .IP "\s-1EV_MINIMAL\s0" 4 |
|
|
2022 | .IX Item "EV_MINIMAL" |
|
|
2023 | If you need to shave off some kilobytes of code at the expense of some |
|
|
2024 | speed, define this symbol to \f(CW1\fR. Currently only used for gcc to override |
|
|
2025 | some inlining decisions, saves roughly 30% codesize of amd64. |
|
|
2026 | .IP "\s-1EV_COMMON\s0" 4 |
|
|
2027 | .IX Item "EV_COMMON" |
|
|
2028 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
|
|
2029 | this macro to a something else you can include more and other types of |
|
|
2030 | members. You have to define it each time you include one of the files, |
|
|
2031 | though, and it must be identical each time. |
|
|
2032 | .Sp |
|
|
2033 | For example, the perl \s-1EV\s0 module uses something like this: |
|
|
2034 | .Sp |
|
|
2035 | .Vb 3 |
|
|
2036 | \& #define EV_COMMON \e |
|
|
2037 | \& SV *self; /* contains this struct */ \e |
|
|
2038 | \& SV *cb_sv, *fh /* note no trailing ";" */ |
|
|
2039 | .Ve |
|
|
2040 | .IP "\s-1EV_CB_DECLARE\s0 (type)" 4 |
|
|
2041 | .IX Item "EV_CB_DECLARE (type)" |
|
|
2042 | .PD 0 |
|
|
2043 | .IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4 |
|
|
2044 | .IX Item "EV_CB_INVOKE (watcher, revents)" |
|
|
2045 | .IP "ev_set_cb (ev, cb)" 4 |
|
|
2046 | .IX Item "ev_set_cb (ev, cb)" |
|
|
2047 | .PD |
|
|
2048 | Can be used to change the callback member declaration in each watcher, |
|
|
2049 | and the way callbacks are invoked and set. Must expand to a struct member |
|
|
2050 | definition and a statement, respectively. See the \fIev.v\fR header file for |
|
|
2051 | their default definitions. One possible use for overriding these is to |
|
|
2052 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
|
|
2053 | method calls instead of plain function calls in \*(C+. |
|
|
2054 | .Sh "\s-1EXAMPLES\s0" |
|
|
2055 | .IX Subsection "EXAMPLES" |
|
|
2056 | For a real-world example of a program the includes libev |
|
|
2057 | verbatim, you can have a look at the \s-1EV\s0 perl module |
|
|
2058 | (<http://software.schmorp.de/pkg/EV.html>). It has the libev files in |
|
|
2059 | the \fIlibev/\fR subdirectory and includes them in the \fI\s-1EV/EVAPI\s0.h\fR (public |
|
|
2060 | interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file |
|
|
2061 | will be compiled. It is pretty complex because it provides its own header |
|
|
2062 | file. |
|
|
2063 | .Sp |
|
|
2064 | The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file |
|
|
2065 | that everybody includes and which overrides some autoconf choices: |
|
|
2066 | .Sp |
|
|
2067 | .Vb 4 |
|
|
2068 | \& #define EV_USE_POLL 0 |
|
|
2069 | \& #define EV_MULTIPLICITY 0 |
|
|
2070 | \& #define EV_PERIODICS 0 |
|
|
2071 | \& #define EV_CONFIG_H <config.h> |
|
|
2072 | .Ve |
|
|
2073 | .Sp |
|
|
2074 | .Vb 1 |
|
|
2075 | \& #include "ev++.h" |
|
|
2076 | .Ve |
|
|
2077 | .Sp |
|
|
2078 | And a \fIev_cpp.C\fR implementation file that contains libev proper and is compiled: |
|
|
2079 | .Sp |
|
|
2080 | .Vb 2 |
|
|
2081 | \& #include "ev_cpp.h" |
|
|
2082 | \& #include "ev.c" |
|
|
2083 | .Ve |
|
|
2084 | .SH "COMPLEXITIES" |
|
|
2085 | .IX Header "COMPLEXITIES" |
|
|
2086 | In this section the complexities of (many of) the algorithms used inside |
|
|
2087 | libev will be explained. For complexity discussions about backends see the |
|
|
2088 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
|
|
2089 | .RS 4 |
|
|
2090 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
|
|
2091 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
|
|
2092 | .PD 0 |
|
|
2093 | .IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4 |
|
|
2094 | .IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" |
|
|
2095 | .IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 |
|
|
2096 | .IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" |
|
|
2097 | .IP "Stopping check/prepare/idle watchers: O(1)" 4 |
|
|
2098 | .IX Item "Stopping check/prepare/idle watchers: O(1)" |
|
|
2099 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" 4 |
|
|
2100 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" |
|
|
2101 | .IP "Finding the next timer per loop iteration: O(1)" 4 |
|
|
2102 | .IX Item "Finding the next timer per loop iteration: O(1)" |
|
|
2103 | .IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 |
|
|
2104 | .IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" |
|
|
2105 | .IP "Activating one watcher: O(1)" 4 |
|
|
2106 | .IX Item "Activating one watcher: O(1)" |
|
|
2107 | .RE |
|
|
2108 | .RS 4 |
|
|
2109 | .PD |
| 1541 | .SH "AUTHOR" |
2110 | .SH "AUTHOR" |
| 1542 | .IX Header "AUTHOR" |
2111 | .IX Header "AUTHOR" |
| 1543 | Marc Lehmann <libev@schmorp.de>. |
2112 | Marc Lehmann <libev@schmorp.de>. |
