ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.144 by root, Mon Apr 7 12:33:29 2008 UTC vs.
Revision 1.212 by root, Mon Nov 3 15:13:53 2008 UTC

…		…
2		2
3	libev - a high performance full-featured event loop written in C	3	libev - a high performance full-featured event loop written in C
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	#include <ev.h>	7	#include <ev.h>
8		8
9	=head2 EXAMPLE PROGRAM	9	=head2 EXAMPLE PROGRAM
10		10
11	// a single header file is required	11	// a single header file is required
12	#include <ev.h>	12	#include <ev.h>
13		13
14	// every watcher type has its own typedef'd struct	14	// every watcher type has its own typedef'd struct
15	// with the name ev_<type>	15	// with the name ev_TYPE
16	ev_io stdin_watcher;	16	ev_io stdin_watcher;
17	ev_timer timeout_watcher;	17	ev_timer timeout_watcher;
18		18
19	// all watcher callbacks have a similar signature	19	// all watcher callbacks have a similar signature
20	// this callback is called when data is readable on stdin	20	// this callback is called when data is readable on stdin
21	static void	21	static void
22	stdin_cb (EV_P_ struct ev_io *w, int revents)	22	stdin_cb (EV_P_ ev_io *w, int revents)
23	{	23	{
24	puts ("stdin ready");	24	puts ("stdin ready");
25	// for one-shot events, one must manually stop the watcher	25	// for one-shot events, one must manually stop the watcher
26	// with its corresponding stop function.	26	// with its corresponding stop function.
27	ev_io_stop (EV_A_ w);	27	ev_io_stop (EV_A_ w);
28		28
29	// this causes all nested ev_loop's to stop iterating	29	// this causes all nested ev_loop's to stop iterating
30	ev_unloop (EV_A_ EVUNLOOP_ALL);	30	ev_unloop (EV_A_ EVUNLOOP_ALL);
31	}	31	}
32		32
33	// another callback, this time for a time-out	33	// another callback, this time for a time-out
34	static void	34	static void
35	timeout_cb (EV_P_ struct ev_timer *w, int revents)	35	timeout_cb (EV_P_ ev_timer *w, int revents)
36	{	36	{
37	puts ("timeout");	37	puts ("timeout");
38	// this causes the innermost ev_loop to stop iterating	38	// this causes the innermost ev_loop to stop iterating
39	ev_unloop (EV_A_ EVUNLOOP_ONE);	39	ev_unloop (EV_A_ EVUNLOOP_ONE);
40	}	40	}
41		41
42	int	42	int
43	main (void)	43	main (void)
44	{	44	{
45	// use the default event loop unless you have special needs	45	// use the default event loop unless you have special needs
46	struct ev_loop *loop = ev_default_loop (0);	46	ev_loop *loop = ev_default_loop (0);
47		47
48	// initialise an io watcher, then start it	48	// initialise an io watcher, then start it
49	// this one will watch for stdin to become readable	49	// this one will watch for stdin to become readable
50	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);	50	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
51	ev_io_start (loop, &stdin_watcher);	51	ev_io_start (loop, &stdin_watcher);
52		52
53	// initialise a timer watcher, then start it	53	// initialise a timer watcher, then start it
54	// simple non-repeating 5.5 second timeout	54	// simple non-repeating 5.5 second timeout
55	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);	55	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
56	ev_timer_start (loop, &timeout_watcher);	56	ev_timer_start (loop, &timeout_watcher);
57		57
58	// now wait for events to arrive	58	// now wait for events to arrive
59	ev_loop (loop, 0);	59	ev_loop (loop, 0);
60		60
61	// unloop was called, so exit	61	// unloop was called, so exit
62	return 0;	62	return 0;
63	}	63	}
64		64
65	=head1 DESCRIPTION	65	=head1 DESCRIPTION
66		66
67	The newest version of this document is also available as an html-formatted	67	The newest version of this document is also available as an html-formatted
68	web page you might find easier to navigate when reading it for the first	68	web page you might find easier to navigate when reading it for the first
69	time: L<http://cvs.schmorp.de/libev/ev.html>.	69	time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>.
70		70
71	Libev is an event loop: you register interest in certain events (such as a	71	Libev is an event loop: you register interest in certain events (such as a
72	file descriptor being readable or a timeout occurring), and it will manage	72	file descriptor being readable or a timeout occurring), and it will manage
73	these event sources and provide your program with events.	73	these event sources and provide your program with events.
74		74
…		…
103	Libev is very configurable. In this manual the default (and most common)	103	Libev is very configurable. In this manual the default (and most common)
104	configuration will be described, which supports multiple event loops. For	104	configuration will be described, which supports multiple event loops. For
105	more info about various configuration options please have a look at	105	more info about various configuration options please have a look at
106	B<EMBED> section in this manual. If libev was configured without support	106	B<EMBED> section in this manual. If libev was configured without support
107	for multiple event loops, then all functions taking an initial argument of	107	for multiple event loops, then all functions taking an initial argument of
108	name C<loop> (which is always of type C<struct ev_loop *>) will not have	108	name C<loop> (which is always of type C<ev_loop *>) will not have
109	this argument.	109	this argument.
110		110
111	=head2 TIME REPRESENTATION	111	=head2 TIME REPRESENTATION
112		112
113	Libev represents time as a single floating point number, representing the	113	Libev represents time as a single floating point number, representing the
114	(fractional) number of seconds since the (POSIX) epoch (somewhere near	114	(fractional) number of seconds since the (POSIX) epoch (somewhere near
115	the beginning of 1970, details are complicated, don't ask). This type is	115	the beginning of 1970, details are complicated, don't ask). This type is
116	called C<ev_tstamp>, which is what you should use too. It usually aliases	116	called C<ev_tstamp>, which is what you should use too. It usually aliases
117	to the C<double> type in C, and when you need to do any calculations on	117	to the C<double> type in C, and when you need to do any calculations on
118	it, you should treat it as some floatingpoint value. Unlike the name	118	it, you should treat it as some floating point value. Unlike the name
119	component C<stamp> might indicate, it is also used for time differences	119	component C<stamp> might indicate, it is also used for time differences
120	throughout libev.	120	throughout libev.
		121
		122	=head1 ERROR HANDLING
		123
		124	Libev knows three classes of errors: operating system errors, usage errors
		125	and internal errors (bugs).
		126
		127	When libev catches an operating system error it cannot handle (for example
		128	a system call indicating a condition libev cannot fix), it calls the callback
		129	set via C<ev_set_syserr_cb>, which is supposed to fix the problem or
		130	abort. The default is to print a diagnostic message and to call C<abort
		131	()>.
		132
		133	When libev detects a usage error such as a negative timer interval, then
		134	it will print a diagnostic message and abort (via the C<assert> mechanism,
		135	so C<NDEBUG> will disable this checking): these are programming errors in
		136	the libev caller and need to be fixed there.
		137
		138	Libev also has a few internal error-checking C<assert>ions, and also has
		139	extensive consistency checking code. These do not trigger under normal
		140	circumstances, as they indicate either a bug in libev or worse.
		141
121		142
122	=head1 GLOBAL FUNCTIONS	143	=head1 GLOBAL FUNCTIONS
123		144
124	These functions can be called anytime, even before initialising the	145	These functions can be called anytime, even before initialising the
125	library in any way.	146	library in any way.
…		…
134		155
135	=item ev_sleep (ev_tstamp interval)	156	=item ev_sleep (ev_tstamp interval)
136		157
137	Sleep for the given interval: The current thread will be blocked until	158	Sleep for the given interval: The current thread will be blocked until
138	either it is interrupted or the given time interval has passed. Basically	159	either it is interrupted or the given time interval has passed. Basically
139	this is a subsecond-resolution C<sleep ()>.	160	this is a sub-second-resolution C<sleep ()>.
140		161
141	=item int ev_version_major ()	162	=item int ev_version_major ()
142		163
143	=item int ev_version_minor ()	164	=item int ev_version_minor ()
144		165
…		…
157	not a problem.	178	not a problem.
158		179
159	Example: Make sure we haven't accidentally been linked against the wrong	180	Example: Make sure we haven't accidentally been linked against the wrong
160	version.	181	version.
161		182
162	assert (("libev version mismatch",	183	assert (("libev version mismatch",
163	ev_version_major () == EV_VERSION_MAJOR	184	ev_version_major () == EV_VERSION_MAJOR
164	&& ev_version_minor () >= EV_VERSION_MINOR));	185	&& ev_version_minor () >= EV_VERSION_MINOR));
165		186
166	=item unsigned int ev_supported_backends ()	187	=item unsigned int ev_supported_backends ()
167		188
168	Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>	189	Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
169	value) compiled into this binary of libev (independent of their	190	value) compiled into this binary of libev (independent of their
…		…
171	a description of the set values.	192	a description of the set values.
172		193
173	Example: make sure we have the epoll method, because yeah this is cool and	194	Example: make sure we have the epoll method, because yeah this is cool and
174	a must have and can we have a torrent of it please!!!11	195	a must have and can we have a torrent of it please!!!11
175		196
176	assert (("sorry, no epoll, no sex",	197	assert (("sorry, no epoll, no sex",
177	ev_supported_backends () & EVBACKEND_EPOLL));	198	ev_supported_backends () & EVBACKEND_EPOLL));
178		199
179	=item unsigned int ev_recommended_backends ()	200	=item unsigned int ev_recommended_backends ()
180		201
181	Return the set of all backends compiled into this binary of libev and also	202	Return the set of all backends compiled into this binary of libev and also
182	recommended for this platform. This set is often smaller than the one	203	recommended for this platform. This set is often smaller than the one
183	returned by C<ev_supported_backends>, as for example kqueue is broken on	204	returned by C<ev_supported_backends>, as for example kqueue is broken on
184	most BSDs and will not be autodetected unless you explicitly request it	205	most BSDs and will not be auto-detected unless you explicitly request it
185	(assuming you know what you are doing). This is the set of backends that	206	(assuming you know what you are doing). This is the set of backends that
186	libev will probe for if you specify no backends explicitly.	207	libev will probe for if you specify no backends explicitly.
187		208
188	=item unsigned int ev_embeddable_backends ()	209	=item unsigned int ev_embeddable_backends ()
189		210
…		…
193	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	214	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for
194	recommended ones.	215	recommended ones.
195		216
196	See the description of C<ev_embed> watchers for more info.	217	See the description of C<ev_embed> watchers for more info.
197		218
198	=item ev_set_allocator (void *(*cb)(void *ptr, long size))	219	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]
199		220
200	Sets the allocation function to use (the prototype is similar - the	221	Sets the allocation function to use (the prototype is similar - the
201	semantics is identical - to the realloc C function). It is used to	222	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is
202	allocate and free memory (no surprises here). If it returns zero when	223	used to allocate and free memory (no surprises here). If it returns zero
203	memory needs to be allocated, the library might abort or take some	224	when memory needs to be allocated (C<size != 0>), the library might abort
204	potentially destructive action. The default is your system realloc	225	or take some potentially destructive action.
205	function.	226
		227	Since some systems (at least OpenBSD and Darwin) fail to implement
		228	correct C<realloc> semantics, libev will use a wrapper around the system
		229	C<realloc> and C<free> functions by default.
206		230
207	You could override this function in high-availability programs to, say,	231	You could override this function in high-availability programs to, say,
208	free some memory if it cannot allocate memory, to use a special allocator,	232	free some memory if it cannot allocate memory, to use a special allocator,
209	or even to sleep a while and retry until some memory is available.	233	or even to sleep a while and retry until some memory is available.
210		234
211	Example: Replace the libev allocator with one that waits a bit and then	235	Example: Replace the libev allocator with one that waits a bit and then
212	retries).	236	retries (example requires a standards-compliant C<realloc>).
213		237
214	static void *	238	static void *
215	persistent_realloc (void *ptr, size_t size)	239	persistent_realloc (void *ptr, size_t size)
216	{	240	{
217	for (;;)	241	for (;;)
…		…
226	}	250	}
227		251
228	...	252	...
229	ev_set_allocator (persistent_realloc);	253	ev_set_allocator (persistent_realloc);
230		254
231	=item ev_set_syserr_cb (void (*cb)(const char *msg));	255	=item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]
232		256
233	Set the callback function to call on a retryable syscall error (such	257	Set the callback function to call on a retryable system call error (such
234	as failed select, poll, epoll_wait). The message is a printable string	258	as failed select, poll, epoll_wait). The message is a printable string
235	indicating the system call or subsystem causing the problem. If this	259	indicating the system call or subsystem causing the problem. If this
236	callback is set, then libev will expect it to remedy the sitution, no	260	callback is set, then libev will expect it to remedy the situation, no
237	matter what, when it returns. That is, libev will generally retry the	261	matter what, when it returns. That is, libev will generally retry the
238	requested operation, or, if the condition doesn't go away, do bad stuff	262	requested operation, or, if the condition doesn't go away, do bad stuff
239	(such as abort).	263	(such as abort).
240		264
241	Example: This is basically the same thing that libev does internally, too.	265	Example: This is basically the same thing that libev does internally, too.
…		…
252		276
253	=back	277	=back
254		278
255	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	279	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP
256		280
257	An event loop is described by a C<struct ev_loop *>. The library knows two	281	An event loop is described by a C<struct ev_loop *> (the C<struct>
258	types of such loops, the I<default> loop, which supports signals and child	282	is I<not> optional in this case, as there is also an C<ev_loop>
259	events, and dynamically created loops which do not.	283	I<function>).
		284
		285	The library knows two types of such loops, the I<default> loop, which
		286	supports signals and child events, and dynamically created loops which do
		287	not.
260		288
261	=over 4	289	=over 4
262		290
263	=item struct ev_loop *ev_default_loop (unsigned int flags)	291	=item struct ev_loop *ev_default_loop (unsigned int flags)
264		292
…		…
270	If you don't know what event loop to use, use the one returned from this	298	If you don't know what event loop to use, use the one returned from this
271	function.	299	function.
272		300
273	Note that this function is I<not> thread-safe, so if you want to use it	301	Note that this function is I<not> thread-safe, so if you want to use it
274	from multiple threads, you have to lock (note also that this is unlikely,	302	from multiple threads, you have to lock (note also that this is unlikely,
275	as loops cannot bes hared easily between threads anyway).	303	as loops cannot be shared easily between threads anyway).
276		304
277	The default loop is the only loop that can handle C<ev_signal> and	305	The default loop is the only loop that can handle C<ev_signal> and
278	C<ev_child> watchers, and to do this, it always registers a handler	306	C<ev_child> watchers, and to do this, it always registers a handler
279	for C<SIGCHLD>. If this is a problem for your app you can either	307	for C<SIGCHLD>. If this is a problem for your application you can either
280	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	308	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
281	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	309	can simply overwrite the C<SIGCHLD> signal handler I<after> calling
282	C<ev_default_init>.	310	C<ev_default_init>.
283		311
284	The flags argument can be used to specify special behaviour or specific	312	The flags argument can be used to specify special behaviour or specific
…		…
293	The default flags value. Use this if you have no clue (it's the right	321	The default flags value. Use this if you have no clue (it's the right
294	thing, believe me).	322	thing, believe me).
295		323
296	=item C<EVFLAG_NOENV>	324	=item C<EVFLAG_NOENV>
297		325
298	If this flag bit is ored into the flag value (or the program runs setuid	326	If this flag bit is or'ed into the flag value (or the program runs setuid
299	or setgid) then libev will I<not> look at the environment variable	327	or setgid) then libev will I<not> look at the environment variable
300	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will	328	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
301	override the flags completely if it is found in the environment. This is	329	override the flags completely if it is found in the environment. This is
302	useful to try out specific backends to test their performance, or to work	330	useful to try out specific backends to test their performance, or to work
303	around bugs.	331	around bugs.
…		…
310		338
311	This works by calling C<getpid ()> on every iteration of the loop,	339	This works by calling C<getpid ()> on every iteration of the loop,
312	and thus this might slow down your event loop if you do a lot of loop	340	and thus this might slow down your event loop if you do a lot of loop
313	iterations and little real work, but is usually not noticeable (on my	341	iterations and little real work, but is usually not noticeable (on my
314	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence	342	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence
315	without a syscall and thus I<very> fast, but my GNU/Linux system also has	343	without a system call and thus I<very> fast, but my GNU/Linux system also has
316	C<pthread_atfork> which is even faster).	344	C<pthread_atfork> which is even faster).
317		345
318	The big advantage of this flag is that you can forget about fork (and	346	The big advantage of this flag is that you can forget about fork (and
319	forget about forgetting to tell libev about forking) when you use this	347	forget about forgetting to tell libev about forking) when you use this
320	flag.	348	flag.
321		349
322	This flag setting cannot be overriden or specified in the C<LIBEV_FLAGS>	350	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
323	environment variable.	351	environment variable.
324		352
325	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	353	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
326		354
327	This is your standard select(2) backend. Not I<completely> standard, as	355	This is your standard select(2) backend. Not I<completely> standard, as
…		…
329	but if that fails, expect a fairly low limit on the number of fds when	357	but if that fails, expect a fairly low limit on the number of fds when
330	using this backend. It doesn't scale too well (O(highest_fd)), but its	358	using this backend. It doesn't scale too well (O(highest_fd)), but its
331	usually the fastest backend for a low number of (low-numbered :) fds.	359	usually the fastest backend for a low number of (low-numbered :) fds.
332		360
333	To get good performance out of this backend you need a high amount of	361	To get good performance out of this backend you need a high amount of
334	parallelity (most of the file descriptors should be busy). If you are	362	parallelism (most of the file descriptors should be busy). If you are
335	writing a server, you should C<accept ()> in a loop to accept as many	363	writing a server, you should C<accept ()> in a loop to accept as many
336	connections as possible during one iteration. You might also want to have	364	connections as possible during one iteration. You might also want to have
337	a look at C<ev_set_io_collect_interval ()> to increase the amount of	365	a look at C<ev_set_io_collect_interval ()> to increase the amount of
338	readyness notifications you get per iteration.	366	readiness notifications you get per iteration.
		367
		368	This backend maps C<EV_READ> to the C<readfds> set and C<EV_WRITE> to the
		369	C<writefds> set (and to work around Microsoft Windows bugs, also onto the
		370	C<exceptfds> set on that platform).
339		371
340	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)	372	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
341		373
342	And this is your standard poll(2) backend. It's more complicated	374	And this is your standard poll(2) backend. It's more complicated
343	than select, but handles sparse fds better and has no artificial	375	than select, but handles sparse fds better and has no artificial
344	limit on the number of fds you can use (except it will slow down	376	limit on the number of fds you can use (except it will slow down
345	considerably with a lot of inactive fds). It scales similarly to select,	377	considerably with a lot of inactive fds). It scales similarly to select,
346	i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for	378	i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for
347	performance tips.	379	performance tips.
348		380
		381	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and
		382	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.
		383
349	=item C<EVBACKEND_EPOLL> (value 4, Linux)	384	=item C<EVBACKEND_EPOLL> (value 4, Linux)
350		385
351	For few fds, this backend is a bit little slower than poll and select,	386	For few fds, this backend is a bit little slower than poll and select,
352	but it scales phenomenally better. While poll and select usually scale	387	but it scales phenomenally better. While poll and select usually scale
353	like O(total_fds) where n is the total number of fds (or the highest fd),	388	like O(total_fds) where n is the total number of fds (or the highest fd),
354	epoll scales either O(1) or O(active_fds). The epoll design has a number	389	epoll scales either O(1) or O(active_fds).
355	of shortcomings, such as silently dropping events in some hard-to-detect	390
356	cases and requiring a syscall per fd change, no fork support and bad	391	The epoll mechanism deserves honorable mention as the most misdesigned
357	support for dup.	392	of the more advanced event mechanisms: mere annoyances include silently
		393	dropping file descriptors, requiring a system call per change per file
		394	descriptor (and unnecessary guessing of parameters), problems with dup and
		395	so on. The biggest issue is fork races, however - if a program forks then
		396	I<both> parent and child process have to recreate the epoll set, which can
		397	take considerable time (one syscall per file descriptor) and is of course
		398	hard to detect.
		399
		400	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
		401	of course I<doesn't>, and epoll just loves to report events for totally
		402	I<different> file descriptors (even already closed ones, so one cannot
		403	even remove them from the set) than registered in the set (especially
		404	on SMP systems). Libev tries to counter these spurious notifications by
		405	employing an additional generation counter and comparing that against the
		406	events to filter out spurious ones, recreating the set when required.
