ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

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

Diff Legend

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