358		407
359	While stopping, setting and starting an I/O watcher in the same iteration	408	While stopping, setting and starting an I/O watcher in the same iteration
360	will result in some caching, there is still a syscall per such incident	409	will result in some caching, there is still a system call per such
361	(because the fd could point to a different file description now), so its	410	incident (because the same I<file descriptor> could point to a different
362	best to avoid that. Also, C<dup ()>'ed file descriptors might not work	411	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
363	very well if you register events for both fds.	412	file descriptors might not work very well if you register events for both
364		413	file descriptors.
365	Please note that epoll sometimes generates spurious notifications, so you
366	need to use non-blocking I/O or other means to avoid blocking when no data
367	(or space) is available.
368		414
369	Best performance from this backend is achieved by not unregistering all	415	Best performance from this backend is achieved by not unregistering all
370	watchers for a file descriptor until it has been closed, if possible, i.e.	416	watchers for a file descriptor until it has been closed, if possible,
371	keep at least one watcher active per fd at all times.	417	i.e. keep at least one watcher active per fd at all times. Stopping and
		418	starting a watcher (without re-setting it) also usually doesn't cause
		419	extra overhead. A fork can both result in spurious notifications as well
		420	as in libev having to destroy and recreate the epoll object, which can
		421	take considerable time and thus should be avoided.
372		422
373	While nominally embeddeble in other event loops, this feature is broken in	423	While nominally embeddable in other event loops, this feature is broken in
374	all kernel versions tested so far.	424	all kernel versions tested so far.
		425
		426	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		427	C<EVBACKEND_POLL>.
375		428
376	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	429	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
377		430
378	Kqueue deserves special mention, as at the time of this writing, it	431	Kqueue deserves special mention, as at the time of this writing, it
379	was broken on all BSDs except NetBSD (usually it doesn't work reliably	432	was broken on all BSDs except NetBSD (usually it doesn't work reliably
380	with anything but sockets and pipes, except on Darwin, where of course	433	with anything but sockets and pipes, except on Darwin, where of course
381	it's completely useless). For this reason it's not being "autodetected"	434	it's completely useless). Unlike epoll, however, whose brokenness
		435	is by design, these kqueue bugs can (and eventually will) be fixed
		436	without API changes to existing programs. For this reason it's not being
382	unless you explicitly specify it explicitly in the flags (i.e. using	437	"auto-detected" unless you explicitly specify it in the flags (i.e. using
383	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)	438	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
384	system like NetBSD.	439	system like NetBSD.
385		440
386	You still can embed kqueue into a normal poll or select backend and use it	441	You still can embed kqueue into a normal poll or select backend and use it
387	only for sockets (after having made sure that sockets work with kqueue on	442	only for sockets (after having made sure that sockets work with kqueue on
388	the target platform). See C<ev_embed> watchers for more info.	443	the target platform). See C<ev_embed> watchers for more info.
389		444
390	It scales in the same way as the epoll backend, but the interface to the	445	It scales in the same way as the epoll backend, but the interface to the
391	kernel is more efficient (which says nothing about its actual speed, of	446	kernel is more efficient (which says nothing about its actual speed, of
392	course). While stopping, setting and starting an I/O watcher does never	447	course). While stopping, setting and starting an I/O watcher does never
393	cause an extra syscall as with C<EVBACKEND_EPOLL>, it still adds up to	448	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to
394	two event changes per incident, support for C<fork ()> is very bad and it	449	two event changes per incident. Support for C<fork ()> is very bad (but
395	drops fds silently in similarly hard-to-detect cases.	450	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect
		451	cases
396		452
397	This backend usually performs well under most conditions.	453	This backend usually performs well under most conditions.
398		454
399	While nominally embeddable in other event loops, this doesn't work	455	While nominally embeddable in other event loops, this doesn't work
400	everywhere, so you might need to test for this. And since it is broken	456	everywhere, so you might need to test for this. And since it is broken
401	almost everywhere, you should only use it when you have a lot of sockets	457	almost everywhere, you should only use it when you have a lot of sockets
402	(for which it usually works), by embedding it into another event loop	458	(for which it usually works), by embedding it into another event loop
403	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and using it only for	459	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and, did I mention it,
404	sockets.	460	using it only for sockets.
		461
		462	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with
		463	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with
		464	C<NOTE_EOF>.
405		465
406	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)	466	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
407		467
408	This is not implemented yet (and might never be, unless you send me an	468	This is not implemented yet (and might never be, unless you send me an
409	implementation). According to reports, C</dev/poll> only supports sockets	469	implementation). According to reports, C</dev/poll> only supports sockets
…		…
413	=item C<EVBACKEND_PORT> (value 32, Solaris 10)	473	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
414		474
415	This uses the Solaris 10 event port mechanism. As with everything on Solaris,	475	This uses the Solaris 10 event port mechanism. As with everything on Solaris,
416	it's really slow, but it still scales very well (O(active_fds)).	476	it's really slow, but it still scales very well (O(active_fds)).
417		477
418	Please note that solaris event ports can deliver a lot of spurious	478	Please note that Solaris event ports can deliver a lot of spurious
419	notifications, so you need to use non-blocking I/O or other means to avoid	479	notifications, so you need to use non-blocking I/O or other means to avoid
420	blocking when no data (or space) is available.	480	blocking when no data (or space) is available.
421		481
422	While this backend scales well, it requires one system call per active	482	While this backend scales well, it requires one system call per active
423	file descriptor per loop iteration. For small and medium numbers of file	483	file descriptor per loop iteration. For small and medium numbers of file
424	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	484	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
425	might perform better.	485	might perform better.
426		486
427	On the positive side, ignoring the spurious readyness notifications, this	487	On the positive side, with the exception of the spurious readiness
428	backend actually performed to specification in all tests and is fully	488	notifications, this backend actually performed fully to specification
429	embeddable, which is a rare feat among the OS-specific backends.	489	in all tests and is fully embeddable, which is a rare feat among the
		490	OS-specific backends (I vastly prefer correctness over speed hacks).
		491
		492	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		493	C<EVBACKEND_POLL>.
430		494
431	=item C<EVBACKEND_ALL>	495	=item C<EVBACKEND_ALL>
432		496
433	Try all backends (even potentially broken ones that wouldn't be tried	497	Try all backends (even potentially broken ones that wouldn't be tried
434	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as	498	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
…		…
436		500
437	It is definitely not recommended to use this flag.	501	It is definitely not recommended to use this flag.
438		502
439	=back	503	=back
440		504
441	If one or more of these are ored into the flags value, then only these	505	If one or more of these are or'ed into the flags value, then only these
442	backends will be tried (in the reverse order as listed here). If none are	506	backends will be tried (in the reverse order as listed here). If none are
443	specified, all backends in C<ev_recommended_backends ()> will be tried.	507	specified, all backends in C<ev_recommended_backends ()> will be tried.
444		508
445	The most typical usage is like this:	509	Example: This is the most typical usage.
446		510
447	if (!ev_default_loop (0))	511	if (!ev_default_loop (0))
448	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");	512	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
449		513
450	Restrict libev to the select and poll backends, and do not allow	514	Example: Restrict libev to the select and poll backends, and do not allow
451	environment settings to be taken into account:	515	environment settings to be taken into account:
452		516
453	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);	517	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
454		518
455	Use whatever libev has to offer, but make sure that kqueue is used if	519	Example: Use whatever libev has to offer, but make sure that kqueue is
456	available (warning, breaks stuff, best use only with your own private	520	used if available (warning, breaks stuff, best use only with your own
457	event loop and only if you know the OS supports your types of fds):	521	private event loop and only if you know the OS supports your types of
		522	fds):
458		523
459	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);	524	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
460		525
461	=item struct ev_loop *ev_loop_new (unsigned int flags)	526	=item struct ev_loop *ev_loop_new (unsigned int flags)
462		527
463	Similar to C<ev_default_loop>, but always creates a new event loop that is	528	Similar to C<ev_default_loop>, but always creates a new event loop that is
464	always distinct from the default loop. Unlike the default loop, it cannot	529	always distinct from the default loop. Unlike the default loop, it cannot
…		…
469	libev with threads is indeed to create one loop per thread, and using the	534	libev with threads is indeed to create one loop per thread, and using the
470	default loop in the "main" or "initial" thread.	535	default loop in the "main" or "initial" thread.
471		536
472	Example: Try to create a event loop that uses epoll and nothing else.	537	Example: Try to create a event loop that uses epoll and nothing else.
473		538
474	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	539	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
475	if (!epoller)	540	if (!epoller)
476	fatal ("no epoll found here, maybe it hides under your chair");	541	fatal ("no epoll found here, maybe it hides under your chair");
477		542
478	=item ev_default_destroy ()	543	=item ev_default_destroy ()
479		544
480	Destroys the default loop again (frees all memory and kernel state	545	Destroys the default loop again (frees all memory and kernel state
481	etc.). None of the active event watchers will be stopped in the normal	546	etc.). None of the active event watchers will be stopped in the normal
482	sense, so e.g. C<ev_is_active> might still return true. It is your	547	sense, so e.g. C<ev_is_active> might still return true. It is your
483	responsibility to either stop all watchers cleanly yoursef I<before>	548	responsibility to either stop all watchers cleanly yourself I<before>
484	calling this function, or cope with the fact afterwards (which is usually	549	calling this function, or cope with the fact afterwards (which is usually
485	the easiest thing, you can just ignore the watchers and/or C<free ()> them	550	the easiest thing, you can just ignore the watchers and/or C<free ()> them
486	for example).	551	for example).
487		552
488	Note that certain global state, such as signal state, will not be freed by	553	Note that certain global state, such as signal state (and installed signal
489	this function, and related watchers (such as signal and child watchers)	554	handlers), will not be freed by this function, and related watchers (such
490	would need to be stopped manually.	555	as signal and child watchers) would need to be stopped manually.
491		556
492	In general it is not advisable to call this function except in the	557	In general it is not advisable to call this function except in the
493	rare occasion where you really need to free e.g. the signal handling	558	rare occasion where you really need to free e.g. the signal handling
494	pipe fds. If you need dynamically allocated loops it is better to use	559	pipe fds. If you need dynamically allocated loops it is better to use
495	C<ev_loop_new> and C<ev_loop_destroy>).	560	C<ev_loop_new> and C<ev_loop_destroy>).
…		…
520		585
521	=item ev_loop_fork (loop)	586	=item ev_loop_fork (loop)
522		587
523	Like C<ev_default_fork>, but acts on an event loop created by	588	Like C<ev_default_fork>, but acts on an event loop created by
524	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	589	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
525	after fork, and how you do this is entirely your own problem.	590	after fork that you want to re-use in the child, and how you do this is
		591	entirely your own problem.
526		592
527	=item int ev_is_default_loop (loop)	593	=item int ev_is_default_loop (loop)
528		594
529	Returns true when the given loop actually is the default loop, false otherwise.	595	Returns true when the given loop is, in fact, the default loop, and false
		596	otherwise.
530		597
531	=item unsigned int ev_loop_count (loop)	598	=item unsigned int ev_loop_count (loop)
532		599
533	Returns the count of loop iterations for the loop, which is identical to	600	Returns the count of loop iterations for the loop, which is identical to
534	the number of times libev did poll for new events. It starts at C<0> and	601	the number of times libev did poll for new events. It starts at C<0> and
…		…
549	received events and started processing them. This timestamp does not	616	received events and started processing them. This timestamp does not
550	change as long as callbacks are being processed, and this is also the base	617	change as long as callbacks are being processed, and this is also the base
551	time used for relative timers. You can treat it as the timestamp of the	618	time used for relative timers. You can treat it as the timestamp of the
552	event occurring (or more correctly, libev finding out about it).	619	event occurring (or more correctly, libev finding out about it).
553		620
		621	=item ev_now_update (loop)
		622
		623	Establishes the current time by querying the kernel, updating the time
		624	returned by C<ev_now ()> in the progress. This is a costly operation and
		625	is usually done automatically within C<ev_loop ()>.
		626
		627	This function is rarely useful, but when some event callback runs for a
		628	very long time without entering the event loop, updating libev's idea of
		629	the current time is a good idea.
		630
		631	See also "The special problem of time updates" in the C<ev_timer> section.
		632
554	=item ev_loop (loop, int flags)	633	=item ev_loop (loop, int flags)
555		634
556	Finally, this is it, the event handler. This function usually is called	635	Finally, this is it, the event handler. This function usually is called
557	after you initialised all your watchers and you want to start handling	636	after you initialised all your watchers and you want to start handling
558	events.	637	events.
…		…
560	If the flags argument is specified as C<0>, it will not return until	639	If the flags argument is specified as C<0>, it will not return until
561	either no event watchers are active anymore or C<ev_unloop> was called.	640	either no event watchers are active anymore or C<ev_unloop> was called.
562		641
563	Please note that an explicit C<ev_unloop> is usually better than	642	Please note that an explicit C<ev_unloop> is usually better than
564	relying on all watchers to be stopped when deciding when a program has	643	relying on all watchers to be stopped when deciding when a program has
565	finished (especially in interactive programs), but having a program that	644	finished (especially in interactive programs), but having a program
566	automatically loops as long as it has to and no longer by virtue of	645	that automatically loops as long as it has to and no longer by virtue
567	relying on its watchers stopping correctly is a thing of beauty.	646	of relying on its watchers stopping correctly, that is truly a thing of
		647	beauty.
568		648
569	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	649	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle
570	those events and any outstanding ones, but will not block your process in	650	those events and any already outstanding ones, but will not block your
571	case there are no events and will return after one iteration of the loop.	651	process in case there are no events and will return after one iteration of
		652	the loop.
572		653
573	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	654	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
574	neccessary) and will handle those and any outstanding ones. It will block	655	necessary) and will handle those and any already outstanding ones. It
575	your process until at least one new event arrives, and will return after	656	will block your process until at least one new event arrives (which could
576	one iteration of the loop. This is useful if you are waiting for some	657	be an event internal to libev itself, so there is no guarantee that a
577	external event in conjunction with something not expressible using other	658	user-registered callback will be called), and will return after one
		659	iteration of the loop.
		660
		661	This is useful if you are waiting for some external event in conjunction
		662	with something not expressible using other libev watchers (i.e. "roll your
578	libev watchers. However, a pair of C<ev_prepare>/C<ev_check> watchers is	663	own C<ev_loop>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
579	usually a better approach for this kind of thing.	664	usually a better approach for this kind of thing.
580		665
581	Here are the gory details of what C<ev_loop> does:	666	Here are the gory details of what C<ev_loop> does:
582		667
583	- Before the first iteration, call any pending watchers.	668	- Before the first iteration, call any pending watchers.
584	* If EVFLAG_FORKCHECK was used, check for a fork.	669	* If EVFLAG_FORKCHECK was used, check for a fork.
585	- If a fork was detected, queue and call all fork watchers.	670	- If a fork was detected (by any means), queue and call all fork watchers.
586	- Queue and call all prepare watchers.	671	- Queue and call all prepare watchers.
587	- If we have been forked, recreate the kernel state.	672	- If we have been forked, detach and recreate the kernel state
		673	as to not disturb the other process.
588	- Update the kernel state with all outstanding changes.	674	- Update the kernel state with all outstanding changes.
589	- Update the "event loop time".	675	- Update the "event loop time" (ev_now ()).
590	- Calculate for how long to sleep or block, if at all	676	- Calculate for how long to sleep or block, if at all
591	(active idle watchers, EVLOOP_NONBLOCK or not having	677	(active idle watchers, EVLOOP_NONBLOCK or not having
592	any active watchers at all will result in not sleeping).	678	any active watchers at all will result in not sleeping).
593	- Sleep if the I/O and timer collect interval say so.	679	- Sleep if the I/O and timer collect interval say so.
594	- Block the process, waiting for any events.	680	- Block the process, waiting for any events.
595	- Queue all outstanding I/O (fd) events.	681	- Queue all outstanding I/O (fd) events.
596	- Update the "event loop time" and do time jump handling.	682	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
597	- Queue all outstanding timers.	683	- Queue all expired timers.
598	- Queue all outstanding periodics.	684	- Queue all expired periodics.
599	- If no events are pending now, queue all idle watchers.	685	- Unless any events are pending now, queue all idle watchers.
600	- Queue all check watchers.	686	- Queue all check watchers.
601	- Call all queued watchers in reverse order (i.e. check watchers first).	687	- Call all queued watchers in reverse order (i.e. check watchers first).
602	Signals and child watchers are implemented as I/O watchers, and will	688	Signals and child watchers are implemented as I/O watchers, and will
603	be handled here by queueing them when their watcher gets executed.	689	be handled here by queueing them when their watcher gets executed.
604	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	690	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
…		…
609	anymore.	695	anymore.
610		696
611	... queue jobs here, make sure they register event watchers as long	697	... queue jobs here, make sure they register event watchers as long
612	... as they still have work to do (even an idle watcher will do..)	698	... as they still have work to do (even an idle watcher will do..)
613	ev_loop (my_loop, 0);	699	ev_loop (my_loop, 0);
614	... jobs done. yeah!	700	... jobs done or somebody called unloop. yeah!
615		701
616	=item ev_unloop (loop, how)	702	=item ev_unloop (loop, how)
617		703
618	Can be used to make a call to C<ev_loop> return early (but only after it	704	Can be used to make a call to C<ev_loop> return early (but only after it
619	has processed all outstanding events). The C<how> argument must be either	705	has processed all outstanding events). The C<how> argument must be either
620	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	706	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or
621	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	707	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.
622		708
623	This "unloop state" will be cleared when entering C<ev_loop> again.	709	This "unloop state" will be cleared when entering C<ev_loop> again.
624		710
		711	It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls.
		712
625	=item ev_ref (loop)	713	=item ev_ref (loop)
626		714
627	=item ev_unref (loop)	715	=item ev_unref (loop)
628		716
629	Ref/unref can be used to add or remove a reference count on the event	717	Ref/unref can be used to add or remove a reference count on the event
630	loop: Every watcher keeps one reference, and as long as the reference	718	loop: Every watcher keeps one reference, and as long as the reference
631	count is nonzero, C<ev_loop> will not return on its own. If you have	719	count is nonzero, C<ev_loop> will not return on its own.
		720
632	a watcher you never unregister that should not keep C<ev_loop> from	721	If you have a watcher you never unregister that should not keep C<ev_loop>
633	returning, ev_unref() after starting, and ev_ref() before stopping it. For	722	from returning, call ev_unref() after starting, and ev_ref() before
		723	stopping it.
		724
634	example, libev itself uses this for its internal signal pipe: It is not	725	As an example, libev itself uses this for its internal signal pipe: It is
635	visible to the libev user and should not keep C<ev_loop> from exiting if	726	not visible to the libev user and should not keep C<ev_loop> from exiting
636	no event watchers registered by it are active. It is also an excellent	727	if no event watchers registered by it are active. It is also an excellent
637	way to do this for generic recurring timers or from within third-party	728	way to do this for generic recurring timers or from within third-party
638	libraries. Just remember to I<unref after start> and I<ref before stop>	729	libraries. Just remember to I<unref after start> and I<ref before stop>
639	(but only if the watcher wasn't active before, or was active before,	730	(but only if the watcher wasn't active before, or was active before,
640	respectively).	731	respectively).
641		732
642	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	733	Example: Create a signal watcher, but keep it from keeping C<ev_loop>
643	running when nothing else is active.	734	running when nothing else is active.
644		735
645	struct ev_signal exitsig;	736	ev_signal exitsig;
646	ev_signal_init (&exitsig, sig_cb, SIGINT);	737	ev_signal_init (&exitsig, sig_cb, SIGINT);
647	ev_signal_start (loop, &exitsig);	738	ev_signal_start (loop, &exitsig);
648	evf_unref (loop);	739	evf_unref (loop);
649		740
650	Example: For some weird reason, unregister the above signal handler again.	741	Example: For some weird reason, unregister the above signal handler again.
651		742
652	ev_ref (loop);	743	ev_ref (loop);
653	ev_signal_stop (loop, &exitsig);	744	ev_signal_stop (loop, &exitsig);
654		745
655	=item ev_set_io_collect_interval (loop, ev_tstamp interval)	746	=item ev_set_io_collect_interval (loop, ev_tstamp interval)
656		747
657	=item ev_set_timeout_collect_interval (loop, ev_tstamp interval)	748	=item ev_set_timeout_collect_interval (loop, ev_tstamp interval)
658		749
659	These advanced functions influence the time that libev will spend waiting	750	These advanced functions influence the time that libev will spend waiting
660	for events. Both are by default C<0>, meaning that libev will try to	751	for events. Both time intervals are by default C<0>, meaning that libev
661	invoke timer/periodic callbacks and I/O callbacks with minimum latency.	752	will try to invoke timer/periodic callbacks and I/O callbacks with minimum
		753	latency.
662		754
663	Setting these to a higher value (the C<interval> I<must> be >= C<0>)	755	Setting these to a higher value (the C<interval> I<must> be >= C<0>)
664	allows libev to delay invocation of I/O and timer/periodic callbacks to	756	allows libev to delay invocation of I/O and timer/periodic callbacks
665	increase efficiency of loop iterations.	757	to increase efficiency of loop iterations (or to increase power-saving
		758	opportunities).
666		759
667	The background is that sometimes your program runs just fast enough to	760	The idea is that sometimes your program runs just fast enough to handle
668	handle one (or very few) event(s) per loop iteration. While this makes	761	one (or very few) event(s) per loop iteration. While this makes the
669	the program responsive, it also wastes a lot of CPU time to poll for new	762	program responsive, it also wastes a lot of CPU time to poll for new
670	events, especially with backends like C<select ()> which have a high	763	events, especially with backends like C<select ()> which have a high
671	overhead for the actual polling but can deliver many events at once.	764	overhead for the actual polling but can deliver many events at once.
672		765
673	By setting a higher I<io collect interval> you allow libev to spend more	766	By setting a higher I<io collect interval> you allow libev to spend more
674	time collecting I/O events, so you can handle more events per iteration,	767	time collecting I/O events, so you can handle more events per iteration,
…		…
676	C<ev_timer>) will be not affected. Setting this to a non-null value will	769	C<ev_timer>) will be not affected. Setting this to a non-null value will
677	introduce an additional C<ev_sleep ()> call into most loop iterations.	770	introduce an additional C<ev_sleep ()> call into most loop iterations.
678		771
679	Likewise, by setting a higher I<timeout collect interval> you allow libev	772	Likewise, by setting a higher I<timeout collect interval> you allow libev
680	to spend more time collecting timeouts, at the expense of increased	773	to spend more time collecting timeouts, at the expense of increased
681	latency (the watcher callback will be called later). C<ev_io> watchers	774	latency/jitter/inexactness (the watcher callback will be called
682	will not be affected. Setting this to a non-null value will not introduce	775	later). C<ev_io> watchers will not be affected. Setting this to a non-null
683	any overhead in libev.	776	value will not introduce any overhead in libev.
684		777
685	Many (busy) programs can usually benefit by setting the io collect	778	Many (busy) programs can usually benefit by setting the I/O collect
686	interval to a value near C<0.1> or so, which is often enough for	779	interval to a value near C<0.1> or so, which is often enough for
687	interactive servers (of course not for games), likewise for timeouts. It	780	interactive servers (of course not for games), likewise for timeouts. It
688	usually doesn't make much sense to set it to a lower value than C<0.01>,	781	usually doesn't make much sense to set it to a lower value than C<0.01>,
689	as this approsaches the timing granularity of most systems.	782	as this approaches the timing granularity of most systems.
		783
		784	Setting the I<timeout collect interval> can improve the opportunity for
		785	saving power, as the program will "bundle" timer callback invocations that
		786	are "near" in time together, by delaying some, thus reducing the number of
		787	times the process sleeps and wakes up again. Another useful technique to
		788	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure
		789	they fire on, say, one-second boundaries only.
		790
		791	=item ev_loop_verify (loop)
		792
		793	This function only does something when C<EV_VERIFY> support has been
		794	compiled in, which is the default for non-minimal builds. It tries to go
		795	through all internal structures and checks them for validity. If anything
		796	is found to be inconsistent, it will print an error message to standard
		797	error and call C<abort ()>.
		798
		799	This can be used to catch bugs inside libev itself: under normal
		800	circumstances, this function will never abort as of course libev keeps its
		801	data structures consistent.
690		802
691	=back	803	=back
692		804
693		805
694	=head1 ANATOMY OF A WATCHER	806	=head1 ANATOMY OF A WATCHER
		807
		808	In the following description, uppercase C<TYPE> in names stands for the
		809	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
		810	watchers and C<ev_io_start> for I/O watchers.
695		811
696	A watcher is a structure that you create and register to record your	812	A watcher is a structure that you create and register to record your
697	interest in some event. For instance, if you want to wait for STDIN to	813	interest in some event. For instance, if you want to wait for STDIN to
698	become readable, you would create an C<ev_io> watcher for that:	814	become readable, you would create an C<ev_io> watcher for that:
699		815
700	static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)	816	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
701	{	817	{
702	ev_io_stop (w);	818	ev_io_stop (w);
703	ev_unloop (loop, EVUNLOOP_ALL);	819	ev_unloop (loop, EVUNLOOP_ALL);
704	}	820	}
705		821
706	struct ev_loop *loop = ev_default_loop (0);	822	struct ev_loop *loop = ev_default_loop (0);
		823
707	struct ev_io stdin_watcher;	824	ev_io stdin_watcher;
		825
708	ev_init (&stdin_watcher, my_cb);	826	ev_init (&stdin_watcher, my_cb);
709	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	827	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
710	ev_io_start (loop, &stdin_watcher);	828	ev_io_start (loop, &stdin_watcher);
		829
711	ev_loop (loop, 0);	830	ev_loop (loop, 0);
712		831
713	As you can see, you are responsible for allocating the memory for your	832	As you can see, you are responsible for allocating the memory for your
714	watcher structures (and it is usually a bad idea to do this on the stack,	833	watcher structures (and it is I<usually> a bad idea to do this on the
715	although this can sometimes be quite valid).	834	stack).
		835
		836	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
		837	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
716		838
717	Each watcher structure must be initialised by a call to C<ev_init	839	Each watcher structure must be initialised by a call to C<ev_init
718	(watcher *, callback)>, which expects a callback to be provided. This	840	(watcher *, callback)>, which expects a callback to be provided. This
719	callback gets invoked each time the event occurs (or, in the case of io	841	callback gets invoked each time the event occurs (or, in the case of I/O
720	watchers, each time the event loop detects that the file descriptor given	842	watchers, each time the event loop detects that the file descriptor given
721	is readable and/or writable).	843	is readable and/or writable).
722		844
723	Each watcher type has its own C<< ev_<type>_set (watcher *, ...) >> macro	845	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
724	with arguments specific to this watcher type. There is also a macro	846	macro to configure it, with arguments specific to the watcher type. There
725	to combine initialisation and setting in one call: C<< ev_<type>_init	847	is also a macro to combine initialisation and setting in one call: C<<
726	(watcher *, callback, ...) >>.	848	ev_TYPE_init (watcher *, callback, ...) >>.
727		849
728	To make the watcher actually watch out for events, you have to start it	850	To make the watcher actually watch out for events, you have to start it
729	with a watcher-specific start function (C<< ev_<type>_start (loop, watcher	851	with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher
730	*) >>), and you can stop watching for events at any time by calling the	852	*) >>), and you can stop watching for events at any time by calling the
731	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	853	corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>.
732		854
733	As long as your watcher is active (has been started but not stopped) you	855	As long as your watcher is active (has been started but not stopped) you
734	must not touch the values stored in it. Most specifically you must never	856	must not touch the values stored in it. Most specifically you must never
735	reinitialise it or call its C<set> macro.	857	reinitialise it or call its C<ev_TYPE_set> macro.
736		858
737	Each and every callback receives the event loop pointer as first, the	859	Each and every callback receives the event loop pointer as first, the
738	registered watcher structure as second, and a bitset of received events as	860	registered watcher structure as second, and a bitset of received events as
739	third argument.	861	third argument.
740		862
…		…
800		922
801	The given async watcher has been asynchronously notified (see C<ev_async>).	923	The given async watcher has been asynchronously notified (see C<ev_async>).
802		924
803	=item C<EV_ERROR>	925	=item C<EV_ERROR>
804		926
805	An unspecified error has occured, the watcher has been stopped. This might	927	An unspecified error has occurred, the watcher has been stopped. This might
806	happen because the watcher could not be properly started because libev	928	happen because the watcher could not be properly started because libev
807	ran out of memory, a file descriptor was found to be closed or any other	929	ran out of memory, a file descriptor was found to be closed or any other
		930	problem. Libev considers these application bugs.
		931
808	problem. You best act on it by reporting the problem and somehow coping	932	You best act on it by reporting the problem and somehow coping with the
809	with the watcher being stopped.	933	watcher being stopped. Note that well-written programs should not receive
		934	an error ever, so when your watcher receives it, this usually indicates a
		935	bug in your program.
810		936
811	Libev will usually signal a few "dummy" events together with an error,	937	Libev will usually signal a few "dummy" events together with an error, for
812	for example it might indicate that a fd is readable or writable, and if	938	example it might indicate that a fd is readable or writable, and if your
813	your callbacks is well-written it can just attempt the operation and cope	939	callbacks is well-written it can just attempt the operation and cope with
814	with the error from read() or write(). This will not work in multithreaded	940	the error from read() or write(). This will not work in multi-threaded
815	programs, though, so beware.	941	programs, though, as the fd could already be closed and reused for another
		942	thing, so beware.
816		943
817	=back	944	=back
818		945
819	=head2 GENERIC WATCHER FUNCTIONS	946	=head2 GENERIC WATCHER FUNCTIONS
820
821	In the following description, C<TYPE> stands for the watcher type,
822	e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.
823		947
824	=over 4	948	=over 4
825		949
826	=item C<ev_init> (ev_TYPE *watcher, callback)	950	=item C<ev_init> (ev_TYPE *watcher, callback)
827		951
…		…
833	which rolls both calls into one.	957	which rolls both calls into one.
834		958
835	You can reinitialise a watcher at any time as long as it has been stopped	959	You can reinitialise a watcher at any time as long as it has been stopped
836	(or never started) and there are no pending events outstanding.	960	(or never started) and there are no pending events outstanding.
837		961
838	The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,	962	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
839	int revents)>.	963	int revents)>.
		964
		965	Example: Initialise an C<ev_io> watcher in two steps.
		966
		967	ev_io w;
		968	ev_init (&w, my_cb);
		969	ev_io_set (&w, STDIN_FILENO, EV_READ);
840		970
841	=item C<ev_TYPE_set> (ev_TYPE *, [args])	971	=item C<ev_TYPE_set> (ev_TYPE *, [args])
842		972
843	This macro initialises the type-specific parts of a watcher. You need to	973	This macro initialises the type-specific parts of a watcher. You need to
844	call C<ev_init> at least once before you call this macro, but you can	974	call C<ev_init> at least once before you call this macro, but you can
…		…
847	difference to the C<ev_init> macro).	977	difference to the C<ev_init> macro).
848		978
849	Although some watcher types do not have type-specific arguments	979	Although some watcher types do not have type-specific arguments
850	(e.g. C<ev_prepare>) you still need to call its C<set> macro.	980	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
851		981
		982	See C<ev_init>, above, for an example.
		983
852	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])	984	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
853		985
854	This convinience macro rolls both C<ev_init> and C<ev_TYPE_set> macro	986	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro
855	calls into a single call. This is the most convinient method to initialise	987	calls into a single call. This is the most convenient method to initialise
856	a watcher. The same limitations apply, of course.	988	a watcher. The same limitations apply, of course.
		989
		990	Example: Initialise and set an C<ev_io> watcher in one step.
		991
		992	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
857		993
858	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)	994	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)
859		995
860	Starts (activates) the given watcher. Only active watchers will receive	996	Starts (activates) the given watcher. Only active watchers will receive
861	events. If the watcher is already active nothing will happen.	997	events. If the watcher is already active nothing will happen.
862		998
		999	Example: Start the C<ev_io> watcher that is being abused as example in this
		1000	whole section.
		1001
		1002	ev_io_start (EV_DEFAULT_UC, &w);
		1003
863	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)	1004	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)
864		1005
865	Stops the given watcher again (if active) and clears the pending	1006	Stops the given watcher if active, and clears the pending status (whether
		1007	the watcher was active or not).
		1008
866	status. It is possible that stopped watchers are pending (for example,	1009	It is possible that stopped watchers are pending - for example,
867	non-repeating timers are being stopped when they become pending), but	1010	non-repeating timers are being stopped when they become pending - but
868	C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If	1011	calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
869	you want to free or reuse the memory used by the watcher it is therefore a	1012	pending. If you want to free or reuse the memory used by the watcher it is
870	good idea to always call its C<ev_TYPE_stop> function.	1013	therefore a good idea to always call its C<ev_TYPE_stop> function.
871		1014
872	=item bool ev_is_active (ev_TYPE *watcher)	1015	=item bool ev_is_active (ev_TYPE *watcher)
873		1016
874	Returns a true value iff the watcher is active (i.e. it has been started	1017	Returns a true value iff the watcher is active (i.e. it has been started
875	and not yet been stopped). As long as a watcher is active you must not modify	1018	and not yet been stopped). As long as a watcher is active you must not modify
…		…
917	The default priority used by watchers when no priority has been set is	1060	The default priority used by watchers when no priority has been set is
918	always C<0>, which is supposed to not be too high and not be too low :).	1061	always C<0>, which is supposed to not be too high and not be too low :).
919		1062
920	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1063	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
921	fine, as long as you do not mind that the priority value you query might	1064	fine, as long as you do not mind that the priority value you query might
922	or might not have been adjusted to be within valid range.	1065	or might not have been clamped to the valid range.
923		1066
924	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1067	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
925		1068
926	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1069	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
927	C<loop> nor C<revents> need to be valid as long as the watcher callback	1070	C<loop> nor C<revents> need to be valid as long as the watcher callback
928	can deal with that fact.	1071	can deal with that fact, as both are simply passed through to the
		1072	callback.
929		1073
930	=item int ev_clear_pending (loop, ev_TYPE *watcher)	1074	=item int ev_clear_pending (loop, ev_TYPE *watcher)
931		1075
932	If the watcher is pending, this function returns clears its pending status	1076	If the watcher is pending, this function clears its pending status and
933	and returns its C<revents> bitset (as if its callback was invoked). If the	1077	returns its C<revents> bitset (as if its callback was invoked). If the
934	watcher isn't pending it does nothing and returns C<0>.	1078	watcher isn't pending it does nothing and returns C<0>.
935		1079
		1080	Sometimes it can be useful to "poll" a watcher instead of waiting for its
		1081	callback to be invoked, which can be accomplished with this function.
		1082
936	=back	1083	=back
937		1084
938		1085
939	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1086	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
940		1087
941	Each watcher has, by default, a member C<void *data> that you can change	1088	Each watcher has, by default, a member C<void *data> that you can change
942	and read at any time, libev will completely ignore it. This can be used	1089	and read at any time: libev will completely ignore it. This can be used
943	to associate arbitrary data with your watcher. If you need more data and	1090	to associate arbitrary data with your watcher. If you need more data and
944	don't want to allocate memory and store a pointer to it in that data	1091	don't want to allocate memory and store a pointer to it in that data
945	member, you can also "subclass" the watcher type and provide your own	1092	member, you can also "subclass" the watcher type and provide your own
946	data:	1093	data:
947		1094
948	struct my_io	1095	struct my_io
949	{	1096	{
950	struct ev_io io;	1097	ev_io io;
951	int otherfd;	1098	int otherfd;
952	void *somedata;	1099	void *somedata;
953	struct whatever *mostinteresting;	1100	struct whatever *mostinteresting;
954	}	1101	};
		1102
		1103	...
		1104	struct my_io w;
		1105	ev_io_init (&w.io, my_cb, fd, EV_READ);
955		1106
956	And since your callback will be called with a pointer to the watcher, you	1107	And since your callback will be called with a pointer to the watcher, you
957	can cast it back to your own type:	1108	can cast it back to your own type:
958		1109
959	static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents)	1110	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
960	{	1111	{
961	struct my_io *w = (struct my_io *)w_;	1112	struct my_io *w = (struct my_io *)w_;
962	...	1113	...
963	}	1114	}
964		1115
965	More interesting and less C-conformant ways of casting your callback type	1116	More interesting and less C-conformant ways of casting your callback type
966	instead have been omitted.	1117	instead have been omitted.
967		1118
968	Another common scenario is having some data structure with multiple	1119	Another common scenario is to use some data structure with multiple
969	watchers:	1120	embedded watchers:
970		1121
971	struct my_biggy	1122	struct my_biggy
972	{	1123	{
973	int some_data;	1124	int some_data;
974	ev_timer t1;	1125	ev_timer t1;
975	ev_timer t2;	1126	ev_timer t2;
976	}	1127	}
977		1128
978	In this case getting the pointer to C<my_biggy> is a bit more complicated,	1129	In this case getting the pointer to C<my_biggy> is a bit more
979	you need to use C<offsetof>:	1130	complicated: Either you store the address of your C<my_biggy> struct
		1131	in the C<data> member of the watcher (for woozies), or you need to use
		1132	some pointer arithmetic using C<offsetof> inside your watchers (for real
		1133	programmers):
980		1134
981	#include <stddef.h>	1135	#include <stddef.h>
982		1136
983	static void	1137	static void
984	t1_cb (EV_P_ struct ev_timer *w, int revents)	1138	t1_cb (EV_P_ ev_timer *w, int revents)
985	{	1139	{
986	struct my_biggy big = (struct my_biggy *	1140	struct my_biggy big = (struct my_biggy *
987	(((char *)w) - offsetof (struct my_biggy, t1));	1141	(((char *)w) - offsetof (struct my_biggy, t1));
988	}	1142	}
989		1143
990	static void	1144	static void
991	t2_cb (EV_P_ struct ev_timer *w, int revents)	1145	t2_cb (EV_P_ ev_timer *w, int revents)
992	{	1146	{
993	struct my_biggy big = (struct my_biggy *	1147	struct my_biggy big = (struct my_biggy *
994	(((char *)w) - offsetof (struct my_biggy, t2));	1148	(((char *)w) - offsetof (struct my_biggy, t2));
995	}	1149	}
996		1150
997		1151
998	=head1 WATCHER TYPES	1152	=head1 WATCHER TYPES
999		1153
1000	This section describes each watcher in detail, but will not repeat	1154	This section describes each watcher in detail, but will not repeat
…		…
1024	In general you can register as many read and/or write event watchers per	1178	In general you can register as many read and/or write event watchers per
1025	fd as you want (as long as you don't confuse yourself). Setting all file	1179	fd as you want (as long as you don't confuse yourself). Setting all file
1026	descriptors to non-blocking mode is also usually a good idea (but not	1180	descriptors to non-blocking mode is also usually a good idea (but not
1027	required if you know what you are doing).	1181	required if you know what you are doing).
1028		1182
1029	If you must do this, then force the use of a known-to-be-good backend	1183	If you cannot use non-blocking mode, then force the use of a
1030	(at the time of this writing, this includes only C<EVBACKEND_SELECT> and	1184	known-to-be-good backend (at the time of this writing, this includes only
1031	C<EVBACKEND_POLL>).	1185	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>).
1032		1186
1033	Another thing you have to watch out for is that it is quite easy to	1187	Another thing you have to watch out for is that it is quite easy to
1034	receive "spurious" readyness notifications, that is your callback might	1188	receive "spurious" readiness notifications, that is your callback might
1035	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1189	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1036	because there is no data. Not only are some backends known to create a	1190	because there is no data. Not only are some backends known to create a
1037	lot of those (for example solaris ports), it is very easy to get into	1191	lot of those (for example Solaris ports), it is very easy to get into
1038	this situation even with a relatively standard program structure. Thus	1192	this situation even with a relatively standard program structure. Thus
1039	it is best to always use non-blocking I/O: An extra C<read>(2) returning	1193	it is best to always use non-blocking I/O: An extra C<read>(2) returning
1040	C<EAGAIN> is far preferable to a program hanging until some data arrives.	1194	C<EAGAIN> is far preferable to a program hanging until some data arrives.
1041		1195
1042	If you cannot run the fd in non-blocking mode (for example you should not	1196	If you cannot run the fd in non-blocking mode (for example you should
1043	play around with an Xlib connection), then you have to seperately re-test	1197	not play around with an Xlib connection), then you have to separately
1044	whether a file descriptor is really ready with a known-to-be good interface	1198	re-test whether a file descriptor is really ready with a known-to-be good
1045	such as poll (fortunately in our Xlib example, Xlib already does this on	1199	interface such as poll (fortunately in our Xlib example, Xlib already
1046	its own, so its quite safe to use).	1200	does this on its own, so its quite safe to use). Some people additionally
		1201	use C<SIGALRM> and an interval timer, just to be sure you won't block
		1202	indefinitely.
		1203
		1204	But really, best use non-blocking mode.
1047		1205
1048	=head3 The special problem of disappearing file descriptors	1206	=head3 The special problem of disappearing file descriptors
1049		1207
1050	Some backends (e.g. kqueue, epoll) need to be told about closing a file	1208	Some backends (e.g. kqueue, epoll) need to be told about closing a file
1051	descriptor (either by calling C<close> explicitly or by any other means,	1209	descriptor (either due to calling C<close> explicitly or any other means,
1052	such as C<dup>). The reason is that you register interest in some file	1210	such as C<dup2>). The reason is that you register interest in some file
1053	descriptor, but when it goes away, the operating system will silently drop	1211	descriptor, but when it goes away, the operating system will silently drop
1054	this interest. If another file descriptor with the same number then is	1212	this interest. If another file descriptor with the same number then is
1055	registered with libev, there is no efficient way to see that this is, in	1213	registered with libev, there is no efficient way to see that this is, in
1056	fact, a different file descriptor.	1214	fact, a different file descriptor.
1057		1215
…		…
1088	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1246	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or
1089	C<EVBACKEND_POLL>.	1247	C<EVBACKEND_POLL>.
1090		1248
1091	=head3 The special problem of SIGPIPE	1249	=head3 The special problem of SIGPIPE
1092		1250
1093	While not really specific to libev, it is easy to forget about SIGPIPE:	1251	While not really specific to libev, it is easy to forget about C<SIGPIPE>:
1094	when reading from a pipe whose other end has been closed, your program	1252	when writing to a pipe whose other end has been closed, your program gets
1095	gets send a SIGPIPE, which, by default, aborts your program. For most	1253	sent a SIGPIPE, which, by default, aborts your program. For most programs
1096	programs this is sensible behaviour, for daemons, this is usually	1254	this is sensible behaviour, for daemons, this is usually undesirable.
1097	undesirable.
1098		1255
1099	So when you encounter spurious, unexplained daemon exits, make sure you	1256	So when you encounter spurious, unexplained daemon exits, make sure you
1100	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon	1257	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1101	somewhere, as that would have given you a big clue).	1258	somewhere, as that would have given you a big clue).
1102		1259
…		…
1108	=item ev_io_init (ev_io *, callback, int fd, int events)	1265	=item ev_io_init (ev_io *, callback, int fd, int events)
1109		1266
1110	=item ev_io_set (ev_io *, int fd, int events)	1267	=item ev_io_set (ev_io *, int fd, int events)
1111		1268
1112	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to	1269	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to
1113	rceeive events for and events is either C<EV_READ>, C<EV_WRITE> or	1270	receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or
1114	C<EV_READ | EV_WRITE> to receive the given events.	1271	C<EV_READ | EV_WRITE>, to express the desire to receive the given events.
1115		1272
1116	=item int fd [read-only]	1273	=item int fd [read-only]
1117		1274
1118	The file descriptor being watched.	1275	The file descriptor being watched.
1119		1276
…		…
1127		1284
1128	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well	1285	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well
1129	readable, but only once. Since it is likely line-buffered, you could	1286	readable, but only once. Since it is likely line-buffered, you could
1130	attempt to read a whole line in the callback.	1287	attempt to read a whole line in the callback.
1131		1288
1132	static void	1289	static void
1133	stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1290	stdin_readable_cb (struct ev_loop *loop, ev_io *w, int revents)
1134	{	1291	{
1135	ev_io_stop (loop, w);	1292	ev_io_stop (loop, w);
1136	.. read from stdin here (or from w->fd) and haqndle any I/O errors	1293	.. read from stdin here (or from w->fd) and handle any I/O errors
1137	}	1294	}
1138		1295
1139	...	1296	...
1140	struct ev_loop *loop = ev_default_init (0);	1297	struct ev_loop *loop = ev_default_init (0);
1141	struct ev_io stdin_readable;	1298	ev_io stdin_readable;
1142	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1299	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1143	ev_io_start (loop, &stdin_readable);	1300	ev_io_start (loop, &stdin_readable);
1144	ev_loop (loop, 0);	1301	ev_loop (loop, 0);
1145		1302
1146		1303
1147	=head2 C<ev_timer> - relative and optionally repeating timeouts	1304	=head2 C<ev_timer> - relative and optionally repeating timeouts
1148		1305
1149	Timer watchers are simple relative timers that generate an event after a	1306	Timer watchers are simple relative timers that generate an event after a
1150	given time, and optionally repeating in regular intervals after that.	1307	given time, and optionally repeating in regular intervals after that.
1151		1308
1152	The timers are based on real time, that is, if you register an event that	1309	The timers are based on real time, that is, if you register an event that
1153	times out after an hour and you reset your system clock to last years	1310	times out after an hour and you reset your system clock to January last
1154	time, it will still time out after (roughly) and hour. "Roughly" because	1311	year, it will still time out after (roughly) one hour. "Roughly" because
1155	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1312	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1156	monotonic clock option helps a lot here).	1313	monotonic clock option helps a lot here).
		1314
		1315	The callback is guaranteed to be invoked only I<after> its timeout has
		1316	passed, but if multiple timers become ready during the same loop iteration
		1317	then order of execution is undefined.
		1318
		1319	=head3 Be smart about timeouts
		1320
		1321	Many real-world problems involve some kind of timeout, usually for error
		1322	recovery. A typical example is an HTTP request - if the other side hangs,
		1323	you want to raise some error after a while.
		1324
		1325	What follows are some ways to handle this problem, from obvious and
		1326	inefficient to smart and efficient.
		1327
		1328	In the following, a 60 second activity timeout is assumed - a timeout that
		1329	gets reset to 60 seconds each time there is activity (e.g. each time some
		1330	data or other life sign was received).
		1331
		1332	=over 4
		1333
		1334	=item 1. Use a timer and stop, reinitialise and start it on activity.
		1335
		1336	This is the most obvious, but not the most simple way: In the beginning,
		1337	start the watcher:
		1338
		1339	ev_timer_init (timer, callback, 60., 0.);
		1340	ev_timer_start (loop, timer);
		1341
		1342	Then, each time there is some activity, C<ev_timer_stop> it, initialise it
		1343	and start it again:
		1344
		1345	ev_timer_stop (loop, timer);
		1346	ev_timer_set (timer, 60., 0.);
		1347	ev_timer_start (loop, timer);
		1348
		1349	This is relatively simple to implement, but means that each time there is
		1350	some activity, libev will first have to remove the timer from its internal
		1351	data structure and then add it again. Libev tries to be fast, but it's
		1352	still not a constant-time operation.
		1353
		1354	=item 2. Use a timer and re-start it with C<ev_timer_again> inactivity.
		1355
		1356	This is the easiest way, and involves using C<ev_timer_again> instead of
		1357	C<ev_timer_start>.
		1358
		1359	To implement this, configure an C<ev_timer> with a C<repeat> value
		1360	of C<60> and then call C<ev_timer_again> at start and each time you
		1361	successfully read or write some data. If you go into an idle state where
		1362	you do not expect data to travel on the socket, you can C<ev_timer_stop>
		1363	the timer, and C<ev_timer_again> will automatically restart it if need be.
		1364
		1365	That means you can ignore both the C<ev_timer_start> function and the
		1366	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
		1367	member and C<ev_timer_again>.
		1368
		1369	At start:
		1370
		1371	ev_timer_init (timer, callback);
		1372	timer->repeat = 60.;
		1373	ev_timer_again (loop, timer);
		1374
		1375	Each time there is some activity:
		1376
		1377	ev_timer_again (loop, timer);
		1378
		1379	It is even possible to change the time-out on the fly, regardless of
		1380	whether the watcher is active or not:
		1381
		1382	timer->repeat = 30.;
		1383	ev_timer_again (loop, timer);
		1384
		1385	This is slightly more efficient then stopping/starting the timer each time
		1386	you want to modify its timeout value, as libev does not have to completely
		1387	remove and re-insert the timer from/into its internal data structure.
		1388
		1389	It is, however, even simpler than the "obvious" way to do it.
		1390
		1391	=item 3. Let the timer time out, but then re-arm it as required.
		1392
		1393	This method is more tricky, but usually most efficient: Most timeouts are
		1394	relatively long compared to the intervals between other activity - in
		1395	our example, within 60 seconds, there are usually many I/O events with
		1396	associated activity resets.
		1397
		1398	In this case, it would be more efficient to leave the C<ev_timer> alone,
		1399	but remember the time of last activity, and check for a real timeout only
		1400	within the callback:
		1401
		1402	ev_tstamp last_activity; // time of last activity
		1403
		1404	static void
		1405	callback (EV_P_ ev_timer *w, int revents)
		1406	{
		1407	ev_tstamp now = ev_now (EV_A);
		1408	ev_tstamp timeout = last_activity + 60.;
		1409
		1410	// if last_activity + 60. is older than now, we did time out
		1411	if (timeout < now)
		1412	{
		1413	// timeout occured, take action
		1414	}
		1415	else
		1416	{
		1417	// callback was invoked, but there was some activity, re-arm
		1418	// the watcher to fire in last_activity + 60, which is
		1419	// guaranteed to be in the future, so "again" is positive:
		1420	w->again = timeout - now;
		1421	ev_timer_again (EV_A_ w);
		1422	}
		1423	}
		1424
		1425	To summarise the callback: first calculate the real timeout (defined
		1426	as "60 seconds after the last activity"), then check if that time has
		1427	been reached, which means something I<did>, in fact, time out. Otherwise
		1428	the callback was invoked too early (C<timeout> is in the future), so
		1429	re-schedule the timer to fire at that future time, to see if maybe we have
		1430	a timeout then.
		1431
		1432	Note how C<ev_timer_again> is used, taking advantage of the
		1433	C<ev_timer_again> optimisation when the timer is already running.
		1434
		1435	This scheme causes more callback invocations (about one every 60 seconds
		1436	minus half the average time between activity), but virtually no calls to
		1437	libev to change the timeout.
		1438
		1439	To start the timer, simply initialise the watcher and set C<last_activity>
		1440	to the current time (meaning we just have some activity :), then call the
		1441	callback, which will "do the right thing" and start the timer:
		1442
		1443	ev_timer_init (timer, callback);
		1444	last_activity = ev_now (loop);
		1445	callback (loop, timer, EV_TIMEOUT);
		1446
		1447	And when there is some activity, simply store the current time in
		1448	C<last_activity>, no libev calls at all:
		1449
		1450	last_actiivty = ev_now (loop);
		1451
		1452	This technique is slightly more complex, but in most cases where the
		1453	time-out is unlikely to be triggered, much more efficient.
		1454
		1455	Changing the timeout is trivial as well (if it isn't hard-coded in the
		1456	callback :) - just change the timeout and invoke the callback, which will
		1457	fix things for you.
		1458
		1459	=item 4. Wee, just use a double-linked list for your timeouts.
		1460
		1461	If there is not one request, but many thousands (millions...), all
		1462	employing some kind of timeout with the same timeout value, then one can
		1463	do even better:
		1464
		1465	When starting the timeout, calculate the timeout value and put the timeout
		1466	at the I<end> of the list.
		1467
		1468	Then use an C<ev_timer> to fire when the timeout at the I<beginning> of
		1469	the list is expected to fire (for example, using the technique #3).
		1470
		1471	When there is some activity, remove the timer from the list, recalculate
		1472	the timeout, append it to the end of the list again, and make sure to
		1473	update the C<ev_timer> if it was taken from the beginning of the list.
		1474
		1475	This way, one can manage an unlimited number of timeouts in O(1) time for
		1476	starting, stopping and updating the timers, at the expense of a major
		1477	complication, and having to use a constant timeout. The constant timeout
		1478	ensures that the list stays sorted.
		1479
		1480	=back
		1481
		1482	So which method the best?
		1483
		1484	Method #2 is a simple no-brain-required solution that is adequate in most
		1485	situations. Method #3 requires a bit more thinking, but handles many cases
		1486	better, and isn't very complicated either. In most case, choosing either
		1487	one is fine, with #3 being better in typical situations.
		1488
		1489	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is
		1490	rather complicated, but extremely efficient, something that really pays
		1491	off after the first million or so of active timers, i.e. it's usually
		1492	overkill :)
		1493
		1494	=head3 The special problem of time updates
		1495
		1496	Establishing the current time is a costly operation (it usually takes at
		1497	least two system calls): EV therefore updates its idea of the current
		1498	time only before and after C<ev_loop> collects new events, which causes a
		1499	growing difference between C<ev_now ()> and C<ev_time ()> when handling
		1500	lots of events in one iteration.
1157		1501
1158	The relative timeouts are calculated relative to the C<ev_now ()>	1502	The relative timeouts are calculated relative to the C<ev_now ()>
1159	time. This is usually the right thing as this timestamp refers to the time	1503	time. This is usually the right thing as this timestamp refers to the time
1160	of the event triggering whatever timeout you are modifying/starting. If	1504	of the event triggering whatever timeout you are modifying/starting. If
1161	you suspect event processing to be delayed and you I<need> to base the timeout	1505	you suspect event processing to be delayed and you I<need> to base the
1162	on the current time, use something like this to adjust for this:	1506	timeout on the current time, use something like this to adjust for this:
1163		1507
1164	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	1508	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
1165		1509
1166	The callback is guarenteed to be invoked only when its timeout has passed,	1510	If the event loop is suspended for a long time, you can also force an
1167	but if multiple timers become ready during the same loop iteration then	1511	update of the time returned by C<ev_now ()> by calling C<ev_now_update
1168	order of execution is undefined.	1512	()>.
1169		1513
1170	=head3 Watcher-Specific Functions and Data Members	1514	=head3 Watcher-Specific Functions and Data Members
1171		1515
1172	=over 4	1516	=over 4
1173		1517
1174	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	1518	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
1175		1519
1176	=item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)	1520	=item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)
1177		1521
1178	Configure the timer to trigger after C<after> seconds. If C<repeat> is	1522	Configure the timer to trigger after C<after> seconds. If C<repeat>
1179	C<0.>, then it will automatically be stopped. If it is positive, then the	1523	is C<0.>, then it will automatically be stopped once the timeout is
1180	timer will automatically be configured to trigger again C<repeat> seconds	1524	reached. If it is positive, then the timer will automatically be
1181	later, again, and again, until stopped manually.	1525	configured to trigger again C<repeat> seconds later, again, and again,
		1526	until stopped manually.
1182		1527
1183	The timer itself will do a best-effort at avoiding drift, that is, if you	1528	The timer itself will do a best-effort at avoiding drift, that is, if
1184	configure a timer to trigger every 10 seconds, then it will trigger at	1529	you configure a timer to trigger every 10 seconds, then it will normally
1185	exactly 10 second intervals. If, however, your program cannot keep up with	1530	trigger at exactly 10 second intervals. If, however, your program cannot
1186	the timer (because it takes longer than those 10 seconds to do stuff) the	1531	keep up with the timer (because it takes longer than those 10 seconds to
1187	timer will not fire more than once per event loop iteration.	1532	do stuff) the timer will not fire more than once per event loop iteration.
1188		1533
1189	=item ev_timer_again (loop, ev_timer *)	1534	=item ev_timer_again (loop, ev_timer *)
1190		1535
1191	This will act as if the timer timed out and restart it again if it is	1536	This will act as if the timer timed out and restart it again if it is
1192	repeating. The exact semantics are:	1537	repeating. The exact semantics are:
1193		1538
1194	If the timer is pending, its pending status is cleared.	1539	If the timer is pending, its pending status is cleared.
1195		1540
1196	If the timer is started but nonrepeating, stop it (as if it timed out).	1541	If the timer is started but non-repeating, stop it (as if it timed out).
1197		1542
1198	If the timer is repeating, either start it if necessary (with the	1543	If the timer is repeating, either start it if necessary (with the
1199	C<repeat> value), or reset the running timer to the C<repeat> value.	1544	C<repeat> value), or reset the running timer to the C<repeat> value.
1200		1545
1201	This sounds a bit complicated, but here is a useful and typical	1546	This sounds a bit complicated, see "Be smart about timeouts", above, for a
1202	example: Imagine you have a tcp connection and you want a so-called idle	1547	usage example.
1203	timeout, that is, you want to be called when there have been, say, 60
1204	seconds of inactivity on the socket. The easiest way to do this is to
1205	configure an C<ev_timer> with a C<repeat> value of C<60> and then call
1206	C<ev_timer_again> each time you successfully read or write some data. If
1207	you go into an idle state where you do not expect data to travel on the
1208	socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
1209	automatically restart it if need be.
1210
1211	That means you can ignore the C<after> value and C<ev_timer_start>
1212	altogether and only ever use the C<repeat> value and C<ev_timer_again>:
1213
1214	ev_timer_init (timer, callback, 0., 5.);
1215	ev_timer_again (loop, timer);
1216	...
1217	timer->again = 17.;
1218	ev_timer_again (loop, timer);
1219	...
1220	timer->again = 10.;
1221	ev_timer_again (loop, timer);
1222
1223	This is more slightly efficient then stopping/starting the timer each time
1224	you want to modify its timeout value.
1225		1548
1226	=item ev_tstamp repeat [read-write]	1549	=item ev_tstamp repeat [read-write]
1227		1550
1228	The current C<repeat> value. Will be used each time the watcher times out	1551	The current C<repeat> value. Will be used each time the watcher times out
1229	or C<ev_timer_again> is called and determines the next timeout (if any),	1552	or C<ev_timer_again> is called, and determines the next timeout (if any),
1230	which is also when any modifications are taken into account.	1553	which is also when any modifications are taken into account.
1231		1554
1232	=back	1555	=back
1233		1556
1234	=head3 Examples	1557	=head3 Examples
1235		1558
1236	Example: Create a timer that fires after 60 seconds.	1559	Example: Create a timer that fires after 60 seconds.
1237		1560
1238	static void	1561	static void
1239	one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1562	one_minute_cb (struct ev_loop *loop, ev_timer *w, int revents)
1240	{	1563	{
1241	.. one minute over, w is actually stopped right here	1564	.. one minute over, w is actually stopped right here
1242	}	1565	}
1243		1566
1244	struct ev_timer mytimer;	1567	ev_timer mytimer;
1245	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);	1568	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1246	ev_timer_start (loop, &mytimer);	1569	ev_timer_start (loop, &mytimer);
1247		1570
1248	Example: Create a timeout timer that times out after 10 seconds of	1571	Example: Create a timeout timer that times out after 10 seconds of
1249	inactivity.	1572	inactivity.
1250		1573
1251	static void	1574	static void
1252	timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1575	timeout_cb (struct ev_loop *loop, ev_timer *w, int revents)
1253	{	1576	{
1254	.. ten seconds without any activity	1577	.. ten seconds without any activity
1255	}	1578	}
1256		1579
1257	struct ev_timer mytimer;	1580	ev_timer mytimer;
1258	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	1581	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1259	ev_timer_again (&mytimer); /* start timer */	1582	ev_timer_again (&mytimer); /* start timer */
1260	ev_loop (loop, 0);	1583	ev_loop (loop, 0);
1261		1584
1262	// and in some piece of code that gets executed on any "activity":	1585	// and in some piece of code that gets executed on any "activity":
1263	// reset the timeout to start ticking again at 10 seconds	1586	// reset the timeout to start ticking again at 10 seconds
1264	ev_timer_again (&mytimer);	1587	ev_timer_again (&mytimer);
1265		1588
1266		1589
1267	=head2 C<ev_periodic> - to cron or not to cron?	1590	=head2 C<ev_periodic> - to cron or not to cron?
1268		1591
1269	Periodic watchers are also timers of a kind, but they are very versatile	1592	Periodic watchers are also timers of a kind, but they are very versatile
1270	(and unfortunately a bit complex).	1593	(and unfortunately a bit complex).
1271		1594
1272	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	1595	Unlike C<ev_timer>'s, they are not based on real time (or relative time)
1273	but on wallclock time (absolute time). You can tell a periodic watcher	1596	but on wall clock time (absolute time). You can tell a periodic watcher
1274	to trigger "at" some specific point in time. For example, if you tell a	1597	to trigger after some specific point in time. For example, if you tell a
1275	periodic watcher to trigger in 10 seconds (by specifiying e.g. C<ev_now ()	1598	periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now ()
1276	+ 10.>) and then reset your system clock to the last year, then it will	1599	+ 10.>, that is, an absolute time not a delay) and then reset your system
		1600	clock to January of the previous year, then it will take more than year
1277	take a year to trigger the event (unlike an C<ev_timer>, which would trigger	1601	to trigger the event (unlike an C<ev_timer>, which would still trigger
1278	roughly 10 seconds later).	1602	roughly 10 seconds later as it uses a relative timeout).
1279		1603
1280	They can also be used to implement vastly more complex timers, such as	1604	C<ev_periodic>s can also be used to implement vastly more complex timers,
1281	triggering an event on each midnight, local time or other, complicated,	1605	such as triggering an event on each "midnight, local time", or other
1282	rules.	1606	complicated rules.
1283		1607
1284	As with timers, the callback is guarenteed to be invoked only when the	1608	As with timers, the callback is guaranteed to be invoked only when the
1285	time (C<at>) has been passed, but if multiple periodic timers become ready	1609	time (C<at>) has passed, but if multiple periodic timers become ready
1286	during the same loop iteration then order of execution is undefined.	1610	during the same loop iteration, then order of execution is undefined.
1287		1611
1288	=head3 Watcher-Specific Functions and Data Members	1612	=head3 Watcher-Specific Functions and Data Members
1289		1613
1290	=over 4	1614	=over 4
1291		1615
1292	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	1616	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)
1293		1617
1294	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	1618	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)
1295		1619
1296	Lots of arguments, lets sort it out... There are basically three modes of	1620	Lots of arguments, lets sort it out... There are basically three modes of
1297	operation, and we will explain them from simplest to complex:	1621	operation, and we will explain them from simplest to most complex:
1298		1622
1299	=over 4	1623	=over 4
1300		1624
1301	=item * absolute timer (at = time, interval = reschedule_cb = 0)	1625	=item * absolute timer (at = time, interval = reschedule_cb = 0)
1302		1626
1303	In this configuration the watcher triggers an event at the wallclock time	1627	In this configuration the watcher triggers an event after the wall clock
1304	C<at> and doesn't repeat. It will not adjust when a time jump occurs,	1628	time C<at> has passed. It will not repeat and will not adjust when a time
1305	that is, if it is to be run at January 1st 2011 then it will run when the	1629	jump occurs, that is, if it is to be run at January 1st 2011 then it will
1306	system time reaches or surpasses this time.	1630	only run when the system clock reaches or surpasses this time.
1307		1631
1308	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)	1632	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)
1309		1633
1310	In this mode the watcher will always be scheduled to time out at the next	1634	In this mode the watcher will always be scheduled to time out at the next
1311	C<at + N * interval> time (for some integer N, which can also be negative)	1635	C<at + N * interval> time (for some integer N, which can also be negative)
1312	and then repeat, regardless of any time jumps.	1636	and then repeat, regardless of any time jumps.
1313		1637
1314	This can be used to create timers that do not drift with respect to system	1638	This can be used to create timers that do not drift with respect to the
1315	time:	1639	system clock, for example, here is a C<ev_periodic> that triggers each
		1640	hour, on the hour:
1316		1641
1317	ev_periodic_set (&periodic, 0., 3600., 0);	1642	ev_periodic_set (&periodic, 0., 3600., 0);
1318		1643
1319	This doesn't mean there will always be 3600 seconds in between triggers,	1644	This doesn't mean there will always be 3600 seconds in between triggers,
1320	but only that the the callback will be called when the system time shows a	1645	but only that the callback will be called when the system time shows a
1321	full hour (UTC), or more correctly, when the system time is evenly divisible	1646	full hour (UTC), or more correctly, when the system time is evenly divisible
1322	by 3600.	1647	by 3600.
1323		1648
1324	Another way to think about it (for the mathematically inclined) is that	1649	Another way to think about it (for the mathematically inclined) is that
1325	C<ev_periodic> will try to run the callback in this mode at the next possible	1650	C<ev_periodic> will try to run the callback in this mode at the next possible
1326	time where C<time = at (mod interval)>, regardless of any time jumps.	1651	time where C<time = at (mod interval)>, regardless of any time jumps.
1327		1652
1328	For numerical stability it is preferable that the C<at> value is near	1653	For numerical stability it is preferable that the C<at> value is near
1329	C<ev_now ()> (the current time), but there is no range requirement for	1654	C<ev_now ()> (the current time), but there is no range requirement for
1330	this value.	1655	this value, and in fact is often specified as zero.
		1656
		1657	Note also that there is an upper limit to how often a timer can fire (CPU
		1658	speed for example), so if C<interval> is very small then timing stability
		1659	will of course deteriorate. Libev itself tries to be exact to be about one
		1660	millisecond (if the OS supports it and the machine is fast enough).
1331		1661
1332	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)	1662	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)
1333		1663
1334	In this mode the values for C<interval> and C<at> are both being	1664	In this mode the values for C<interval> and C<at> are both being
1335	ignored. Instead, each time the periodic watcher gets scheduled, the	1665	ignored. Instead, each time the periodic watcher gets scheduled, the
1336	reschedule callback will be called with the watcher as first, and the	1666	reschedule callback will be called with the watcher as first, and the
1337	current time as second argument.	1667	current time as second argument.
1338		1668
1339	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,	1669	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,
1340	ever, or make any event loop modifications>. If you need to stop it,	1670	ever, or make ANY event loop modifications whatsoever>.
1341	return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by
1342	starting an C<ev_prepare> watcher, which is legal).
1343		1671
		1672	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop
		1673	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
		1674	only event loop modification you are allowed to do).
		1675
1344	Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w,	1676	The callback prototype is C<ev_tstamp (*reschedule_cb)(ev_periodic
1345	ev_tstamp now)>, e.g.:	1677	*w, ev_tstamp now)>, e.g.:
1346		1678
		1679	static ev_tstamp
1347	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	1680	my_rescheduler (ev_periodic *w, ev_tstamp now)
1348	{	1681	{
1349	return now + 60.;	1682	return now + 60.;
1350	}	1683	}
1351		1684
1352	It must return the next time to trigger, based on the passed time value	1685	It must return the next time to trigger, based on the passed time value
1353	(that is, the lowest time value larger than to the second argument). It	1686	(that is, the lowest time value larger than to the second argument). It
1354	will usually be called just before the callback will be triggered, but	1687	will usually be called just before the callback will be triggered, but
1355	might be called at other times, too.	1688	might be called at other times, too.
1356		1689
1357	NOTE: I<< This callback must always return a time that is later than the	1690	NOTE: I<< This callback must always return a time that is higher than or
1358	passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger.	1691	equal to the passed C<now> value >>.
1359		1692
1360	This can be used to create very complex timers, such as a timer that	1693	This can be used to create very complex timers, such as a timer that
1361	triggers on each midnight, local time. To do this, you would calculate the	1694	triggers on "next midnight, local time". To do this, you would calculate the
1362	next midnight after C<now> and return the timestamp value for this. How	1695	next midnight after C<now> and return the timestamp value for this. How
1363	you do this is, again, up to you (but it is not trivial, which is the main	1696	you do this is, again, up to you (but it is not trivial, which is the main
1364	reason I omitted it as an example).	1697	reason I omitted it as an example).
1365		1698
1366	=back	1699	=back
…		…
1370	Simply stops and restarts the periodic watcher again. This is only useful	1703	Simply stops and restarts the periodic watcher again. This is only useful
1371	when you changed some parameters or the reschedule callback would return	1704	when you changed some parameters or the reschedule callback would return
1372	a different time than the last time it was called (e.g. in a crond like	1705	a different time than the last time it was called (e.g. in a crond like
1373	program when the crontabs have changed).	1706	program when the crontabs have changed).
1374		1707
		1708	=item ev_tstamp ev_periodic_at (ev_periodic *)
		1709
		1710	When active, returns the absolute time that the watcher is supposed to
		1711	trigger next.
		1712
1375	=item ev_tstamp offset [read-write]	1713	=item ev_tstamp offset [read-write]
1376		1714
1377	When repeating, this contains the offset value, otherwise this is the	1715	When repeating, this contains the offset value, otherwise this is the
1378	absolute point in time (the C<at> value passed to C<ev_periodic_set>).	1716	absolute point in time (the C<at> value passed to C<ev_periodic_set>).
1379		1717
…		…
1384		1722
1385	The current interval value. Can be modified any time, but changes only	1723	The current interval value. Can be modified any time, but changes only
1386	take effect when the periodic timer fires or C<ev_periodic_again> is being	1724	take effect when the periodic timer fires or C<ev_periodic_again> is being
1387	called.	1725	called.
1388		1726
1389	=item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]	1727	=item ev_tstamp (*reschedule_cb)(ev_periodic *w, ev_tstamp now) [read-write]
1390		1728
1391	The current reschedule callback, or C<0>, if this functionality is	1729	The current reschedule callback, or C<0>, if this functionality is
1392	switched off. Can be changed any time, but changes only take effect when	1730	switched off. Can be changed any time, but changes only take effect when
1393	the periodic timer fires or C<ev_periodic_again> is being called.	1731	the periodic timer fires or C<ev_periodic_again> is being called.
1394		1732
1395	=item ev_tstamp at [read-only]
1396
1397	When active, contains the absolute time that the watcher is supposed to
1398	trigger next.
1399
1400	=back	1733	=back
1401		1734
1402	=head3 Examples	1735	=head3 Examples
1403		1736
1404	Example: Call a callback every hour, or, more precisely, whenever the	1737	Example: Call a callback every hour, or, more precisely, whenever the
1405	system clock is divisible by 3600. The callback invocation times have	1738	system time is divisible by 3600. The callback invocation times have
1406	potentially a lot of jittering, but good long-term stability.	1739	potentially a lot of jitter, but good long-term stability.
1407		1740
1408	static void	1741	static void
1409	clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1742	clock_cb (struct ev_loop *loop, ev_io *w, int revents)
1410	{	1743	{
1411	... its now a full hour (UTC, or TAI or whatever your clock follows)	1744	... its now a full hour (UTC, or TAI or whatever your clock follows)
1412	}	1745	}
1413		1746
1414	struct ev_periodic hourly_tick;	1747	ev_periodic hourly_tick;
1415	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);	1748	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1416	ev_periodic_start (loop, &hourly_tick);	1749	ev_periodic_start (loop, &hourly_tick);
1417		1750
1418	Example: The same as above, but use a reschedule callback to do it:	1751	Example: The same as above, but use a reschedule callback to do it:
1419		1752
1420	#include <math.h>	1753	#include <math.h>
1421		1754
1422	static ev_tstamp	1755	static ev_tstamp
1423	my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)	1756	my_scheduler_cb (ev_periodic *w, ev_tstamp now)
1424	{	1757	{
1425	return fmod (now, 3600.) + 3600.;	1758	return now + (3600. - fmod (now, 3600.));
1426	}	1759	}
1427		1760
1428	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);	1761	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1429		1762
1430	Example: Call a callback every hour, starting now:	1763	Example: Call a callback every hour, starting now:
1431		1764
1432	struct ev_periodic hourly_tick;	1765	ev_periodic hourly_tick;
1433	ev_periodic_init (&hourly_tick, clock_cb,	1766	ev_periodic_init (&hourly_tick, clock_cb,
1434	fmod (ev_now (loop), 3600.), 3600., 0);	1767	fmod (ev_now (loop), 3600.), 3600., 0);
1435	ev_periodic_start (loop, &hourly_tick);	1768	ev_periodic_start (loop, &hourly_tick);
1436		1769
1437		1770
1438	=head2 C<ev_signal> - signal me when a signal gets signalled!	1771	=head2 C<ev_signal> - signal me when a signal gets signalled!
1439		1772
1440	Signal watchers will trigger an event when the process receives a specific	1773	Signal watchers will trigger an event when the process receives a specific
1441	signal one or more times. Even though signals are very asynchronous, libev	1774	signal one or more times. Even though signals are very asynchronous, libev
1442	will try it's best to deliver signals synchronously, i.e. as part of the	1775	will try it's best to deliver signals synchronously, i.e. as part of the
1443	normal event processing, like any other event.	1776	normal event processing, like any other event.
1444		1777
		1778	If you want signals asynchronously, just use C<sigaction> as you would
		1779	do without libev and forget about sharing the signal. You can even use
		1780	C<ev_async> from a signal handler to synchronously wake up an event loop.
		1781
1445	You can configure as many watchers as you like per signal. Only when the	1782	You can configure as many watchers as you like per signal. Only when the
1446	first watcher gets started will libev actually register a signal watcher	1783	first watcher gets started will libev actually register a signal handler
1447	with the kernel (thus it coexists with your own signal handlers as long	1784	with the kernel (thus it coexists with your own signal handlers as long as
1448	as you don't register any with libev). Similarly, when the last signal	1785	you don't register any with libev for the same signal). Similarly, when
1449	watcher for a signal is stopped libev will reset the signal handler to	1786	the last signal watcher for a signal is stopped, libev will reset the
1450	SIG_DFL (regardless of what it was set to before).	1787	signal handler to SIG_DFL (regardless of what it was set to before).
1451		1788
1452	If possible and supported, libev will install its handlers with	1789	If possible and supported, libev will install its handlers with
1453	C<SA_RESTART> behaviour enabled, so syscalls should not be unduly	1790	C<SA_RESTART> behaviour enabled, so system calls should not be unduly
1454	interrupted. If you have a problem with syscalls getting interrupted by	1791	interrupted. If you have a problem with system calls getting interrupted by
1455	signals you can block all signals in an C<ev_check> watcher and unblock	1792	signals you can block all signals in an C<ev_check> watcher and unblock
1456	them in an C<ev_prepare> watcher.	1793	them in an C<ev_prepare> watcher.
1457		1794
1458	=head3 Watcher-Specific Functions and Data Members	1795	=head3 Watcher-Specific Functions and Data Members
1459		1796
…		…
1472		1809
1473	=back	1810	=back
1474		1811
1475	=head3 Examples	1812	=head3 Examples
1476		1813
1477	Example: Try to exit cleanly on SIGINT and SIGTERM.	1814	Example: Try to exit cleanly on SIGINT.
1478		1815
1479	static void	1816	static void
1480	sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)	1817	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
1481	{	1818	{
1482	ev_unloop (loop, EVUNLOOP_ALL);	1819	ev_unloop (loop, EVUNLOOP_ALL);
1483	}	1820	}
1484		1821
1485	struct ev_signal signal_watcher;	1822	ev_signal signal_watcher;
1486	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	1823	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1487	ev_signal_start (loop, &sigint_cb);	1824	ev_signal_start (loop, &signal_watcher);
1488		1825
1489		1826
1490	=head2 C<ev_child> - watch out for process status changes	1827	=head2 C<ev_child> - watch out for process status changes
1491		1828
1492	Child watchers trigger when your process receives a SIGCHLD in response to	1829	Child watchers trigger when your process receives a SIGCHLD in response to
1493	some child status changes (most typically when a child of yours dies). It	1830	some child status changes (most typically when a child of yours dies or
1494	is permissible to install a child watcher I<after> the child has been	1831	exits). It is permissible to install a child watcher I<after> the child
1495	forked (which implies it might have already exited), as long as the event	1832	has been forked (which implies it might have already exited), as long
1496	loop isn't entered (or is continued from a watcher).	1833	as the event loop isn't entered (or is continued from a watcher), i.e.,
		1834	forking and then immediately registering a watcher for the child is fine,
		1835	but forking and registering a watcher a few event loop iterations later is
		1836	not.
1497		1837
1498	Only the default event loop is capable of handling signals, and therefore	1838	Only the default event loop is capable of handling signals, and therefore
1499	you can only rgeister child watchers in the default event loop.	1839	you can only register child watchers in the default event loop.
1500		1840
1501	=head3 Process Interaction	1841	=head3 Process Interaction
1502		1842
1503	Libev grabs C<SIGCHLD> as soon as the default event loop is	1843	Libev grabs C<SIGCHLD> as soon as the default event loop is
1504	initialised. This is necessary to guarantee proper behaviour even if	1844	initialised. This is necessary to guarantee proper behaviour even if
1505	the first child watcher is started after the child exits. The occurance	1845	the first child watcher is started after the child exits. The occurrence
1506	of C<SIGCHLD> is recorded asynchronously, but child reaping is done	1846	of C<SIGCHLD> is recorded asynchronously, but child reaping is done
1507	synchronously as part of the event loop processing. Libev always reaps all	1847	synchronously as part of the event loop processing. Libev always reaps all
1508	children, even ones not watched.	1848	children, even ones not watched.
1509		1849
1510	=head3 Overriding the Built-In Processing	1850	=head3 Overriding the Built-In Processing
…		…
1514	handler, you can override it easily by installing your own handler for	1854	handler, you can override it easily by installing your own handler for
1515	C<SIGCHLD> after initialising the default loop, and making sure the	1855	C<SIGCHLD> after initialising the default loop, and making sure the
1516	default loop never gets destroyed. You are encouraged, however, to use an	1856	default loop never gets destroyed. You are encouraged, however, to use an
1517	event-based approach to child reaping and thus use libev's support for	1857	event-based approach to child reaping and thus use libev's support for
1518	that, so other libev users can use C<ev_child> watchers freely.	1858	that, so other libev users can use C<ev_child> watchers freely.
		1859
		1860	=head3 Stopping the Child Watcher
		1861
		1862	Currently, the child watcher never gets stopped, even when the
		1863	child terminates, so normally one needs to stop the watcher in the
		1864	callback. Future versions of libev might stop the watcher automatically
		1865	when a child exit is detected.
1519		1866
1520	=head3 Watcher-Specific Functions and Data Members	1867	=head3 Watcher-Specific Functions and Data Members
1521		1868
1522	=over 4	1869	=over 4
1523		1870
…		…
1552	=head3 Examples	1899	=head3 Examples
1553		1900
1554	Example: C<fork()> a new process and install a child handler to wait for	1901	Example: C<fork()> a new process and install a child handler to wait for
1555	its completion.	1902	its completion.
1556		1903
1557	ev_child cw;	1904	ev_child cw;
1558		1905
1559	static void	1906	static void
1560	child_cb (EV_P_ struct ev_child *w, int revents)	1907	child_cb (EV_P_ ev_child *w, int revents)
1561	{	1908	{
1562	ev_child_stop (EV_A_ w);	1909	ev_child_stop (EV_A_ w);
1563	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);	1910	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);
1564	}	1911	}
1565		1912
1566	pid_t pid = fork ();	1913	pid_t pid = fork ();
1567		1914
1568	if (pid < 0)	1915	if (pid < 0)
1569	// error	1916	// error
1570	else if (pid == 0)	1917	else if (pid == 0)
1571	{	1918	{
1572	// the forked child executes here	1919	// the forked child executes here
1573	exit (1);	1920	exit (1);
1574	}	1921	}
1575	else	1922	else
1576	{	1923	{
1577	ev_child_init (&cw, child_cb, pid, 0);	1924	ev_child_init (&cw, child_cb, pid, 0);
1578	ev_child_start (EV_DEFAULT_ &cw);	1925	ev_child_start (EV_DEFAULT_ &cw);
1579	}	1926	}
1580		1927
1581		1928
1582	=head2 C<ev_stat> - did the file attributes just change?	1929	=head2 C<ev_stat> - did the file attributes just change?
1583		1930
1584	This watches a filesystem path for attribute changes. That is, it calls	1931	This watches a file system path for attribute changes. That is, it calls
1585	C<stat> regularly (or when the OS says it changed) and sees if it changed	1932	C<stat> on that path in regular intervals (or when the OS says it changed)
1586	compared to the last time, invoking the callback if it did.	1933	and sees if it changed compared to the last time, invoking the callback if
		1934	it did.
1587		1935
1588	The path does not need to exist: changing from "path exists" to "path does	1936	The path does not need to exist: changing from "path exists" to "path does
1589	not exist" is a status change like any other. The condition "path does	1937	not exist" is a status change like any other. The condition "path does not
1590	not exist" is signified by the C<st_nlink> field being zero (which is	1938	exist" (or more correctly "path cannot be stat'ed") is signified by the
1591	otherwise always forced to be at least one) and all the other fields of	1939	C<st_nlink> field being zero (which is otherwise always forced to be at
1592	the stat buffer having unspecified contents.	1940	least one) and all the other fields of the stat buffer having unspecified
		1941	contents.
1593		1942
1594	The path I<should> be absolute and I<must not> end in a slash. If it is	1943	The path I<must not> end in a slash or contain special components such as
		1944	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1595	relative and your working directory changes, the behaviour is undefined.	1945	your working directory changes, then the behaviour is undefined.
1596		1946
1597	Since there is no standard to do this, the portable implementation simply	1947	Since there is no portable change notification interface available, the
1598	calls C<stat (2)> regularly on the path to see if it changed somehow. You	1948	portable implementation simply calls C<stat(2)> regularly on the path
1599	can specify a recommended polling interval for this case. If you specify	1949	to see if it changed somehow. You can specify a recommended polling
1600	a polling interval of C<0> (highly recommended!) then a I<suitable,	1950	interval for this case. If you specify a polling interval of C<0> (highly
1601	unspecified default> value will be used (which you can expect to be around	1951	recommended!) then a I<suitable, unspecified default> value will be used
1602	five seconds, although this might change dynamically). Libev will also	1952	(which you can expect to be around five seconds, although this might
1603	impose a minimum interval which is currently around C<0.1>, but thats	1953	change dynamically). Libev will also impose a minimum interval which is
1604	usually overkill.	1954	currently around C<0.1>, but that's usually overkill.
1605		1955
1606	This watcher type is not meant for massive numbers of stat watchers,	1956	This watcher type is not meant for massive numbers of stat watchers,
1607	as even with OS-supported change notifications, this can be	1957	as even with OS-supported change notifications, this can be
1608	resource-intensive.	1958	resource-intensive.
1609		1959
1610	At the time of this writing, only the Linux inotify interface is	1960	At the time of this writing, the only OS-specific interface implemented
1611	implemented (implementing kqueue support is left as an exercise for the	1961	is the Linux inotify interface (implementing kqueue support is left as an
1612	reader). Inotify will be used to give hints only and should not change the	1962	exercise for the reader. Note, however, that the author sees no way of
1613	semantics of C<ev_stat> watchers, which means that libev sometimes needs	1963	implementing C<ev_stat> semantics with kqueue, except as a hint).
1614	to fall back to regular polling again even with inotify, but changes are
1615	usually detected immediately, and if the file exists there will be no
1616	polling.
1617		1964
1618	=head3 ABI Issues (Largefile Support)	1965	=head3 ABI Issues (Largefile Support)
1619		1966
1620	Libev by default (unless the user overrides this) uses the default	1967	Libev by default (unless the user overrides this) uses the default
1621	compilation environment, which means that on systems with optionally	1968	compilation environment, which means that on systems with large file
1622	disabled large file support, you get the 32 bit version of the stat	1969	support disabled by default, you get the 32 bit version of the stat
1623	structure. When using the library from programs that change the ABI to	1970	structure. When using the library from programs that change the ABI to
1624	use 64 bit file offsets the programs will fail. In that case you have to	1971	use 64 bit file offsets the programs will fail. In that case you have to
1625	compile libev with the same flags to get binary compatibility. This is	1972	compile libev with the same flags to get binary compatibility. This is
1626	obviously the case with any flags that change the ABI, but the problem is	1973	obviously the case with any flags that change the ABI, but the problem is
1627	most noticably with ev_stat and largefile support.	1974	most noticeably displayed with ev_stat and large file support.
1628		1975
1629	=head3 Inotify	1976	The solution for this is to lobby your distribution maker to make large
		1977	file interfaces available by default (as e.g. FreeBSD does) and not
		1978	optional. Libev cannot simply switch on large file support because it has
		1979	to exchange stat structures with application programs compiled using the
		1980	default compilation environment.
1630		1981
		1982	=head3 Inotify and Kqueue
		1983
1631	When C<inotify (7)> support has been compiled into libev (generally only	1984	When C<inotify (7)> support has been compiled into libev and present at
1632	available on Linux) and present at runtime, it will be used to speed up	1985	runtime, it will be used to speed up change detection where possible. The
1633	change detection where possible. The inotify descriptor will be created lazily	1986	inotify descriptor will be created lazily when the first C<ev_stat>
1634	when the first C<ev_stat> watcher is being started.	1987	watcher is being started.
1635		1988
1636	Inotify presense does not change the semantics of C<ev_stat> watchers	1989	Inotify presence does not change the semantics of C<ev_stat> watchers
1637	except that changes might be detected earlier, and in some cases, to avoid	1990	except that changes might be detected earlier, and in some cases, to avoid
1638	making regular C<stat> calls. Even in the presense of inotify support	1991	making regular C<stat> calls. Even in the presence of inotify support
1639	there are many cases where libev has to resort to regular C<stat> polling.	1992	there are many cases where libev has to resort to regular C<stat> polling,
		1993	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		1994	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		1995	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		1996	xfs are fully working) libev usually gets away without polling.
1640		1997
1641	(There is no support for kqueue, as apparently it cannot be used to	1998	There is no support for kqueue, as apparently it cannot be used to
1642	implement this functionality, due to the requirement of having a file	1999	implement this functionality, due to the requirement of having a file
1643	descriptor open on the object at all times).	2000	descriptor open on the object at all times, and detecting renames, unlinks
		2001	etc. is difficult.
		2002
		2003	=head3 C<stat ()> is a synchronous operation
		2004
		2005	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2006	the process. The exception are C<ev_stat> watchers - those call C<stat
		2007	()>, which is a synchronous operation.
		2008
		2009	For local paths, this usually doesn't matter: unless the system is very
		2010	busy or the intervals between stat's are large, a stat call will be fast,
		2011	as the path data is suually in memory already (except when starting the
		2012	watcher).
		2013
		2014	For networked file systems, calling C<stat ()> can block an indefinite
		2015	time due to network issues, and even under good conditions, a stat call
		2016	often takes multiple milliseconds.
		2017
		2018	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2019	paths, although this is fully supported by libev.
1644		2020
1645	=head3 The special problem of stat time resolution	2021	=head3 The special problem of stat time resolution
1646		2022
1647	The C<stat ()> syscall only supports full-second resolution portably, and	2023	The C<stat ()> system call only supports full-second resolution portably,
1648	even on systems where the resolution is higher, many filesystems still	2024	and even on systems where the resolution is higher, most file systems
1649	only support whole seconds.	2025	still only support whole seconds.
1650		2026
1651	That means that, if the time is the only thing that changes, you might	2027	That means that, if the time is the only thing that changes, you can
1652	miss updates: on the first update, C<ev_stat> detects a change and calls	2028	easily miss updates: on the first update, C<ev_stat> detects a change and
1653	your callback, which does something. When there is another update within	2029	calls your callback, which does something. When there is another update
1654	the same second, C<ev_stat> will be unable to detect it.	2030	within the same second, C<ev_stat> will be unable to detect unless the
		2031	stat data does change in other ways (e.g. file size).
1655		2032
1656	The solution to this is to delay acting on a change for a second (or till	2033	The solution to this is to delay acting on a change for slightly more
1657	the next second boundary), using a roughly one-second delay C<ev_timer>	2034	than a second (or till slightly after the next full second boundary), using
1658	(C<ev_timer_set (w, 0., 1.01); ev_timer_again (loop, w)>). The C<.01>	2035	a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);
1659	is added to work around small timing inconsistencies of some operating	2036	ev_timer_again (loop, w)>).
1660	systems.	2037
		2038	The C<.02> offset is added to work around small timing inconsistencies
		2039	of some operating systems (where the second counter of the current time
		2040	might be be delayed. One such system is the Linux kernel, where a call to
		2041	C<gettimeofday> might return a timestamp with a full second later than
		2042	a subsequent C<time> call - if the equivalent of C<time ()> is used to
		2043	update file times then there will be a small window where the kernel uses
		2044	the previous second to update file times but libev might already execute
		2045	the timer callback).
1661		2046
1662	=head3 Watcher-Specific Functions and Data Members	2047	=head3 Watcher-Specific Functions and Data Members
1663		2048
1664	=over 4	2049	=over 4
1665		2050
…		…
1671	C<path>. The C<interval> is a hint on how quickly a change is expected to	2056	C<path>. The C<interval> is a hint on how quickly a change is expected to
1672	be detected and should normally be specified as C<0> to let libev choose	2057	be detected and should normally be specified as C<0> to let libev choose
1673	a suitable value. The memory pointed to by C<path> must point to the same	2058	a suitable value. The memory pointed to by C<path> must point to the same
1674	path for as long as the watcher is active.	2059	path for as long as the watcher is active.
1675		2060
1676	The callback will be receive C<EV_STAT> when a change was detected,	2061	The callback will receive an C<EV_STAT> event when a change was detected,
1677	relative to the attributes at the time the watcher was started (or the	2062	relative to the attributes at the time the watcher was started (or the
1678	last change was detected).	2063	last change was detected).
1679		2064
1680	=item ev_stat_stat (loop, ev_stat *)	2065	=item ev_stat_stat (loop, ev_stat *)
1681		2066
1682	Updates the stat buffer immediately with new values. If you change the	2067	Updates the stat buffer immediately with new values. If you change the
1683	watched path in your callback, you could call this fucntion to avoid	2068	watched path in your callback, you could call this function to avoid
1684	detecting this change (while introducing a race condition). Can also be	2069	detecting this change (while introducing a race condition if you are not
1685	useful simply to find out the new values.	2070	the only one changing the path). Can also be useful simply to find out the
		2071	new values.
1686		2072
1687	=item ev_statdata attr [read-only]	2073	=item ev_statdata attr [read-only]
1688		2074
1689	The most-recently detected attributes of the file. Although the type is of	2075	The most-recently detected attributes of the file. Although the type is
1690	C<ev_statdata>, this is usually the (or one of the) C<struct stat> types	2076	C<ev_statdata>, this is usually the (or one of the) C<struct stat> types
1691	suitable for your system. If the C<st_nlink> member is C<0>, then there	2077	suitable for your system, but you can only rely on the POSIX-standardised
		2078	members to be present. If the C<st_nlink> member is C<0>, then there was
1692	was some error while C<stat>ing the file.	2079	some error while C<stat>ing the file.
1693		2080
1694	=item ev_statdata prev [read-only]	2081	=item ev_statdata prev [read-only]
1695		2082
1696	The previous attributes of the file. The callback gets invoked whenever	2083	The previous attributes of the file. The callback gets invoked whenever
1697	C<prev> != C<attr>.	2084	C<prev> != C<attr>, or, more precisely, one or more of these members
		2085	differ: C<st_dev>, C<st_ino>, C<st_mode>, C<st_nlink>, C<st_uid>,
		2086	C<st_gid>, C<st_rdev>, C<st_size>, C<st_atime>, C<st_mtime>, C<st_ctime>.
1698		2087
1699	=item ev_tstamp interval [read-only]	2088	=item ev_tstamp interval [read-only]
1700		2089
1701	The specified interval.	2090	The specified interval.
1702		2091
1703	=item const char *path [read-only]	2092	=item const char *path [read-only]
1704		2093
1705	The filesystem path that is being watched.	2094	The file system path that is being watched.
1706		2095
1707	=back	2096	=back
1708		2097
1709	=head3 Examples	2098	=head3 Examples
1710		2099
1711	Example: Watch C</etc/passwd> for attribute changes.	2100	Example: Watch C</etc/passwd> for attribute changes.
1712		2101
1713	static void	2102	static void
1714	passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)	2103	passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
1715	{	2104	{
1716	/* /etc/passwd changed in some way */	2105	/* /etc/passwd changed in some way */
1717	if (w->attr.st_nlink)	2106	if (w->attr.st_nlink)
1718	{	2107	{
1719	printf ("passwd current size %ld\n", (long)w->attr.st_size);	2108	printf ("passwd current size %ld\n", (long)w->attr.st_size);
1720	printf ("passwd current atime %ld\n", (long)w->attr.st_mtime);	2109	printf ("passwd current atime %ld\n", (long)w->attr.st_mtime);
1721	printf ("passwd current mtime %ld\n", (long)w->attr.st_mtime);	2110	printf ("passwd current mtime %ld\n", (long)w->attr.st_mtime);
1722	}	2111	}
1723	else	2112	else
1724	/* you shalt not abuse printf for puts */	2113	/* you shalt not abuse printf for puts */
1725	puts ("wow, /etc/passwd is not there, expect problems. "	2114	puts ("wow, /etc/passwd is not there, expect problems. "
1726	"if this is windows, they already arrived\n");	2115	"if this is windows, they already arrived\n");
1727	}	2116	}
1728		2117
1729	...	2118	...
1730	ev_stat passwd;	2119	ev_stat passwd;
1731		2120
1732	ev_stat_init (&passwd, passwd_cb, "/etc/passwd", 0.);	2121	ev_stat_init (&passwd, passwd_cb, "/etc/passwd", 0.);
1733	ev_stat_start (loop, &passwd);	2122	ev_stat_start (loop, &passwd);
1734		2123
1735	Example: Like above, but additionally use a one-second delay so we do not	2124	Example: Like above, but additionally use a one-second delay so we do not
1736	miss updates (however, frequent updates will delay processing, too, so	2125	miss updates (however, frequent updates will delay processing, too, so
1737	one might do the work both on C<ev_stat> callback invocation I<and> on	2126	one might do the work both on C<ev_stat> callback invocation I<and> on
1738	C<ev_timer> callback invocation).	2127	C<ev_timer> callback invocation).
1739		2128
1740	static ev_stat passwd;	2129	static ev_stat passwd;
1741	static ev_timer timer;	2130	static ev_timer timer;
1742		2131
1743	static void	2132	static void
1744	timer_cb (EV_P_ ev_timer *w, int revents)	2133	timer_cb (EV_P_ ev_timer *w, int revents)
1745	{	2134	{
1746	ev_timer_stop (EV_A_ w);	2135	ev_timer_stop (EV_A_ w);
1747		2136
1748	/* now it's one second after the most recent passwd change */	2137	/* now it's one second after the most recent passwd change */
1749	}	2138	}
1750		2139
1751	static void	2140	static void
1752	stat_cb (EV_P_ ev_stat *w, int revents)	2141	stat_cb (EV_P_ ev_stat *w, int revents)
1753	{	2142	{
1754	/* reset the one-second timer */	2143	/* reset the one-second timer */
1755	ev_timer_again (EV_A_ &timer);	2144	ev_timer_again (EV_A_ &timer);
1756	}	2145	}
1757		2146
1758	...	2147	...
1759	ev_stat_init (&passwd, stat_cb, "/etc/passwd", 0.);	2148	ev_stat_init (&passwd, stat_cb, "/etc/passwd", 0.);
1760	ev_stat_start (loop, &passwd);	2149	ev_stat_start (loop, &passwd);
1761	ev_timer_init (&timer, timer_cb, 0., 1.01);	2150	ev_timer_init (&timer, timer_cb, 0., 1.02);
1762		2151
1763		2152
1764	=head2 C<ev_idle> - when you've got nothing better to do...	2153	=head2 C<ev_idle> - when you've got nothing better to do...
1765		2154
1766	Idle watchers trigger events when no other events of the same or higher	2155	Idle watchers trigger events when no other events of the same or higher
1767	priority are pending (prepare, check and other idle watchers do not	2156	priority are pending (prepare, check and other idle watchers do not count
1768	count).	2157	as receiving "events").
1769		2158
1770	That is, as long as your process is busy handling sockets or timeouts	2159	That is, as long as your process is busy handling sockets or timeouts
1771	(or even signals, imagine) of the same or higher priority it will not be	2160	(or even signals, imagine) of the same or higher priority it will not be
1772	triggered. But when your process is idle (or only lower-priority watchers	2161	triggered. But when your process is idle (or only lower-priority watchers
1773	are pending), the idle watchers are being called once per event loop	2162	are pending), the idle watchers are being called once per event loop
…		…
1797	=head3 Examples	2186	=head3 Examples
1798		2187
1799	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the	2188	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
1800	callback, free it. Also, use no error checking, as usual.	2189	callback, free it. Also, use no error checking, as usual.
1801		2190
1802	static void	2191	static void
1803	idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)	2192	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)
1804	{	2193	{
1805	free (w);	2194	free (w);
1806	// now do something you wanted to do when the program has	2195	// now do something you wanted to do when the program has
1807	// no longer anything immediate to do.	2196	// no longer anything immediate to do.
1808	}	2197	}
1809		2198
1810	struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));	2199	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
1811	ev_idle_init (idle_watcher, idle_cb);	2200	ev_idle_init (idle_watcher, idle_cb);
1812	ev_idle_start (loop, idle_cb);	2201	ev_idle_start (loop, idle_cb);
1813		2202
1814		2203
1815	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2204	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
1816		2205
1817	Prepare and check watchers are usually (but not always) used in tandem:	2206	Prepare and check watchers are usually (but not always) used in pairs:
1818	prepare watchers get invoked before the process blocks and check watchers	2207	prepare watchers get invoked before the process blocks and check watchers
1819	afterwards.	2208	afterwards.
1820		2209
1821	You I<must not> call C<ev_loop> or similar functions that enter	2210	You I<must not> call C<ev_loop> or similar functions that enter
1822	the current event loop from either C<ev_prepare> or C<ev_check>	2211	the current event loop from either C<ev_prepare> or C<ev_check>
…		…
1825	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2214	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
1826	C<ev_check> so if you have one watcher of each kind they will always be	2215	C<ev_check> so if you have one watcher of each kind they will always be
1827	called in pairs bracketing the blocking call.	2216	called in pairs bracketing the blocking call.
1828		2217
1829	Their main purpose is to integrate other event mechanisms into libev and	2218	Their main purpose is to integrate other event mechanisms into libev and
1830	their use is somewhat advanced. This could be used, for example, to track	2219	their use is somewhat advanced. They could be used, for example, to track
1831	variable changes, implement your own watchers, integrate net-snmp or a	2220	variable changes, implement your own watchers, integrate net-snmp or a
1832	coroutine library and lots more. They are also occasionally useful if	2221	coroutine library and lots more. They are also occasionally useful if
1833	you cache some data and want to flush it before blocking (for example,	2222	you cache some data and want to flush it before blocking (for example,
1834	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>	2223	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>
1835	watcher).	2224	watcher).
1836		2225
1837	This is done by examining in each prepare call which file descriptors need	2226	This is done by examining in each prepare call which file descriptors
1838	to be watched by the other library, registering C<ev_io> watchers for	2227	need to be watched by the other library, registering C<ev_io> watchers
1839	them and starting an C<ev_timer> watcher for any timeouts (many libraries	2228	for them and starting an C<ev_timer> watcher for any timeouts (many
1840	provide just this functionality). Then, in the check watcher you check for	2229	libraries provide exactly this functionality). Then, in the check watcher,
1841	any events that occured (by checking the pending status of all watchers	2230	you check for any events that occurred (by checking the pending status
1842	and stopping them) and call back into the library. The I/O and timer	2231	of all watchers and stopping them) and call back into the library. The
1843	callbacks will never actually be called (but must be valid nevertheless,	2232	I/O and timer callbacks will never actually be called (but must be valid
1844	because you never know, you know?).	2233	nevertheless, because you never know, you know?).
1845		2234
1846	As another example, the Perl Coro module uses these hooks to integrate	2235	As another example, the Perl Coro module uses these hooks to integrate
1847	coroutines into libev programs, by yielding to other active coroutines	2236	coroutines into libev programs, by yielding to other active coroutines
1848	during each prepare and only letting the process block if no coroutines	2237	during each prepare and only letting the process block if no coroutines
1849	are ready to run (it's actually more complicated: it only runs coroutines	2238	are ready to run (it's actually more complicated: it only runs coroutines
…		…
1852	loop from blocking if lower-priority coroutines are active, thus mapping	2241	loop from blocking if lower-priority coroutines are active, thus mapping
1853	low-priority coroutines to idle/background tasks).	2242	low-priority coroutines to idle/background tasks).
1854		2243
1855	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)	2244	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)
1856	priority, to ensure that they are being run before any other watchers	2245	priority, to ensure that they are being run before any other watchers
		2246	after the poll (this doesn't matter for C<ev_prepare> watchers).
		2247
1857	after the poll. Also, C<ev_check> watchers (and C<ev_prepare> watchers,	2248	Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not
1858	too) should not activate ("feed") events into libev. While libev fully	2249	activate ("feed") events into libev. While libev fully supports this, they
1859	supports this, they will be called before other C<ev_check> watchers	2250	might get executed before other C<ev_check> watchers did their job. As
1860	did their job. As C<ev_check> watchers are often used to embed other	2251	C<ev_check> watchers are often used to embed other (non-libev) event
1861	(non-libev) event loops those other event loops might be in an unusable	2252	loops those other event loops might be in an unusable state until their
1862	state until their C<ev_check> watcher ran (always remind yourself to	2253	C<ev_check> watcher ran (always remind yourself to coexist peacefully with
1863	coexist peacefully with others).	2254	others).
1864		2255
1865	=head3 Watcher-Specific Functions and Data Members	2256	=head3 Watcher-Specific Functions and Data Members
1866		2257
1867	=over 4	2258	=over 4
1868		2259
…		…
1870		2261
1871	=item ev_check_init (ev_check *, callback)	2262	=item ev_check_init (ev_check *, callback)
1872		2263
1873	Initialises and configures the prepare or check watcher - they have no	2264	Initialises and configures the prepare or check watcher - they have no
1874	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>	2265	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>
1875	macros, but using them is utterly, utterly and completely pointless.	2266	macros, but using them is utterly, utterly, utterly and completely
		2267	pointless.
1876		2268
1877	=back	2269	=back
1878		2270
1879	=head3 Examples	2271	=head3 Examples
1880		2272
1881	There are a number of principal ways to embed other event loops or modules	2273	There are a number of principal ways to embed other event loops or modules
1882	into libev. Here are some ideas on how to include libadns into libev	2274	into libev. Here are some ideas on how to include libadns into libev
1883	(there is a Perl module named C<EV::ADNS> that does this, which you could	2275	(there is a Perl module named C<EV::ADNS> that does this, which you could
1884	use for an actually working example. Another Perl module named C<EV::Glib>	2276	use as a working example. Another Perl module named C<EV::Glib> embeds a
1885	embeds a Glib main context into libev, and finally, C<Glib::EV> embeds EV	2277	Glib main context into libev, and finally, C<Glib::EV> embeds EV into the
1886	into the Glib event loop).	2278	Glib event loop).
1887		2279
1888	Method 1: Add IO watchers and a timeout watcher in a prepare handler,	2280	Method 1: Add IO watchers and a timeout watcher in a prepare handler,
1889	and in a check watcher, destroy them and call into libadns. What follows	2281	and in a check watcher, destroy them and call into libadns. What follows
1890	is pseudo-code only of course. This requires you to either use a low	2282	is pseudo-code only of course. This requires you to either use a low
1891	priority for the check watcher or use C<ev_clear_pending> explicitly, as	2283	priority for the check watcher or use C<ev_clear_pending> explicitly, as
1892	the callbacks for the IO/timeout watchers might not have been called yet.	2284	the callbacks for the IO/timeout watchers might not have been called yet.
1893		2285
1894	static ev_io iow [nfd];	2286	static ev_io iow [nfd];
1895	static ev_timer tw;	2287	static ev_timer tw;
1896		2288
1897	static void	2289	static void
1898	io_cb (ev_loop *loop, ev_io *w, int revents)	2290	io_cb (struct ev_loop *loop, ev_io *w, int revents)
1899	{	2291	{
1900	}	2292	}
1901		2293
1902	// create io watchers for each fd and a timer before blocking	2294	// create io watchers for each fd and a timer before blocking
1903	static void	2295	static void
1904	adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)	2296	adns_prepare_cb (struct ev_loop *loop, ev_prepare *w, int revents)
1905	{	2297	{
1906	int timeout = 3600000;	2298	int timeout = 3600000;
1907	struct pollfd fds [nfd];	2299	struct pollfd fds [nfd];
1908	// actual code will need to loop here and realloc etc.	2300	// actual code will need to loop here and realloc etc.
1909	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	2301	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1910		2302
1911	/* the callback is illegal, but won't be called as we stop during check */	2303	/* the callback is illegal, but won't be called as we stop during check */
1912	ev_timer_init (&tw, 0, timeout * 1e-3);	2304	ev_timer_init (&tw, 0, timeout * 1e-3);
1913	ev_timer_start (loop, &tw);	2305	ev_timer_start (loop, &tw);
1914		2306
1915	// create one ev_io per pollfd	2307	// create one ev_io per pollfd
1916	for (int i = 0; i < nfd; ++i)	2308	for (int i = 0; i < nfd; ++i)
1917	{	2309	{
1918	ev_io_init (iow + i, io_cb, fds [i].fd,	2310	ev_io_init (iow + i, io_cb, fds [i].fd,
1919	((fds [i].events & POLLIN ? EV_READ : 0)	2311	((fds [i].events & POLLIN ? EV_READ : 0)
1920	| (fds [i].events & POLLOUT ? EV_WRITE : 0)));	2312	| (fds [i].events & POLLOUT ? EV_WRITE : 0)));
1921		2313
1922	fds [i].revents = 0;	2314	fds [i].revents = 0;
1923	ev_io_start (loop, iow + i);	2315	ev_io_start (loop, iow + i);
1924	}	2316	}
1925	}	2317	}
1926		2318
1927	// stop all watchers after blocking	2319	// stop all watchers after blocking
1928	static void	2320	static void
1929	adns_check_cb (ev_loop *loop, ev_check *w, int revents)	2321	adns_check_cb (struct ev_loop *loop, ev_check *w, int revents)
1930	{	2322	{
1931	ev_timer_stop (loop, &tw);	2323	ev_timer_stop (loop, &tw);
1932		2324
1933	for (int i = 0; i < nfd; ++i)	2325	for (int i = 0; i < nfd; ++i)
1934	{	2326	{
1935	// set the relevant poll flags	2327	// set the relevant poll flags
1936	// could also call adns_processreadable etc. here	2328	// could also call adns_processreadable etc. here
1937	struct pollfd *fd = fds + i;	2329	struct pollfd *fd = fds + i;
1938	int revents = ev_clear_pending (iow + i);	2330	int revents = ev_clear_pending (iow + i);
1939	if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;	2331	if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1940	if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;	2332	if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1941		2333
1942	// now stop the watcher	2334	// now stop the watcher
1943	ev_io_stop (loop, iow + i);	2335	ev_io_stop (loop, iow + i);
1944	}	2336	}
1945		2337
1946	adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));	2338	adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1947	}	2339	}
1948		2340
1949	Method 2: This would be just like method 1, but you run C<adns_afterpoll>	2341	Method 2: This would be just like method 1, but you run C<adns_afterpoll>
1950	in the prepare watcher and would dispose of the check watcher.	2342	in the prepare watcher and would dispose of the check watcher.
1951		2343
1952	Method 3: If the module to be embedded supports explicit event	2344	Method 3: If the module to be embedded supports explicit event
1953	notification (adns does), you can also make use of the actual watcher	2345	notification (libadns does), you can also make use of the actual watcher
1954	callbacks, and only destroy/create the watchers in the prepare watcher.	2346	callbacks, and only destroy/create the watchers in the prepare watcher.
1955		2347
1956	static void	2348	static void
1957	timer_cb (EV_P_ ev_timer *w, int revents)	2349	timer_cb (EV_P_ ev_timer *w, int revents)
1958	{	2350	{
1959	adns_state ads = (adns_state)w->data;	2351	adns_state ads = (adns_state)w->data;
1960	update_now (EV_A);	2352	update_now (EV_A);
1961		2353
1962	adns_processtimeouts (ads, &tv_now);	2354	adns_processtimeouts (ads, &tv_now);
1963	}	2355	}
1964		2356
1965	static void	2357	static void
1966	io_cb (EV_P_ ev_io *w, int revents)	2358	io_cb (EV_P_ ev_io *w, int revents)
1967	{	2359	{
1968	adns_state ads = (adns_state)w->data;	2360	adns_state ads = (adns_state)w->data;
1969	update_now (EV_A);	2361	update_now (EV_A);
1970		2362
1971	if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now);	2363	if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now);
1972	if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now);	2364	if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now);
1973	}	2365	}
1974		2366
1975	// do not ever call adns_afterpoll	2367	// do not ever call adns_afterpoll
1976		2368
1977	Method 4: Do not use a prepare or check watcher because the module you	2369	Method 4: Do not use a prepare or check watcher because the module you
1978	want to embed is too inflexible to support it. Instead, youc na override	2370	want to embed is not flexible enough to support it. Instead, you can
1979	their poll function. The drawback with this solution is that the main	2371	override their poll function. The drawback with this solution is that the
1980	loop is now no longer controllable by EV. The C<Glib::EV> module does	2372	main loop is now no longer controllable by EV. The C<Glib::EV> module uses
1981	this.	2373	this approach, effectively embedding EV as a client into the horrible
		2374	libglib event loop.
1982		2375
1983	static gint	2376	static gint
1984	event_poll_func (GPollFD *fds, guint nfds, gint timeout)	2377	event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1985	{	2378	{
1986	int got_events = 0;	2379	int got_events = 0;
1987		2380
1988	for (n = 0; n < nfds; ++n)	2381	for (n = 0; n < nfds; ++n)
1989	// create/start io watcher that sets the relevant bits in fds[n] and increment got_events	2382	// create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1990		2383
1991	if (timeout >= 0)	2384	if (timeout >= 0)
1992	// create/start timer	2385	// create/start timer
1993		2386
1994	// poll	2387	// poll
1995	ev_loop (EV_A_ 0);	2388	ev_loop (EV_A_ 0);
1996		2389
1997	// stop timer again	2390	// stop timer again
1998	if (timeout >= 0)	2391	if (timeout >= 0)
1999	ev_timer_stop (EV_A_ &to);	2392	ev_timer_stop (EV_A_ &to);
2000		2393
2001	// stop io watchers again - their callbacks should have set	2394	// stop io watchers again - their callbacks should have set
2002	for (n = 0; n < nfds; ++n)	2395	for (n = 0; n < nfds; ++n)
2003	ev_io_stop (EV_A_ iow [n]);	2396	ev_io_stop (EV_A_ iow [n]);
2004		2397
2005	return got_events;	2398	return got_events;
2006	}	2399	}
2007		2400
2008		2401
2009	=head2 C<ev_embed> - when one backend isn't enough...	2402	=head2 C<ev_embed> - when one backend isn't enough...
2010		2403
2011	This is a rather advanced watcher type that lets you embed one event loop	2404	This is a rather advanced watcher type that lets you embed one event loop
…		…
2017	prioritise I/O.	2410	prioritise I/O.
2018		2411
2019	As an example for a bug workaround, the kqueue backend might only support	2412	As an example for a bug workaround, the kqueue backend might only support
2020	sockets on some platform, so it is unusable as generic backend, but you	2413	sockets on some platform, so it is unusable as generic backend, but you
2021	still want to make use of it because you have many sockets and it scales	2414	still want to make use of it because you have many sockets and it scales
2022	so nicely. In this case, you would create a kqueue-based loop and embed it	2415	so nicely. In this case, you would create a kqueue-based loop and embed
2023	into your default loop (which might use e.g. poll). Overall operation will	2416	it into your default loop (which might use e.g. poll). Overall operation
2024	be a bit slower because first libev has to poll and then call kevent, but	2417	will be a bit slower because first libev has to call C<poll> and then
2025	at least you can use both at what they are best.	2418	C<kevent>, but at least you can use both mechanisms for what they are
		2419	best: C<kqueue> for scalable sockets and C<poll> if you want it to work :)
2026		2420
2027	As for prioritising I/O: rarely you have the case where some fds have	2421	As for prioritising I/O: under rare circumstances you have the case where
2028	to be watched and handled very quickly (with low latency), and even	2422	some fds have to be watched and handled very quickly (with low latency),
2029	priorities and idle watchers might have too much overhead. In this case	2423	and even priorities and idle watchers might have too much overhead. In
2030	you would put all the high priority stuff in one loop and all the rest in	2424	this case you would put all the high priority stuff in one loop and all
2031	a second one, and embed the second one in the first.	2425	the rest in a second one, and embed the second one in the first.
2032		2426
2033	As long as the watcher is active, the callback will be invoked every time	2427	As long as the watcher is active, the callback will be invoked every time
2034	there might be events pending in the embedded loop. The callback must then	2428	there might be events pending in the embedded loop. The callback must then
2035	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke	2429	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke
2036	their callbacks (you could also start an idle watcher to give the embedded	2430	their callbacks (you could also start an idle watcher to give the embedded
…		…
2044	interested in that.	2438	interested in that.
2045		2439
2046	Also, there have not currently been made special provisions for forking:	2440	Also, there have not currently been made special provisions for forking:
2047	when you fork, you not only have to call C<ev_loop_fork> on both loops,	2441	when you fork, you not only have to call C<ev_loop_fork> on both loops,
2048	but you will also have to stop and restart any C<ev_embed> watchers	2442	but you will also have to stop and restart any C<ev_embed> watchers
2049	yourself.	2443	yourself - but you can use a fork watcher to handle this automatically,
		2444	and future versions of libev might do just that.
2050		2445
2051	Unfortunately, not all backends are embeddable, only the ones returned by	2446	Unfortunately, not all backends are embeddable: only the ones returned by
2052	C<ev_embeddable_backends> are, which, unfortunately, does not include any	2447	C<ev_embeddable_backends> are, which, unfortunately, does not include any
2053	portable one.	2448	portable one.
2054		2449
2055	So when you want to use this feature you will always have to be prepared	2450	So when you want to use this feature you will always have to be prepared
2056	that you cannot get an embeddable loop. The recommended way to get around	2451	that you cannot get an embeddable loop. The recommended way to get around
2057	this is to have a separate variables for your embeddable loop, try to	2452	this is to have a separate variables for your embeddable loop, try to
2058	create it, and if that fails, use the normal loop for everything.	2453	create it, and if that fails, use the normal loop for everything.
2059		2454
		2455	=head3 C<ev_embed> and fork
		2456
		2457	While the C<ev_embed> watcher is running, forks in the embedding loop will
		2458	automatically be applied to the embedded loop as well, so no special
		2459	fork handling is required in that case. When the watcher is not running,
		2460	however, it is still the task of the libev user to call C<ev_loop_fork ()>
		2461	as applicable.
		2462
2060	=head3 Watcher-Specific Functions and Data Members	2463	=head3 Watcher-Specific Functions and Data Members
2061		2464
2062	=over 4	2465	=over 4
2063		2466
2064	=item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)	2467	=item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)
…		…
2067		2470
2068	Configures the watcher to embed the given loop, which must be	2471	Configures the watcher to embed the given loop, which must be
2069	embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be	2472	embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be
2070	invoked automatically, otherwise it is the responsibility of the callback	2473	invoked automatically, otherwise it is the responsibility of the callback
2071	to invoke it (it will continue to be called until the sweep has been done,	2474	to invoke it (it will continue to be called until the sweep has been done,
2072	if you do not want thta, you need to temporarily stop the embed watcher).	2475	if you do not want that, you need to temporarily stop the embed watcher).
2073		2476
2074	=item ev_embed_sweep (loop, ev_embed *)	2477	=item ev_embed_sweep (loop, ev_embed *)
2075		2478
2076	Make a single, non-blocking sweep over the embedded loop. This works	2479	Make a single, non-blocking sweep over the embedded loop. This works
2077	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most	2480	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most
2078	apropriate way for embedded loops.	2481	appropriate way for embedded loops.
2079		2482
2080	=item struct ev_loop *other [read-only]	2483	=item struct ev_loop *other [read-only]
2081		2484
2082	The embedded event loop.	2485	The embedded event loop.
2083		2486
…		…
2085		2488
2086	=head3 Examples	2489	=head3 Examples
2087		2490
2088	Example: Try to get an embeddable event loop and embed it into the default	2491	Example: Try to get an embeddable event loop and embed it into the default
2089	event loop. If that is not possible, use the default loop. The default	2492	event loop. If that is not possible, use the default loop. The default
2090	loop is stored in C<loop_hi>, while the mebeddable loop is stored in	2493	loop is stored in C<loop_hi>, while the embeddable loop is stored in
2091	C<loop_lo> (which is C<loop_hi> in the acse no embeddable loop can be	2494	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be
2092	used).	2495	used).
2093		2496
2094	struct ev_loop *loop_hi = ev_default_init (0);	2497	struct ev_loop *loop_hi = ev_default_init (0);
2095	struct ev_loop *loop_lo = 0;	2498	struct ev_loop *loop_lo = 0;
2096	struct ev_embed embed;	2499	ev_embed embed;
2097		2500
2098	// see if there is a chance of getting one that works	2501	// see if there is a chance of getting one that works
2099	// (remember that a flags value of 0 means autodetection)	2502	// (remember that a flags value of 0 means autodetection)
2100	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()	2503	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
2101	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())	2504	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
2102	: 0;	2505	: 0;
2103		2506
2104	// if we got one, then embed it, otherwise default to loop_hi	2507	// if we got one, then embed it, otherwise default to loop_hi
2105	if (loop_lo)	2508	if (loop_lo)
2106	{	2509	{
2107	ev_embed_init (&embed, 0, loop_lo);	2510	ev_embed_init (&embed, 0, loop_lo);
2108	ev_embed_start (loop_hi, &embed);	2511	ev_embed_start (loop_hi, &embed);
2109	}	2512	}
2110	else	2513	else
2111	loop_lo = loop_hi;	2514	loop_lo = loop_hi;
2112		2515
2113	Example: Check if kqueue is available but not recommended and create	2516	Example: Check if kqueue is available but not recommended and create
2114	a kqueue backend for use with sockets (which usually work with any	2517	a kqueue backend for use with sockets (which usually work with any
2115	kqueue implementation). Store the kqueue/socket-only event loop in	2518	kqueue implementation). Store the kqueue/socket-only event loop in
2116	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).	2519	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
2117		2520
2118	struct ev_loop *loop = ev_default_init (0);	2521	struct ev_loop *loop = ev_default_init (0);
2119	struct ev_loop *loop_socket = 0;	2522	struct ev_loop *loop_socket = 0;
2120	struct ev_embed embed;	2523	ev_embed embed;
2121		2524
2122	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)	2525	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
2123	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))	2526	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
2124	{	2527	{
2125	ev_embed_init (&embed, 0, loop_socket);	2528	ev_embed_init (&embed, 0, loop_socket);
2126	ev_embed_start (loop, &embed);	2529	ev_embed_start (loop, &embed);
2127	}	2530	}
2128		2531
2129	if (!loop_socket)	2532	if (!loop_socket)
2130	loop_socket = loop;	2533	loop_socket = loop;
2131		2534
2132	// now use loop_socket for all sockets, and loop for everything else	2535	// now use loop_socket for all sockets, and loop for everything else
2133		2536
2134		2537
2135	=head2 C<ev_fork> - the audacity to resume the event loop after a fork	2538	=head2 C<ev_fork> - the audacity to resume the event loop after a fork
2136		2539
2137	Fork watchers are called when a C<fork ()> was detected (usually because	2540	Fork watchers are called when a C<fork ()> was detected (usually because
…		…
2181	is that the author does not know of a simple (or any) algorithm for a	2584	is that the author does not know of a simple (or any) algorithm for a
2182	multiple-writer-single-reader queue that works in all cases and doesn't	2585	multiple-writer-single-reader queue that works in all cases and doesn't
2183	need elaborate support such as pthreads.	2586	need elaborate support such as pthreads.
2184		2587
2185	That means that if you want to queue data, you have to provide your own	2588	That means that if you want to queue data, you have to provide your own
2186	queue. But at least I can tell you would implement locking around your	2589	queue. But at least I can tell you how to implement locking around your
2187	queue:	2590	queue:
2188		2591
2189	=over 4	2592	=over 4
2190		2593
2191	=item queueing from a signal handler context	2594	=item queueing from a signal handler context
2192		2595
2193	To implement race-free queueing, you simply add to the queue in the signal	2596	To implement race-free queueing, you simply add to the queue in the signal
2194	handler but you block the signal handler in the watcher callback. Here is an example that does that for	2597	handler but you block the signal handler in the watcher callback. Here is
2195	some fictitiuous SIGUSR1 handler:	2598	an example that does that for some fictitious SIGUSR1 handler:
2196		2599
2197	static ev_async mysig;	2600	static ev_async mysig;
2198		2601
2199	static void	2602	static void
2200	sigusr1_handler (void)	2603	sigusr1_handler (void)
…		…
2266	=over 4	2669	=over 4
2267		2670
2268	=item ev_async_init (ev_async *, callback)	2671	=item ev_async_init (ev_async *, callback)
2269		2672
2270	Initialises and configures the async watcher - it has no parameters of any	2673	Initialises and configures the async watcher - it has no parameters of any
2271	kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless,	2674	kind. There is a C<ev_async_set> macro, but using it is utterly pointless,
2272	believe me.	2675	trust me.
2273		2676
2274	=item ev_async_send (loop, ev_async *)	2677	=item ev_async_send (loop, ev_async *)
2275		2678
2276	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	2679	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
2277	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	2680	an C<EV_ASYNC> event on the watcher into the event loop. Unlike
2278	C<ev_feed_event>, this call is safe to do in other threads, signal or	2681	C<ev_feed_event>, this call is safe to do from other threads, signal or
2279	similar contexts (see the dicusssion of C<EV_ATOMIC_T> in the embedding	2682	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding
2280	section below on what exactly this means).	2683	section below on what exactly this means).
2281		2684
2282	This call incurs the overhead of a syscall only once per loop iteration,	2685	This call incurs the overhead of a system call only once per loop iteration,
2283	so while the overhead might be noticable, it doesn't apply to repeated	2686	so while the overhead might be noticeable, it doesn't apply to repeated
2284	calls to C<ev_async_send>.	2687	calls to C<ev_async_send>.
2285		2688
2286	=item bool = ev_async_pending (ev_async *)	2689	=item bool = ev_async_pending (ev_async *)
2287		2690
2288	Returns a non-zero value when C<ev_async_send> has been called on the	2691	Returns a non-zero value when C<ev_async_send> has been called on the
…		…
2290	event loop.	2693	event loop.
2291		2694
2292	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When	2695	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When
2293	the loop iterates next and checks for the watcher to have become active,	2696	the loop iterates next and checks for the watcher to have become active,
2294	it will reset the flag again. C<ev_async_pending> can be used to very	2697	it will reset the flag again. C<ev_async_pending> can be used to very
2295	quickly check wether invoking the loop might be a good idea.	2698	quickly check whether invoking the loop might be a good idea.
2296		2699
2297	Not that this does I<not> check wether the watcher itself is pending, only	2700	Not that this does I<not> check whether the watcher itself is pending, only
2298	wether it has been requested to make this watcher pending.	2701	whether it has been requested to make this watcher pending.
2299		2702
2300	=back	2703	=back
2301		2704
2302		2705
2303	=head1 OTHER FUNCTIONS	2706	=head1 OTHER FUNCTIONS
…		…
2307	=over 4	2710	=over 4
2308		2711
2309	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)	2712	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)
2310		2713
2311	This function combines a simple timer and an I/O watcher, calls your	2714	This function combines a simple timer and an I/O watcher, calls your
2312	callback on whichever event happens first and automatically stop both	2715	callback on whichever event happens first and automatically stops both
2313	watchers. This is useful if you want to wait for a single event on an fd	2716	watchers. This is useful if you want to wait for a single event on an fd
2314	or timeout without having to allocate/configure/start/stop/free one or	2717	or timeout without having to allocate/configure/start/stop/free one or
2315	more watchers yourself.	2718	more watchers yourself.
2316		2719
2317	If C<fd> is less than 0, then no I/O watcher will be started and events	2720	If C<fd> is less than 0, then no I/O watcher will be started and the
2318	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and	2721	C<events> argument is being ignored. Otherwise, an C<ev_io> watcher for
2319	C<events> set will be craeted and started.	2722	the given C<fd> and C<events> set will be created and started.
2320		2723
2321	If C<timeout> is less than 0, then no timeout watcher will be	2724	If C<timeout> is less than 0, then no timeout watcher will be
2322	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	2725	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
2323	repeat = 0) will be started. While C<0> is a valid timeout, it is of	2726	repeat = 0) will be started. C<0> is a valid timeout.
2324	dubious value.
2325		2727
2326	The callback has the type C<void (*cb)(int revents, void *arg)> and gets	2728	The callback has the type C<void (*cb)(int revents, void *arg)> and gets
2327	passed an C<revents> set like normal event callbacks (a combination of	2729	passed an C<revents> set like normal event callbacks (a combination of
2328	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	2730	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>
2329	value passed to C<ev_once>:	2731	value passed to C<ev_once>. Note that it is possible to receive I<both>
		2732	a timeout and an io event at the same time - you probably should give io
		2733	events precedence.
2330		2734
		2735	Example: wait up to ten seconds for data to appear on STDIN_FILENO.
		2736
2331	static void stdin_ready (int revents, void *arg)	2737	static void stdin_ready (int revents, void *arg)
2332	{	2738	{
2333	if (revents & EV_TIMEOUT)
2334	/* doh, nothing entered */;
2335	else if (revents & EV_READ)	2739	if (revents & EV_READ)
2336	/* stdin might have data for us, joy! */;	2740	/* stdin might have data for us, joy! */;
		2741	else if (revents & EV_TIMEOUT)
		2742	/* doh, nothing entered */;
2337	}	2743	}
2338		2744
2339	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	2745	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
2340		2746
2341	=item ev_feed_event (ev_loop *, watcher *, int revents)	2747	=item ev_feed_event (struct ev_loop *, watcher *, int revents)
2342		2748
2343	Feeds the given event set into the event loop, as if the specified event	2749	Feeds the given event set into the event loop, as if the specified event
2344	had happened for the specified watcher (which must be a pointer to an	2750	had happened for the specified watcher (which must be a pointer to an
2345	initialised but not necessarily started event watcher).	2751	initialised but not necessarily started event watcher).
2346		2752
2347	=item ev_feed_fd_event (ev_loop *, int fd, int revents)	2753	=item ev_feed_fd_event (struct ev_loop *, int fd, int revents)
2348		2754
2349	Feed an event on the given fd, as if a file descriptor backend detected	2755	Feed an event on the given fd, as if a file descriptor backend detected
2350	the given events it.	2756	the given events it.
2351		2757
2352	=item ev_feed_signal_event (ev_loop *loop, int signum)	2758	=item ev_feed_signal_event (struct ev_loop *loop, int signum)
2353		2759
2354	Feed an event as if the given signal occured (C<loop> must be the default	2760	Feed an event as if the given signal occurred (C<loop> must be the default
2355	loop!).	2761	loop!).
2356		2762
2357	=back	2763	=back
2358		2764
2359		2765
…		…
2375		2781
2376	=item * Priorities are not currently supported. Initialising priorities	2782	=item * Priorities are not currently supported. Initialising priorities
2377	will fail and all watchers will have the same priority, even though there	2783	will fail and all watchers will have the same priority, even though there
2378	is an ev_pri field.	2784	is an ev_pri field.
2379		2785
		2786	=item * In libevent, the last base created gets the signals, in libev, the
		2787	first base created (== the default loop) gets the signals.
		2788
2380	=item * Other members are not supported.	2789	=item * Other members are not supported.
2381		2790
2382	=item * The libev emulation is I<not> ABI compatible to libevent, you need	2791	=item * The libev emulation is I<not> ABI compatible to libevent, you need
2383	to use the libev header file and library.	2792	to use the libev header file and library.
2384		2793
2385	=back	2794	=back
2386		2795
2387	=head1 C++ SUPPORT	2796	=head1 C++ SUPPORT
2388		2797
2389	Libev comes with some simplistic wrapper classes for C++ that mainly allow	2798	Libev comes with some simplistic wrapper classes for C++ that mainly allow
2390	you to use some convinience methods to start/stop watchers and also change	2799	you to use some convenience methods to start/stop watchers and also change
2391	the callback model to a model using method callbacks on objects.	2800	the callback model to a model using method callbacks on objects.
2392		2801
2393	To use it,	2802	To use it,
2394		2803
2395	#include <ev++.h>	2804	#include <ev++.h>
2396		2805
2397	This automatically includes F<ev.h> and puts all of its definitions (many	2806	This automatically includes F<ev.h> and puts all of its definitions (many
2398	of them macros) into the global namespace. All C++ specific things are	2807	of them macros) into the global namespace. All C++ specific things are
2399	put into the C<ev> namespace. It should support all the same embedding	2808	put into the C<ev> namespace. It should support all the same embedding
2400	options as F<ev.h>, most notably C<EV_MULTIPLICITY>.	2809	options as F<ev.h>, most notably C<EV_MULTIPLICITY>.
…		…
2467	your compiler is good :), then the method will be fully inlined into the	2876	your compiler is good :), then the method will be fully inlined into the
2468	thunking function, making it as fast as a direct C callback.	2877	thunking function, making it as fast as a direct C callback.
2469		2878
2470	Example: simple class declaration and watcher initialisation	2879	Example: simple class declaration and watcher initialisation
2471		2880
2472	struct myclass	2881	struct myclass
2473	{	2882	{
2474	void io_cb (ev::io &w, int revents) { }	2883	void io_cb (ev::io &w, int revents) { }
2475	}	2884	}
2476		2885
2477	myclass obj;	2886	myclass obj;
2478	ev::io iow;	2887	ev::io iow;
2479	iow.set <myclass, &myclass::io_cb> (&obj);	2888	iow.set <myclass, &myclass::io_cb> (&obj);
2480		2889
2481	=item w->set<function> (void *data = 0)	2890	=item w->set<function> (void *data = 0)
2482		2891
2483	Also sets a callback, but uses a static method or plain function as	2892	Also sets a callback, but uses a static method or plain function as
2484	callback. The optional C<data> argument will be stored in the watcher's	2893	callback. The optional C<data> argument will be stored in the watcher's
…		…
2486		2895
2487	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.	2896	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.
2488		2897
2489	See the method-C<set> above for more details.	2898	See the method-C<set> above for more details.
2490		2899
2491	Example:	2900	Example: Use a plain function as callback.
2492		2901
2493	static void io_cb (ev::io &w, int revents) { }	2902	static void io_cb (ev::io &w, int revents) { }
2494	iow.set <io_cb> ();	2903	iow.set <io_cb> ();
2495		2904
2496	=item w->set (struct ev_loop *)	2905	=item w->set (struct ev_loop *)
2497		2906
2498	Associates a different C<struct ev_loop> with this watcher. You can only	2907	Associates a different C<struct ev_loop> with this watcher. You can only
2499	do this when the watcher is inactive (and not pending either).	2908	do this when the watcher is inactive (and not pending either).
2500		2909
2501	=item w->set ([args])	2910	=item w->set ([arguments])
2502		2911
2503	Basically the same as C<ev_TYPE_set>, with the same args. Must be	2912	Basically the same as C<ev_TYPE_set>, with the same arguments. Must be
2504	called at least once. Unlike the C counterpart, an active watcher gets	2913	called at least once. Unlike the C counterpart, an active watcher gets
2505	automatically stopped and restarted when reconfiguring it with this	2914	automatically stopped and restarted when reconfiguring it with this
2506	method.	2915	method.
2507		2916
2508	=item w->start ()	2917	=item w->start ()
…		…
2532	=back	2941	=back
2533		2942
2534	Example: Define a class with an IO and idle watcher, start one of them in	2943	Example: Define a class with an IO and idle watcher, start one of them in
2535	the constructor.	2944	the constructor.
2536		2945
2537	class myclass	2946	class myclass
2538	{	2947	{
2539	ev::io io; void io_cb (ev::io &w, int revents);	2948	ev::io io ; void io_cb (ev::io &w, int revents);
2540	ev:idle idle void idle_cb (ev::idle &w, int revents);	2949	ev::idle idle; void idle_cb (ev::idle &w, int revents);
2541		2950
2542	myclass (int fd)	2951	myclass (int fd)
2543	{	2952	{
2544	io .set <myclass, &myclass::io_cb > (this);	2953	io .set <myclass, &myclass::io_cb > (this);
2545	idle.set <myclass, &myclass::idle_cb> (this);	2954	idle.set <myclass, &myclass::idle_cb> (this);
2546		2955
2547	io.start (fd, ev::READ);	2956	io.start (fd, ev::READ);
2548	}	2957	}
2549	};	2958	};
2550		2959
2551		2960
2552	=head1 OTHER LANGUAGE BINDINGS	2961	=head1 OTHER LANGUAGE BINDINGS
2553		2962
2554	Libev does not offer other language bindings itself, but bindings for a	2963	Libev does not offer other language bindings itself, but bindings for a
2555	numbe rof languages exist in the form of third-party packages. If you know	2964	number of languages exist in the form of third-party packages. If you know
2556	any interesting language binding in addition to the ones listed here, drop	2965	any interesting language binding in addition to the ones listed here, drop
2557	me a note.	2966	me a note.
2558		2967
2559	=over 4	2968	=over 4
2560		2969
2561	=item Perl	2970	=item Perl
2562		2971
2563	The EV module implements the full libev API and is actually used to test	2972	The EV module implements the full libev API and is actually used to test
2564	libev. EV is developed together with libev. Apart from the EV core module,	2973	libev. EV is developed together with libev. Apart from the EV core module,
2565	there are additional modules that implement libev-compatible interfaces	2974	there are additional modules that implement libev-compatible interfaces
2566	to C<libadns> (C<EV::ADNS>), C<Net::SNMP> (C<Net::SNMP::EV>) and the	2975	to C<libadns> (C<EV::ADNS>, but C<AnyEvent::DNS> is preferred nowadays),
2567	C<libglib> event core (C<Glib::EV> and C<EV::Glib>).	2976	C<Net::SNMP> (C<Net::SNMP::EV>) and the C<libglib> event core (C<Glib::EV>
		2977	and C<EV::Glib>).
2568		2978
2569	It can be found and installed via CPAN, its homepage is found at	2979	It can be found and installed via CPAN, its homepage is at
2570	L<http://software.schmorp.de/pkg/EV>.	2980	L<http://software.schmorp.de/pkg/EV>.
2571		2981
		2982	=item Python
		2983
		2984	Python bindings can be found at L<http://code.google.com/p/pyev/>. It
		2985	seems to be quite complete and well-documented. Note, however, that the
		2986	patch they require for libev is outright dangerous as it breaks the ABI
		2987	for everybody else, and therefore, should never be applied in an installed
		2988	libev (if python requires an incompatible ABI then it needs to embed
		2989	libev).
		2990
2572	=item Ruby	2991	=item Ruby
2573		2992
2574	Tony Arcieri has written a ruby extension that offers access to a subset	2993	Tony Arcieri has written a ruby extension that offers access to a subset
2575	of the libev API and adds filehandle abstractions, asynchronous DNS and	2994	of the libev API and adds file handle abstractions, asynchronous DNS and
2576	more on top of it. It can be found via gem servers. Its homepage is at	2995	more on top of it. It can be found via gem servers. Its homepage is at
2577	L<http://rev.rubyforge.org/>.	2996	L<http://rev.rubyforge.org/>.
2578		2997
2579	=item D	2998	=item D
2580		2999
2581	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3000	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2582	be found at L<http://git.llucax.com.ar/?p=software/ev.d.git;a=summary>.	3001	be found at L<http://proj.llucax.com.ar/wiki/evd>.
		3002
		3003	=item Ocaml
		3004
		3005	Erkki Seppala has written Ocaml bindings for libev, to be found at
		3006	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
2583		3007
2584	=back	3008	=back
2585		3009
2586		3010
2587	=head1 MACRO MAGIC	3011	=head1 MACRO MAGIC
2588		3012
2589	Libev can be compiled with a variety of options, the most fundamantal	3013	Libev can be compiled with a variety of options, the most fundamental
2590	of which is C<EV_MULTIPLICITY>. This option determines whether (most)	3014	of which is C<EV_MULTIPLICITY>. This option determines whether (most)
2591	functions and callbacks have an initial C<struct ev_loop *> argument.	3015	functions and callbacks have an initial C<struct ev_loop *> argument.
2592		3016
2593	To make it easier to write programs that cope with either variant, the	3017	To make it easier to write programs that cope with either variant, the
2594	following macros are defined:	3018	following macros are defined:
…		…
2599		3023
2600	This provides the loop I<argument> for functions, if one is required ("ev	3024	This provides the loop I<argument> for functions, if one is required ("ev
2601	loop argument"). The C<EV_A> form is used when this is the sole argument,	3025	loop argument"). The C<EV_A> form is used when this is the sole argument,
2602	C<EV_A_> is used when other arguments are following. Example:	3026	C<EV_A_> is used when other arguments are following. Example:
2603		3027
2604	ev_unref (EV_A);	3028	ev_unref (EV_A);
2605	ev_timer_add (EV_A_ watcher);	3029	ev_timer_add (EV_A_ watcher);
2606	ev_loop (EV_A_ 0);	3030	ev_loop (EV_A_ 0);
2607		3031
2608	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,	3032	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
2609	which is often provided by the following macro.	3033	which is often provided by the following macro.
2610		3034
2611	=item C<EV_P>, C<EV_P_>	3035	=item C<EV_P>, C<EV_P_>
2612		3036
2613	This provides the loop I<parameter> for functions, if one is required ("ev	3037	This provides the loop I<parameter> for functions, if one is required ("ev
2614	loop parameter"). The C<EV_P> form is used when this is the sole parameter,	3038	loop parameter"). The C<EV_P> form is used when this is the sole parameter,
2615	C<EV_P_> is used when other parameters are following. Example:	3039	C<EV_P_> is used when other parameters are following. Example:
2616		3040
2617	// this is how ev_unref is being declared	3041	// this is how ev_unref is being declared
2618	static void ev_unref (EV_P);	3042	static void ev_unref (EV_P);
2619		3043
2620	// this is how you can declare your typical callback	3044	// this is how you can declare your typical callback
2621	static void cb (EV_P_ ev_timer *w, int revents)	3045	static void cb (EV_P_ ev_timer *w, int revents)
2622		3046
2623	It declares a parameter C<loop> of type C<struct ev_loop *>, quite	3047	It declares a parameter C<loop> of type C<struct ev_loop *>, quite
2624	suitable for use with C<EV_A>.	3048	suitable for use with C<EV_A>.
2625		3049
2626	=item C<EV_DEFAULT>, C<EV_DEFAULT_>	3050	=item C<EV_DEFAULT>, C<EV_DEFAULT_>
…		…
2642		3066
2643	Example: Declare and initialise a check watcher, utilising the above	3067	Example: Declare and initialise a check watcher, utilising the above
2644	macros so it will work regardless of whether multiple loops are supported	3068	macros so it will work regardless of whether multiple loops are supported
2645	or not.	3069	or not.
2646		3070
2647	static void	3071	static void
2648	check_cb (EV_P_ ev_timer *w, int revents)	3072	check_cb (EV_P_ ev_timer *w, int revents)
2649	{	3073	{
2650	ev_check_stop (EV_A_ w);	3074	ev_check_stop (EV_A_ w);
2651	}	3075	}
2652		3076
2653	ev_check check;	3077	ev_check check;
2654	ev_check_init (&check, check_cb);	3078	ev_check_init (&check, check_cb);
2655	ev_check_start (EV_DEFAULT_ &check);	3079	ev_check_start (EV_DEFAULT_ &check);
2656	ev_loop (EV_DEFAULT_ 0);	3080	ev_loop (EV_DEFAULT_ 0);
2657		3081
2658	=head1 EMBEDDING	3082	=head1 EMBEDDING
2659		3083
2660	Libev can (and often is) directly embedded into host	3084	Libev can (and often is) directly embedded into host
2661	applications. Examples of applications that embed it include the Deliantra	3085	applications. Examples of applications that embed it include the Deliantra
…		…
2668	libev somewhere in your source tree).	3092	libev somewhere in your source tree).
2669		3093
2670	=head2 FILESETS	3094	=head2 FILESETS
2671		3095
2672	Depending on what features you need you need to include one or more sets of files	3096	Depending on what features you need you need to include one or more sets of files
2673	in your app.	3097	in your application.
2674		3098
2675	=head3 CORE EVENT LOOP	3099	=head3 CORE EVENT LOOP
2676		3100
2677	To include only the libev core (all the C<ev_*> functions), with manual	3101	To include only the libev core (all the C<ev_*> functions), with manual
2678	configuration (no autoconf):	3102	configuration (no autoconf):
2679		3103
2680	#define EV_STANDALONE 1	3104	#define EV_STANDALONE 1
2681	#include "ev.c"	3105	#include "ev.c"
2682		3106
2683	This will automatically include F<ev.h>, too, and should be done in a	3107	This will automatically include F<ev.h>, too, and should be done in a
2684	single C source file only to provide the function implementations. To use	3108	single C source file only to provide the function implementations. To use
2685	it, do the same for F<ev.h> in all files wishing to use this API (best	3109	it, do the same for F<ev.h> in all files wishing to use this API (best
2686	done by writing a wrapper around F<ev.h> that you can include instead and	3110	done by writing a wrapper around F<ev.h> that you can include instead and
2687	where you can put other configuration options):	3111	where you can put other configuration options):
2688		3112
2689	#define EV_STANDALONE 1	3113	#define EV_STANDALONE 1
2690	#include "ev.h"	3114	#include "ev.h"
2691		3115
2692	Both header files and implementation files can be compiled with a C++	3116	Both header files and implementation files can be compiled with a C++
2693	compiler (at least, thats a stated goal, and breakage will be treated	3117	compiler (at least, that's a stated goal, and breakage will be treated
2694	as a bug).	3118	as a bug).
2695		3119
2696	You need the following files in your source tree, or in a directory	3120	You need the following files in your source tree, or in a directory
2697	in your include path (e.g. in libev/ when using -Ilibev):	3121	in your include path (e.g. in libev/ when using -Ilibev):
2698		3122
2699	ev.h	3123	ev.h
2700	ev.c	3124	ev.c
2701	ev_vars.h	3125	ev_vars.h
2702	ev_wrap.h	3126	ev_wrap.h
2703		3127
2704	ev_win32.c required on win32 platforms only	3128	ev_win32.c required on win32 platforms only
2705		3129
2706	ev_select.c only when select backend is enabled (which is enabled by default)	3130	ev_select.c only when select backend is enabled (which is enabled by default)
2707	ev_poll.c only when poll backend is enabled (disabled by default)	3131	ev_poll.c only when poll backend is enabled (disabled by default)
2708	ev_epoll.c only when the epoll backend is enabled (disabled by default)	3132	ev_epoll.c only when the epoll backend is enabled (disabled by default)
2709	ev_kqueue.c only when the kqueue backend is enabled (disabled by default)	3133	ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
2710	ev_port.c only when the solaris port backend is enabled (disabled by default)	3134	ev_port.c only when the solaris port backend is enabled (disabled by default)
2711		3135
2712	F<ev.c> includes the backend files directly when enabled, so you only need	3136	F<ev.c> includes the backend files directly when enabled, so you only need
2713	to compile this single file.	3137	to compile this single file.
2714		3138
2715	=head3 LIBEVENT COMPATIBILITY API	3139	=head3 LIBEVENT COMPATIBILITY API
2716		3140
2717	To include the libevent compatibility API, also include:	3141	To include the libevent compatibility API, also include:
2718		3142
2719	#include "event.c"	3143	#include "event.c"
2720		3144
2721	in the file including F<ev.c>, and:	3145	in the file including F<ev.c>, and:
2722		3146
2723	#include "event.h"	3147	#include "event.h"
2724		3148
2725	in the files that want to use the libevent API. This also includes F<ev.h>.	3149	in the files that want to use the libevent API. This also includes F<ev.h>.
2726		3150
2727	You need the following additional files for this:	3151	You need the following additional files for this:
2728		3152
2729	event.h	3153	event.h
2730	event.c	3154	event.c
2731		3155
2732	=head3 AUTOCONF SUPPORT	3156	=head3 AUTOCONF SUPPORT
2733		3157
2734	Instead of using C<EV_STANDALONE=1> and providing your config in	3158	Instead of using C<EV_STANDALONE=1> and providing your configuration in
2735	whatever way you want, you can also C<m4_include([libev.m4])> in your	3159	whatever way you want, you can also C<m4_include([libev.m4])> in your
2736	F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then	3160	F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then
2737	include F<config.h> and configure itself accordingly.	3161	include F<config.h> and configure itself accordingly.
2738		3162
2739	For this of course you need the m4 file:	3163	For this of course you need the m4 file:
2740		3164
2741	libev.m4	3165	libev.m4
2742		3166
2743	=head2 PREPROCESSOR SYMBOLS/MACROS	3167	=head2 PREPROCESSOR SYMBOLS/MACROS
2744		3168
2745	Libev can be configured via a variety of preprocessor symbols you have to	3169	Libev can be configured via a variety of preprocessor symbols you have to
2746	define before including any of its files. The default in the absense of	3170	define before including any of its files. The default in the absence of
2747	autoconf is noted for every option.	3171	autoconf is documented for every option.
2748		3172
2749	=over 4	3173	=over 4
2750		3174
2751	=item EV_STANDALONE	3175	=item EV_STANDALONE
2752		3176
…		…
2757	F<event.h> that are not directly supported by the libev core alone.	3181	F<event.h> that are not directly supported by the libev core alone.
2758		3182
2759	=item EV_USE_MONOTONIC	3183	=item EV_USE_MONOTONIC
2760		3184
2761	If defined to be C<1>, libev will try to detect the availability of the	3185	If defined to be C<1>, libev will try to detect the availability of the
2762	monotonic clock option at both compiletime and runtime. Otherwise no use	3186	monotonic clock option at both compile time and runtime. Otherwise no use
2763	of the monotonic clock option will be attempted. If you enable this, you	3187	of the monotonic clock option will be attempted. If you enable this, you
2764	usually have to link against librt or something similar. Enabling it when	3188	usually have to link against librt or something similar. Enabling it when
2765	the functionality isn't available is safe, though, although you have	3189	the functionality isn't available is safe, though, although you have
2766	to make sure you link against any libraries where the C<clock_gettime>	3190	to make sure you link against any libraries where the C<clock_gettime>
2767	function is hiding in (often F<-lrt>).	3191	function is hiding in (often F<-lrt>).
2768		3192
2769	=item EV_USE_REALTIME	3193	=item EV_USE_REALTIME
2770		3194
2771	If defined to be C<1>, libev will try to detect the availability of the	3195	If defined to be C<1>, libev will try to detect the availability of the
2772	realtime clock option at compiletime (and assume its availability at	3196	real-time clock option at compile time (and assume its availability at
2773	runtime if successful). Otherwise no use of the realtime clock option will	3197	runtime if successful). Otherwise no use of the real-time clock option will
2774	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	3198	be attempted. This effectively replaces C<gettimeofday> by C<clock_get
2775	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	3199	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the
2776	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	3200	note about libraries in the description of C<EV_USE_MONOTONIC>, though.
2777		3201
2778	=item EV_USE_NANOSLEEP	3202	=item EV_USE_NANOSLEEP
…		…
2789	2.7 or newer, otherwise disabled.	3213	2.7 or newer, otherwise disabled.
2790		3214
2791	=item EV_USE_SELECT	3215	=item EV_USE_SELECT
2792		3216
2793	If undefined or defined to be C<1>, libev will compile in support for the	3217	If undefined or defined to be C<1>, libev will compile in support for the
2794	C<select>(2) backend. No attempt at autodetection will be done: if no	3218	C<select>(2) backend. No attempt at auto-detection will be done: if no
2795	other method takes over, select will be it. Otherwise the select backend	3219	other method takes over, select will be it. Otherwise the select backend
2796	will not be compiled in.	3220	will not be compiled in.
2797		3221
2798	=item EV_SELECT_USE_FD_SET	3222	=item EV_SELECT_USE_FD_SET
2799		3223
2800	If defined to C<1>, then the select backend will use the system C<fd_set>	3224	If defined to C<1>, then the select backend will use the system C<fd_set>
2801	structure. This is useful if libev doesn't compile due to a missing	3225	structure. This is useful if libev doesn't compile due to a missing
2802	C<NFDBITS> or C<fd_mask> definition or it misguesses the bitset layout on	3226	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on
2803	exotic systems. This usually limits the range of file descriptors to some	3227	exotic systems. This usually limits the range of file descriptors to some
2804	low limit such as 1024 or might have other limitations (winsocket only	3228	low limit such as 1024 or might have other limitations (winsocket only
2805	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	3229	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might
2806	influence the size of the C<fd_set> used.	3230	influence the size of the C<fd_set> used.
2807		3231
…		…
2856	otherwise another method will be used as fallback. This is the preferred	3280	otherwise another method will be used as fallback. This is the preferred
2857	backend for Solaris 10 systems.	3281	backend for Solaris 10 systems.
2858		3282
2859	=item EV_USE_DEVPOLL	3283	=item EV_USE_DEVPOLL
2860		3284
2861	reserved for future expansion, works like the USE symbols above.	3285	Reserved for future expansion, works like the USE symbols above.
2862		3286
2863	=item EV_USE_INOTIFY	3287	=item EV_USE_INOTIFY
2864		3288
2865	If defined to be C<1>, libev will compile in support for the Linux inotify	3289	If defined to be C<1>, libev will compile in support for the Linux inotify
2866	interface to speed up C<ev_stat> watchers. Its actual availability will	3290	interface to speed up C<ev_stat> watchers. Its actual availability will
…		…
2873	access is atomic with respect to other threads or signal contexts. No such	3297	access is atomic with respect to other threads or signal contexts. No such
2874	type is easily found in the C language, so you can provide your own type	3298	type is easily found in the C language, so you can provide your own type
2875	that you know is safe for your purposes. It is used both for signal handler "locking"	3299	that you know is safe for your purposes. It is used both for signal handler "locking"
2876	as well as for signal and thread safety in C<ev_async> watchers.	3300	as well as for signal and thread safety in C<ev_async> watchers.
2877		3301
2878	In the absense of this define, libev will use C<sig_atomic_t volatile>	3302	In the absence of this define, libev will use C<sig_atomic_t volatile>
2879	(from F<signal.h>), which is usually good enough on most platforms.	3303	(from F<signal.h>), which is usually good enough on most platforms.
2880		3304
2881	=item EV_H	3305	=item EV_H
2882		3306
2883	The name of the F<ev.h> header file used to include it. The default if	3307	The name of the F<ev.h> header file used to include it. The default if
…		…
2922	When doing priority-based operations, libev usually has to linearly search	3346	When doing priority-based operations, libev usually has to linearly search
2923	all the priorities, so having many of them (hundreds) uses a lot of space	3347	all the priorities, so having many of them (hundreds) uses a lot of space
2924	and time, so using the defaults of five priorities (-2 .. +2) is usually	3348	and time, so using the defaults of five priorities (-2 .. +2) is usually
2925	fine.	3349	fine.
2926		3350
2927	If your embedding app does not need any priorities, defining these both to	3351	If your embedding application does not need any priorities, defining these
2928	C<0> will save some memory and cpu.	3352	both to C<0> will save some memory and CPU.
2929		3353
2930	=item EV_PERIODIC_ENABLE	3354	=item EV_PERIODIC_ENABLE
2931		3355
2932	If undefined or defined to be C<1>, then periodic timers are supported. If	3356	If undefined or defined to be C<1>, then periodic timers are supported. If
2933	defined to be C<0>, then they are not. Disabling them saves a few kB of	3357	defined to be C<0>, then they are not. Disabling them saves a few kB of
…		…
2940	code.	3364	code.
2941		3365
2942	=item EV_EMBED_ENABLE	3366	=item EV_EMBED_ENABLE
2943		3367
2944	If undefined or defined to be C<1>, then embed watchers are supported. If	3368	If undefined or defined to be C<1>, then embed watchers are supported. If
2945	defined to be C<0>, then they are not.	3369	defined to be C<0>, then they are not. Embed watchers rely on most other
		3370	watcher types, which therefore must not be disabled.
2946		3371
2947	=item EV_STAT_ENABLE	3372	=item EV_STAT_ENABLE
2948		3373
2949	If undefined or defined to be C<1>, then stat watchers are supported. If	3374	If undefined or defined to be C<1>, then stat watchers are supported. If
2950	defined to be C<0>, then they are not.	3375	defined to be C<0>, then they are not.
…		…
2960	defined to be C<0>, then they are not.	3385	defined to be C<0>, then they are not.
2961		3386
2962	=item EV_MINIMAL	3387	=item EV_MINIMAL
2963		3388
2964	If you need to shave off some kilobytes of code at the expense of some	3389	If you need to shave off some kilobytes of code at the expense of some
2965	speed, define this symbol to C<1>. Currently only used for gcc to override	3390	speed, define this symbol to C<1>. Currently this is used to override some
2966	some inlining decisions, saves roughly 30% codesize of amd64.	3391	inlining decisions, saves roughly 30% code size on amd64. It also selects a
		3392	much smaller 2-heap for timer management over the default 4-heap.
2967		3393
2968	=item EV_PID_HASHSIZE	3394	=item EV_PID_HASHSIZE
2969		3395
2970	C<ev_child> watchers use a small hash table to distribute workload by	3396	C<ev_child> watchers use a small hash table to distribute workload by
2971	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	3397	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more
…		…
2978	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	3404	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),
2979	usually more than enough. If you need to manage thousands of C<ev_stat>	3405	usually more than enough. If you need to manage thousands of C<ev_stat>
2980	watchers you might want to increase this value (I<must> be a power of	3406	watchers you might want to increase this value (I<must> be a power of
2981	two).	3407	two).
2982		3408
		3409	=item EV_USE_4HEAP
		3410
		3411	Heaps are not very cache-efficient. To improve the cache-efficiency of the
		3412	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
		3413	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
		3414	faster performance with many (thousands) of watchers.
		3415
		3416	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>
		3417	(disabled).
		3418
		3419	=item EV_HEAP_CACHE_AT
		3420
		3421	Heaps are not very cache-efficient. To improve the cache-efficiency of the
		3422	timer and periodics heaps, libev can cache the timestamp (I<at>) within
		3423	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
		3424	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
		3425	but avoids random read accesses on heap changes. This improves performance
		3426	noticeably with many (hundreds) of watchers.
		3427
		3428	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>
		3429	(disabled).
		3430
		3431	=item EV_VERIFY
		3432
		3433	Controls how much internal verification (see C<ev_loop_verify ()>) will
		3434	be done: If set to C<0>, no internal verification code will be compiled
		3435	in. If set to C<1>, then verification code will be compiled in, but not
		3436	called. If set to C<2>, then the internal verification code will be
		3437	called once per loop, which can slow down libev. If set to C<3>, then the
		3438	verification code will be called very frequently, which will slow down
		3439	libev considerably.
		3440
		3441	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be
		3442	C<0>.
		3443
2983	=item EV_COMMON	3444	=item EV_COMMON
2984		3445
2985	By default, all watchers have a C<void *data> member. By redefining	3446	By default, all watchers have a C<void *data> member. By redefining
2986	this macro to a something else you can include more and other types of	3447	this macro to a something else you can include more and other types of
2987	members. You have to define it each time you include one of the files,	3448	members. You have to define it each time you include one of the files,
2988	though, and it must be identical each time.	3449	though, and it must be identical each time.
2989		3450
2990	For example, the perl EV module uses something like this:	3451	For example, the perl EV module uses something like this:
2991		3452
2992	#define EV_COMMON \	3453	#define EV_COMMON \
2993	SV *self; /* contains this struct */ \	3454	SV *self; /* contains this struct */ \
2994	SV *cb_sv, *fh /* note no trailing ";" */	3455	SV *cb_sv, *fh /* note no trailing ";" */
2995		3456
2996	=item EV_CB_DECLARE (type)	3457	=item EV_CB_DECLARE (type)
2997		3458
2998	=item EV_CB_INVOKE (watcher, revents)	3459	=item EV_CB_INVOKE (watcher, revents)
2999		3460
…		…
3004	definition and a statement, respectively. See the F<ev.h> header file for	3465	definition and a statement, respectively. See the F<ev.h> header file for
3005	their default definitions. One possible use for overriding these is to	3466	their default definitions. One possible use for overriding these is to
3006	avoid the C<struct ev_loop *> as first argument in all cases, or to use	3467	avoid the C<struct ev_loop *> as first argument in all cases, or to use
3007	method calls instead of plain function calls in C++.	3468	method calls instead of plain function calls in C++.
3008		3469
		3470	=back
		3471
3009	=head2 EXPORTED API SYMBOLS	3472	=head2 EXPORTED API SYMBOLS
3010		3473
3011	If you need to re-export the API (e.g. via a dll) and you need a list of	3474	If you need to re-export the API (e.g. via a DLL) and you need a list of
3012	exported symbols, you can use the provided F<Symbol.*> files which list	3475	exported symbols, you can use the provided F<Symbol.*> files which list
3013	all public symbols, one per line:	3476	all public symbols, one per line:
3014		3477
3015	Symbols.ev for libev proper	3478	Symbols.ev for libev proper
3016	Symbols.event for the libevent emulation	3479	Symbols.event for the libevent emulation
3017		3480
3018	This can also be used to rename all public symbols to avoid clashes with	3481	This can also be used to rename all public symbols to avoid clashes with
3019	multiple versions of libev linked together (which is obviously bad in	3482	multiple versions of libev linked together (which is obviously bad in
3020	itself, but sometimes it is inconvinient to avoid this).	3483	itself, but sometimes it is inconvenient to avoid this).
3021		3484
3022	A sed command like this will create wrapper C<#define>'s that you need to	3485	A sed command like this will create wrapper C<#define>'s that you need to
3023	include before including F<ev.h>:	3486	include before including F<ev.h>:
3024		3487
3025	<Symbols.ev sed -e "s/.*/#define & myprefix_&/" >wrap.h	3488	<Symbols.ev sed -e "s/.*/#define & myprefix_&/" >wrap.h
…		…
3042	file.	3505	file.
3043		3506
3044	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	3507	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
3045	that everybody includes and which overrides some configure choices:	3508	that everybody includes and which overrides some configure choices:
3046		3509
3047	#define EV_MINIMAL 1	3510	#define EV_MINIMAL 1
3048	#define EV_USE_POLL 0	3511	#define EV_USE_POLL 0
3049	#define EV_MULTIPLICITY 0	3512	#define EV_MULTIPLICITY 0
3050	#define EV_PERIODIC_ENABLE 0	3513	#define EV_PERIODIC_ENABLE 0
3051	#define EV_STAT_ENABLE 0	3514	#define EV_STAT_ENABLE 0
3052	#define EV_FORK_ENABLE 0	3515	#define EV_FORK_ENABLE 0
3053	#define EV_CONFIG_H <config.h>	3516	#define EV_CONFIG_H <config.h>
3054	#define EV_MINPRI 0	3517	#define EV_MINPRI 0
3055	#define EV_MAXPRI 0	3518	#define EV_MAXPRI 0
3056		3519
3057	#include "ev++.h"	3520	#include "ev++.h"
3058		3521
3059	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	3522	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
3060		3523
3061	#include "ev_cpp.h"	3524	#include "ev_cpp.h"
3062	#include "ev.c"	3525	#include "ev.c"
3063		3526
		3527	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES
3064		3528
3065	=head1 THREADS AND COROUTINES	3529	=head2 THREADS AND COROUTINES
3066		3530
3067	=head2 THREADS	3531	=head3 THREADS
3068		3532
3069	Libev itself is completely threadsafe, but it uses no locking. This	3533	All libev functions are reentrant and thread-safe unless explicitly
		3534	documented otherwise, but libev implements no locking itself. This means
3070	means that you can use as many loops as you want in parallel, as long as	3535	that you can use as many loops as you want in parallel, as long as there
3071	only one thread ever calls into one libev function with the same loop	3536	are no concurrent calls into any libev function with the same loop
3072	parameter.	3537	parameter (C<ev_default_*> calls have an implicit default loop parameter,
		3538	of course): libev guarantees that different event loops share no data
		3539	structures that need any locking.
3073		3540
3074	Or put differently: calls with different loop parameters can be done in	3541	Or to put it differently: calls with different loop parameters can be done
3075	parallel from multiple threads, calls with the same loop parameter must be	3542	concurrently from multiple threads, calls with the same loop parameter
3076	done serially (but can be done from different threads, as long as only one	3543	must be done serially (but can be done from different threads, as long as
3077	thread ever is inside a call at any point in time, e.g. by using a mutex	3544	only one thread ever is inside a call at any point in time, e.g. by using
3078	per loop).	3545	a mutex per loop).
3079		3546
3080	If you want to know which design is best for your problem, then I cannot	3547	Specifically to support threads (and signal handlers), libev implements
		3548	so-called C<ev_async> watchers, which allow some limited form of
		3549	concurrency on the same event loop, namely waking it up "from the
		3550	outside".
		3551
		3552	If you want to know which design (one loop, locking, or multiple loops
		3553	without or something else still) is best for your problem, then I cannot
3081	help you but by giving some generic advice:	3554	help you, but here is some generic advice:
3082		3555
3083	=over 4	3556	=over 4
3084		3557
3085	=item * most applications have a main thread: use the default libev loop	3558	=item * most applications have a main thread: use the default libev loop
3086	in that thread, or create a seperate thread running only the default loop.	3559	in that thread, or create a separate thread running only the default loop.
3087		3560
3088	This helps integrating other libraries or software modules that use libev	3561	This helps integrating other libraries or software modules that use libev
3089	themselves and don't care/know about threading.	3562	themselves and don't care/know about threading.
3090		3563
3091	=item * one loop per thread is usually a good model.	3564	=item * one loop per thread is usually a good model.
3092		3565
3093	Doing this is almost never wrong, sometimes a better-performance model	3566	Doing this is almost never wrong, sometimes a better-performance model
3094	exists, but it is always a good start.	3567	exists, but it is always a good start.
3095		3568
3096	=item * other models exist, such as the leader/follower pattern, where one	3569	=item * other models exist, such as the leader/follower pattern, where one
3097	loop is handed through multiple threads in a kind of round-robbin fashion.	3570	loop is handed through multiple threads in a kind of round-robin fashion.
3098		3571
3099	Chosing a model is hard - look around, learn, know that usually you cna do	3572	Choosing a model is hard - look around, learn, know that usually you can do
3100	better than you currently do :-)	3573	better than you currently do :-)
3101		3574
3102	=item * often you need to talk to some other thread which blocks in the	3575	=item * often you need to talk to some other thread which blocks in the
		3576	event loop.
		3577
3103	event loop - C<ev_async> watchers can be used to wake them up from other	3578	C<ev_async> watchers can be used to wake them up from other threads safely
3104	threads safely (or from signal contexts...).	3579	(or from signal contexts...).
		3580
		3581	An example use would be to communicate signals or other events that only
		3582	work in the default loop by registering the signal watcher with the
		3583	default loop and triggering an C<ev_async> watcher from the default loop
		3584	watcher callback into the event loop interested in the signal.
3105		3585
3106	=back	3586	=back
3107		3587
3108	=head2 COROUTINES	3588	=head3 COROUTINES
3109		3589
3110	Libev is much more accomodating to coroutines ("cooperative threads"):	3590	Libev is very accommodating to coroutines ("cooperative threads"):
3111	libev fully supports nesting calls to it's functions from different	3591	libev fully supports nesting calls to its functions from different
3112	coroutines (e.g. you can call C<ev_loop> on the same loop from two	3592	coroutines (e.g. you can call C<ev_loop> on the same loop from two
3113	different coroutines and switch freely between both coroutines running the	3593	different coroutines, and switch freely between both coroutines running the
3114	loop, as long as you don't confuse yourself). The only exception is that	3594	loop, as long as you don't confuse yourself). The only exception is that
3115	you must not do this from C<ev_periodic> reschedule callbacks.	3595	you must not do this from C<ev_periodic> reschedule callbacks.
3116		3596
3117	Care has been invested into making sure that libev does not keep local	3597	Care has been taken to ensure that libev does not keep local state inside
3118	state inside C<ev_loop>, and other calls do not usually allow coroutine	3598	C<ev_loop>, and other calls do not usually allow for coroutine switches as
3119	switches.	3599	they do not call any callbacks.
3120		3600
		3601	=head2 COMPILER WARNINGS
3121		3602
3122	=head1 COMPLEXITIES	3603	Depending on your compiler and compiler settings, you might get no or a
		3604	lot of warnings when compiling libev code. Some people are apparently
		3605	scared by this.
3123		3606
3124	In this section the complexities of (many of) the algorithms used inside	3607	However, these are unavoidable for many reasons. For one, each compiler
3125	libev will be explained. For complexity discussions about backends see the	3608	has different warnings, and each user has different tastes regarding
3126	documentation for C<ev_default_init>.	3609	warning options. "Warn-free" code therefore cannot be a goal except when
		3610	targeting a specific compiler and compiler-version.
3127		3611
3128	All of the following are about amortised time: If an array needs to be	3612	Another reason is that some compiler warnings require elaborate
3129	extended, libev needs to realloc and move the whole array, but this	3613	workarounds, or other changes to the code that make it less clear and less
3130	happens asymptotically never with higher number of elements, so O(1) might	3614	maintainable.
3131	mean it might do a lengthy realloc operation in rare cases, but on average
3132	it is much faster and asymptotically approaches constant time.
3133		3615
3134	=over 4	3616	And of course, some compiler warnings are just plain stupid, or simply
		3617	wrong (because they don't actually warn about the condition their message
		3618	seems to warn about). For example, certain older gcc versions had some
		3619	warnings that resulted an extreme number of false positives. These have
		3620	been fixed, but some people still insist on making code warn-free with
		3621	such buggy versions.
3135		3622
3136	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)	3623	While libev is written to generate as few warnings as possible,
		3624	"warn-free" code is not a goal, and it is recommended not to build libev
		3625	with any compiler warnings enabled unless you are prepared to cope with
		3626	them (e.g. by ignoring them). Remember that warnings are just that:
		3627	warnings, not errors, or proof of bugs.
3137		3628
3138	This means that, when you have a watcher that triggers in one hour and
3139	there are 100 watchers that would trigger before that then inserting will
3140	have to skip roughly seven (C<ld 100>) of these watchers.
3141		3629
3142	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)	3630	=head2 VALGRIND
3143		3631
3144	That means that changing a timer costs less than removing/adding them	3632	Valgrind has a special section here because it is a popular tool that is
3145	as only the relative motion in the event queue has to be paid for.	3633	highly useful. Unfortunately, valgrind reports are very hard to interpret.
3146		3634
3147	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)	3635	If you think you found a bug (memory leak, uninitialised data access etc.)
		3636	in libev, then check twice: If valgrind reports something like:
3148		3637
3149	These just add the watcher into an array or at the head of a list.	3638	==2274== definitely lost: 0 bytes in 0 blocks.
		3639	==2274== possibly lost: 0 bytes in 0 blocks.
		3640	==2274== still reachable: 256 bytes in 1 blocks.
3150		3641
3151	=item Stopping check/prepare/idle/fork/async watchers: O(1)	3642	Then there is no memory leak, just as memory accounted to global variables
		3643	is not a memleak - the memory is still being referenced, and didn't leak.
3152		3644
3153	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))	3645	Similarly, under some circumstances, valgrind might report kernel bugs
		3646	as if it were a bug in libev (e.g. in realloc or in the poll backend,
		3647	although an acceptable workaround has been found here), or it might be
		3648	confused.
3154		3649
3155	These watchers are stored in lists then need to be walked to find the	3650	Keep in mind that valgrind is a very good tool, but only a tool. Don't
3156	correct watcher to remove. The lists are usually short (you don't usually	3651	make it into some kind of religion.
3157	have many watchers waiting for the same fd or signal).
3158		3652
3159	=item Finding the next timer in each loop iteration: O(1)	3653	If you are unsure about something, feel free to contact the mailing list
		3654	with the full valgrind report and an explanation on why you think this
		3655	is a bug in libev (best check the archives, too :). However, don't be
		3656	annoyed when you get a brisk "this is no bug" answer and take the chance
		3657	of learning how to interpret valgrind properly.
3160		3658
3161	By virtue of using a binary heap, the next timer is always found at the	3659	If you need, for some reason, empty reports from valgrind for your project
3162	beginning of the storage array.	3660	I suggest using suppression lists.
3163		3661
3164	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
3165		3662
3166	A change means an I/O watcher gets started or stopped, which requires	3663	=head1 PORTABILITY NOTES
3167	libev to recalculate its status (and possibly tell the kernel, depending
3168	on backend and wether C<ev_io_set> was used).
3169		3664
3170	=item Activating one watcher (putting it into the pending state): O(1)	3665	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
3171
3172	=item Priority handling: O(number_of_priorities)
3173
3174	Priorities are implemented by allocating some space for each
3175	priority. When doing priority-based operations, libev usually has to
3176	linearly search all the priorities, but starting/stopping and activating
3177	watchers becomes O(1) w.r.t. priority handling.
3178
3179	=item Sending an ev_async: O(1)
3180
3181	=item Processing ev_async_send: O(number_of_async_watchers)
3182
3183	=item Processing signals: O(max_signal_number)
3184
3185	Sending involves a syscall I<iff> there were no other C<ev_async_send>
3186	calls in the current loop iteration. Checking for async and signal events
3187	involves iterating over all running async watchers or all signal numbers.
3188
3189	=back
3190
3191
3192	=head1 Win32 platform limitations and workarounds
3193		3666
3194	Win32 doesn't support any of the standards (e.g. POSIX) that libev	3667	Win32 doesn't support any of the standards (e.g. POSIX) that libev
3195	requires, and its I/O model is fundamentally incompatible with the POSIX	3668	requires, and its I/O model is fundamentally incompatible with the POSIX
3196	model. Libev still offers limited functionality on this platform in	3669	model. Libev still offers limited functionality on this platform in
3197	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	3670	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
3198	descriptors. This only applies when using Win32 natively, not when using	3671	descriptors. This only applies when using Win32 natively, not when using
3199	e.g. cygwin.	3672	e.g. cygwin.
3200		3673
		3674	Lifting these limitations would basically require the full
		3675	re-implementation of the I/O system. If you are into these kinds of
		3676	things, then note that glib does exactly that for you in a very portable
		3677	way (note also that glib is the slowest event library known to man).
		3678
3201	There is no supported compilation method available on windows except	3679	There is no supported compilation method available on windows except
3202	embedding it into other applications.	3680	embedding it into other applications.
3203		3681
		3682	Not a libev limitation but worth mentioning: windows apparently doesn't
		3683	accept large writes: instead of resulting in a partial write, windows will
		3684	either accept everything or return C<ENOBUFS> if the buffer is too large,
		3685	so make sure you only write small amounts into your sockets (less than a
		3686	megabyte seems safe, but this apparently depends on the amount of memory
		3687	available).
		3688
3204	Due to the many, low, and arbitrary limits on the win32 platform and the	3689	Due to the many, low, and arbitrary limits on the win32 platform and
3205	abysmal performance of winsockets, using a large number of sockets is not	3690	the abysmal performance of winsockets, using a large number of sockets
3206	recommended (and not reasonable). If your program needs to use more than	3691	is not recommended (and not reasonable). If your program needs to use
3207	a hundred or so sockets, then likely it needs to use a totally different	3692	more than a hundred or so sockets, then likely it needs to use a totally
3208	implementation for windows, as libev offers the POSIX model, which cannot	3693	different implementation for windows, as libev offers the POSIX readiness
3209	be implemented efficiently on windows (microsoft monopoly games).	3694	notification model, which cannot be implemented efficiently on windows
		3695	(Microsoft monopoly games).
		3696
		3697	A typical way to use libev under windows is to embed it (see the embedding
		3698	section for details) and use the following F<evwrap.h> header file instead
		3699	of F<ev.h>:
		3700
		3701	#define EV_STANDALONE /* keeps ev from requiring config.h */
		3702	#define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */
		3703
		3704	#include "ev.h"
		3705
		3706	And compile the following F<evwrap.c> file into your project (make sure
		3707	you do I<not> compile the F<ev.c> or any other embedded source files!):
		3708
		3709	#include "evwrap.h"
		3710	#include "ev.c"
3210		3711
3211	=over 4	3712	=over 4
3212		3713
3213	=item The winsocket select function	3714	=item The winsocket select function
3214		3715
3215	The winsocket C<select> function doesn't follow POSIX in that it requires	3716	The winsocket C<select> function doesn't follow POSIX in that it
3216	socket I<handles> and not socket I<file descriptors>. This makes select	3717	requires socket I<handles> and not socket I<file descriptors> (it is
3217	very inefficient, and also requires a mapping from file descriptors	3718	also extremely buggy). This makes select very inefficient, and also
3218	to socket handles. See the discussion of the C<EV_SELECT_USE_FD_SET>,	3719	requires a mapping from file descriptors to socket handles (the Microsoft
3219	C<EV_SELECT_IS_WINSOCKET> and C<EV_FD_TO_WIN32_HANDLE> preprocessor	3720	C runtime provides the function C<_open_osfhandle> for this). See the
3220	symbols for more info.	3721	discussion of the C<EV_SELECT_USE_FD_SET>, C<EV_SELECT_IS_WINSOCKET> and
		3722	C<EV_FD_TO_WIN32_HANDLE> preprocessor symbols for more info.
3221		3723
3222	The configuration for a "naked" win32 using the microsoft runtime	3724	The configuration for a "naked" win32 using the Microsoft runtime
3223	libraries and raw winsocket select is:	3725	libraries and raw winsocket select is:
3224		3726
3225	#define EV_USE_SELECT 1	3727	#define EV_USE_SELECT 1
3226	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */	3728	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
3227		3729
3228	Note that winsockets handling of fd sets is O(n), so you can easily get a	3730	Note that winsockets handling of fd sets is O(n), so you can easily get a
3229	complexity in the O(n²) range when using win32.	3731	complexity in the O(n²) range when using win32.
3230		3732
3231	=item Limited number of file descriptors	3733	=item Limited number of file descriptors
3232		3734
3233	Windows has numerous arbitrary (and low) limits on things. Early versions	3735	Windows has numerous arbitrary (and low) limits on things.
3234	of winsocket's select only supported waiting for a max. of C<64> handles	3736
		3737	Early versions of winsocket's select only supported waiting for a maximum
3235	(probably owning to the fact that all windows kernels can only wait for	3738	of C<64> handles (probably owning to the fact that all windows kernels
3236	C<64> things at the same time internally; microsoft recommends spawning a	3739	can only wait for C<64> things at the same time internally; Microsoft
3237	chain of threads and wait for 63 handles and the previous thread in each).	3740	recommends spawning a chain of threads and wait for 63 handles and the
		3741	previous thread in each. Great).
3238		3742
3239	Newer versions support more handles, but you need to define C<FD_SETSIZE>	3743	Newer versions support more handles, but you need to define C<FD_SETSIZE>
3240	to some high number (e.g. C<2048>) before compiling the winsocket select	3744	to some high number (e.g. C<2048>) before compiling the winsocket select
3241	call (which might be in libev or elsewhere, for example, perl does its own	3745	call (which might be in libev or elsewhere, for example, perl does its own
3242	select emulation on windows).	3746	select emulation on windows).
3243		3747
3244	Another limit is the number of file descriptors in the microsoft runtime	3748	Another limit is the number of file descriptors in the Microsoft runtime
3245	libraries, which by default is C<64> (there must be a hidden I<64> fetish	3749	libraries, which by default is C<64> (there must be a hidden I<64> fetish
3246	or something like this inside microsoft). You can increase this by calling	3750	or something like this inside Microsoft). You can increase this by calling
3247	C<_setmaxstdio>, which can increase this limit to C<2048> (another	3751	C<_setmaxstdio>, which can increase this limit to C<2048> (another
3248	arbitrary limit), but is broken in many versions of the microsoft runtime	3752	arbitrary limit), but is broken in many versions of the Microsoft runtime
3249	libraries.	3753	libraries.
3250		3754
3251	This might get you to about C<512> or C<2048> sockets (depending on	3755	This might get you to about C<512> or C<2048> sockets (depending on
3252	windows version and/or the phase of the moon). To get more, you need to	3756	windows version and/or the phase of the moon). To get more, you need to
3253	wrap all I/O functions and provide your own fd management, but the cost of	3757	wrap all I/O functions and provide your own fd management, but the cost of
3254	calling select (O(n²)) will likely make this unworkable.	3758	calling select (O(n²)) will likely make this unworkable.
3255		3759
3256	=back	3760	=back
3257		3761
		3762	=head2 PORTABILITY REQUIREMENTS
		3763
		3764	In addition to a working ISO-C implementation and of course the
		3765	backend-specific APIs, libev relies on a few additional extensions:
		3766
		3767	=over 4
		3768
		3769	=item C<void (*)(ev_watcher_type *, int revents)> must have compatible
		3770	calling conventions regardless of C<ev_watcher_type *>.
		3771
		3772	Libev assumes not only that all watcher pointers have the same internal
		3773	structure (guaranteed by POSIX but not by ISO C for example), but it also
		3774	assumes that the same (machine) code can be used to call any watcher
		3775	callback: The watcher callbacks have different type signatures, but libev
		3776	calls them using an C<ev_watcher *> internally.
		3777
		3778	=item C<sig_atomic_t volatile> must be thread-atomic as well
		3779
		3780	The type C<sig_atomic_t volatile> (or whatever is defined as
		3781	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
		3782	threads. This is not part of the specification for C<sig_atomic_t>, but is
		3783	believed to be sufficiently portable.
		3784
		3785	=item C<sigprocmask> must work in a threaded environment
		3786
		3787	Libev uses C<sigprocmask> to temporarily block signals. This is not
		3788	allowed in a threaded program (C<pthread_sigmask> has to be used). Typical
		3789	pthread implementations will either allow C<sigprocmask> in the "main
		3790	thread" or will block signals process-wide, both behaviours would
		3791	be compatible with libev. Interaction between C<sigprocmask> and
		3792	C<pthread_sigmask> could complicate things, however.
		3793
		3794	The most portable way to handle signals is to block signals in all threads
		3795	except the initial one, and run the default loop in the initial thread as
		3796	well.
		3797
		3798	=item C<long> must be large enough for common memory allocation sizes
		3799
		3800	To improve portability and simplify its API, libev uses C<long> internally
		3801	instead of C<size_t> when allocating its data structures. On non-POSIX
		3802	systems (Microsoft...) this might be unexpectedly low, but is still at
		3803	least 31 bits everywhere, which is enough for hundreds of millions of
		3804	watchers.
		3805
		3806	=item C<double> must hold a time value in seconds with enough accuracy
		3807
		3808	The type C<double> is used to represent timestamps. It is required to
		3809	have at least 51 bits of mantissa (and 9 bits of exponent), which is good
		3810	enough for at least into the year 4000. This requirement is fulfilled by
		3811	implementations implementing IEEE 754 (basically all existing ones).
		3812
		3813	=back
		3814
		3815	If you know of other additional requirements drop me a note.
		3816
		3817
		3818	=head1 ALGORITHMIC COMPLEXITIES
		3819
		3820	In this section the complexities of (many of) the algorithms used inside
		3821	libev will be documented. For complexity discussions about backends see
		3822	the documentation for C<ev_default_init>.
		3823
		3824	All of the following are about amortised time: If an array needs to be
		3825	extended, libev needs to realloc and move the whole array, but this
		3826	happens asymptotically rarer with higher number of elements, so O(1) might
		3827	mean that libev does a lengthy realloc operation in rare cases, but on
		3828	average it is much faster and asymptotically approaches constant time.
		3829
		3830	=over 4
		3831
		3832	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)
		3833
		3834	This means that, when you have a watcher that triggers in one hour and
		3835	there are 100 watchers that would trigger before that, then inserting will
		3836	have to skip roughly seven (C<ld 100>) of these watchers.
		3837
		3838	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)
		3839
		3840	That means that changing a timer costs less than removing/adding them,
		3841	as only the relative motion in the event queue has to be paid for.
		3842
		3843	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
		3844
		3845	These just add the watcher into an array or at the head of a list.
		3846
		3847	=item Stopping check/prepare/idle/fork/async watchers: O(1)
		3848
		3849	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
		3850
		3851	These watchers are stored in lists, so they need to be walked to find the
		3852	correct watcher to remove. The lists are usually short (you don't usually
		3853	have many watchers waiting for the same fd or signal: one is typical, two
		3854	is rare).
		3855
		3856	=item Finding the next timer in each loop iteration: O(1)
		3857
		3858	By virtue of using a binary or 4-heap, the next timer is always found at a
		3859	fixed position in the storage array.
		3860
		3861	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
		3862
		3863	A change means an I/O watcher gets started or stopped, which requires
		3864	libev to recalculate its status (and possibly tell the kernel, depending
		3865	on backend and whether C<ev_io_set> was used).
		3866
		3867	=item Activating one watcher (putting it into the pending state): O(1)
		3868
		3869	=item Priority handling: O(number_of_priorities)
		3870
		3871	Priorities are implemented by allocating some space for each
		3872	priority. When doing priority-based operations, libev usually has to
		3873	linearly search all the priorities, but starting/stopping and activating
		3874	watchers becomes O(1) with respect to priority handling.
		3875
		3876	=item Sending an ev_async: O(1)
		3877
		3878	=item Processing ev_async_send: O(number_of_async_watchers)
		3879
		3880	=item Processing signals: O(max_signal_number)
		3881
		3882	Sending involves a system call I<iff> there were no other C<ev_async_send>
		3883	calls in the current loop iteration. Checking for async and signal events
		3884	involves iterating over all running async watchers or all signal numbers.
		3885
		3886	=back
		3887
3258		3888
3259	=head1 AUTHOR	3889	=head1 AUTHOR
3260		3890
3261	Marc Lehmann <libev@schmorp.de>.	3891	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.
3262		3892

Diff Legend

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