ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.171 by root, Tue Jul 8 09:49:15 2008 UTC vs.
Revision 1.286 by root, Tue Mar 16 00:26:41 2010 UTC

…		…
9	=head2 EXAMPLE PROGRAM	9	=head2 EXAMPLE PROGRAM
10		10
11	// a single header file is required	11	// a single header file is required
12	#include <ev.h>	12	#include <ev.h>
13		13
		14	#include <stdio.h> // for puts
		15
14	// every watcher type has its own typedef'd struct	16	// every watcher type has its own typedef'd struct
15	// with the name ev_<type>	17	// with the name ev_TYPE
16	ev_io stdin_watcher;	18	ev_io stdin_watcher;
17	ev_timer timeout_watcher;	19	ev_timer timeout_watcher;
18		20
19	// all watcher callbacks have a similar signature	21	// all watcher callbacks have a similar signature
20	// this callback is called when data is readable on stdin	22	// this callback is called when data is readable on stdin
21	static void	23	static void
22	stdin_cb (EV_P_ struct ev_io *w, int revents)	24	stdin_cb (EV_P_ ev_io *w, int revents)
23	{	25	{
24	puts ("stdin ready");	26	puts ("stdin ready");
25	// for one-shot events, one must manually stop the watcher	27	// for one-shot events, one must manually stop the watcher
26	// with its corresponding stop function.	28	// with its corresponding stop function.
27	ev_io_stop (EV_A_ w);	29	ev_io_stop (EV_A_ w);
…		…
30	ev_unloop (EV_A_ EVUNLOOP_ALL);	32	ev_unloop (EV_A_ EVUNLOOP_ALL);
31	}	33	}
32		34
33	// another callback, this time for a time-out	35	// another callback, this time for a time-out
34	static void	36	static void
35	timeout_cb (EV_P_ struct ev_timer *w, int revents)	37	timeout_cb (EV_P_ ev_timer *w, int revents)
36	{	38	{
37	puts ("timeout");	39	puts ("timeout");
38	// this causes the innermost ev_loop to stop iterating	40	// this causes the innermost ev_loop to stop iterating
39	ev_unloop (EV_A_ EVUNLOOP_ONE);	41	ev_unloop (EV_A_ EVUNLOOP_ONE);
40	}	42	}
…		…
60		62
61	// unloop was called, so exit	63	// unloop was called, so exit
62	return 0;	64	return 0;
63	}	65	}
64		66
65	=head1 DESCRIPTION	67	=head1 ABOUT THIS DOCUMENT
		68
		69	This document documents the libev software package.
66		70
67	The newest version of this document is also available as an html-formatted	71	The newest version of this document is also available as an html-formatted
68	web page you might find easier to navigate when reading it for the first	72	web page you might find easier to navigate when reading it for the first
69	time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>.	73	time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>.
		74
		75	While this document tries to be as complete as possible in documenting
		76	libev, its usage and the rationale behind its design, it is not a tutorial
		77	on event-based programming, nor will it introduce event-based programming
		78	with libev.
		79
		80	Familarity with event based programming techniques in general is assumed
		81	throughout this document.
		82
		83	=head1 ABOUT LIBEV
70		84
71	Libev is an event loop: you register interest in certain events (such as a	85	Libev is an event loop: you register interest in certain events (such as a
72	file descriptor being readable or a timeout occurring), and it will manage	86	file descriptor being readable or a timeout occurring), and it will manage
73	these event sources and provide your program with events.	87	these event sources and provide your program with events.
74		88
…		…
84	=head2 FEATURES	98	=head2 FEATURES
85		99
86	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the	100	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
87	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms	101	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
88	for file descriptor events (C<ev_io>), the Linux C<inotify> interface	102	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
89	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers	103	(for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner
90	with customised rescheduling (C<ev_periodic>), synchronous signals	104	inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative
91	(C<ev_signal>), process status change events (C<ev_child>), and event	105	timers (C<ev_timer>), absolute timers with customised rescheduling
92	watchers dealing with the event loop mechanism itself (C<ev_idle>,	106	(C<ev_periodic>), synchronous signals (C<ev_signal>), process status
93	C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as	107	change events (C<ev_child>), and event watchers dealing with the event
94	file watchers (C<ev_stat>) and even limited support for fork events	108	loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and
95	(C<ev_fork>).	109	C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even
		110	limited support for fork events (C<ev_fork>).
96		111
97	It also is quite fast (see this	112	It also is quite fast (see this
98	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent	113	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent
99	for example).	114	for example).
100		115
…		…
108	name C<loop> (which is always of type C<struct ev_loop *>) will not have	123	name C<loop> (which is always of type C<struct ev_loop *>) will not have
109	this argument.	124	this argument.
110		125
111	=head2 TIME REPRESENTATION	126	=head2 TIME REPRESENTATION
112		127
113	Libev represents time as a single floating point number, representing the	128	Libev represents time as a single floating point number, representing
114	(fractional) number of seconds since the (POSIX) epoch (somewhere near	129	the (fractional) number of seconds since the (POSIX) epoch (somewhere
115	the beginning of 1970, details are complicated, don't ask). This type is	130	near the beginning of 1970, details are complicated, don't ask). This
116	called C<ev_tstamp>, which is what you should use too. It usually aliases	131	type is called C<ev_tstamp>, which is what you should use too. It usually
117	to the C<double> type in C, and when you need to do any calculations on	132	aliases to the C<double> type in C. When you need to do any calculations
118	it, you should treat it as some floating point value. Unlike the name	133	on it, you should treat it as some floating point value. Unlike the name
119	component C<stamp> might indicate, it is also used for time differences	134	component C<stamp> might indicate, it is also used for time differences
120	throughout libev.	135	throughout libev.
121		136
122	=head1 ERROR HANDLING	137	=head1 ERROR HANDLING
123		138
…		…
214	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	229	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for
215	recommended ones.	230	recommended ones.
216		231
217	See the description of C<ev_embed> watchers for more info.	232	See the description of C<ev_embed> watchers for more info.
218		233
219	=item ev_set_allocator (void *(*cb)(void *ptr, long size))	234	=item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]
220		235
221	Sets the allocation function to use (the prototype is similar - the	236	Sets the allocation function to use (the prototype is similar - the
222	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is	237	semantics are identical to the C<realloc> C89/SuS/POSIX function). It is
223	used to allocate and free memory (no surprises here). If it returns zero	238	used to allocate and free memory (no surprises here). If it returns zero
224	when memory needs to be allocated (C<size != 0>), the library might abort	239	when memory needs to be allocated (C<size != 0>), the library might abort
…		…
250	}	265	}
251		266
252	...	267	...
253	ev_set_allocator (persistent_realloc);	268	ev_set_allocator (persistent_realloc);
254		269
255	=item ev_set_syserr_cb (void (*cb)(const char *msg));	270	=item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]
256		271
257	Set the callback function to call on a retryable system call error (such	272	Set the callback function to call on a retryable system call error (such
258	as failed select, poll, epoll_wait). The message is a printable string	273	as failed select, poll, epoll_wait). The message is a printable string
259	indicating the system call or subsystem causing the problem. If this	274	indicating the system call or subsystem causing the problem. If this
260	callback is set, then libev will expect it to remedy the situation, no	275	callback is set, then libev will expect it to remedy the situation, no
…		…
276		291
277	=back	292	=back
278		293
279	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	294	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP
280		295
281	An event loop is described by a C<struct ev_loop *>. The library knows two	296	An event loop is described by a C<struct ev_loop *> (the C<struct>
282	types of such loops, the I<default> loop, which supports signals and child	297	is I<not> optional in this case, as there is also an C<ev_loop>
283	events, and dynamically created loops which do not.	298	I<function>).
		299
		300	The library knows two types of such loops, the I<default> loop, which
		301	supports signals and child events, and dynamically created loops which do
		302	not.
284		303
285	=over 4	304	=over 4
286		305
287	=item struct ev_loop *ev_default_loop (unsigned int flags)	306	=item struct ev_loop *ev_default_loop (unsigned int flags)
288		307
…		…
294	If you don't know what event loop to use, use the one returned from this	313	If you don't know what event loop to use, use the one returned from this
295	function.	314	function.
296		315
297	Note that this function is I<not> thread-safe, so if you want to use it	316	Note that this function is I<not> thread-safe, so if you want to use it
298	from multiple threads, you have to lock (note also that this is unlikely,	317	from multiple threads, you have to lock (note also that this is unlikely,
299	as loops cannot bes hared easily between threads anyway).	318	as loops cannot be shared easily between threads anyway).
300		319
301	The default loop is the only loop that can handle C<ev_signal> and	320	The default loop is the only loop that can handle C<ev_signal> and
302	C<ev_child> watchers, and to do this, it always registers a handler	321	C<ev_child> watchers, and to do this, it always registers a handler
303	for C<SIGCHLD>. If this is a problem for your application you can either	322	for C<SIGCHLD>. If this is a problem for your application you can either
304	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	323	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
…		…
344	flag.	363	flag.
345		364
346	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>	365	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
347	environment variable.	366	environment variable.
348		367
		368	=item C<EVFLAG_NOINOTIFY>
		369
		370	When this flag is specified, then libev will not attempt to use the
		371	I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and
		372	testing, this flag can be useful to conserve inotify file descriptors, as
		373	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
		374
		375	=item C<EVFLAG_SIGNALFD>
		376
		377	When this flag is specified, then libev will attempt to use the
		378	I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API
		379	delivers signals synchronously, which makes it both faster and might make
		380	it possible to get the queued signal data. It can also simplify signal
		381	handling with threads, as long as you properly block signals in your
		382	threads that are not interested in handling them.
		383
		384	Signalfd will not be used by default as this changes your signal mask, and
		385	there are a lot of shoddy libraries and programs (glib's threadpool for
		386	example) that can't properly initialise their signal masks.
		387
349	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	388	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
350		389
351	This is your standard select(2) backend. Not I<completely> standard, as	390	This is your standard select(2) backend. Not I<completely> standard, as
352	libev tries to roll its own fd_set with no limits on the number of fds,	391	libev tries to roll its own fd_set with no limits on the number of fds,
353	but if that fails, expect a fairly low limit on the number of fds when	392	but if that fails, expect a fairly low limit on the number of fds when
…		…
359	writing a server, you should C<accept ()> in a loop to accept as many	398	writing a server, you should C<accept ()> in a loop to accept as many
360	connections as possible during one iteration. You might also want to have	399	connections as possible during one iteration. You might also want to have
361	a look at C<ev_set_io_collect_interval ()> to increase the amount of	400	a look at C<ev_set_io_collect_interval ()> to increase the amount of
362	readiness notifications you get per iteration.	401	readiness notifications you get per iteration.
363		402
		403	This backend maps C<EV_READ> to the C<readfds> set and C<EV_WRITE> to the
		404	C<writefds> set (and to work around Microsoft Windows bugs, also onto the
		405	C<exceptfds> set on that platform).
		406
364	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)	407	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
365		408
366	And this is your standard poll(2) backend. It's more complicated	409	And this is your standard poll(2) backend. It's more complicated
367	than select, but handles sparse fds better and has no artificial	410	than select, but handles sparse fds better and has no artificial
368	limit on the number of fds you can use (except it will slow down	411	limit on the number of fds you can use (except it will slow down
369	considerably with a lot of inactive fds). It scales similarly to select,	412	considerably with a lot of inactive fds). It scales similarly to select,
370	i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for	413	i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for
371	performance tips.	414	performance tips.
372		415
		416	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and
		417	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.
		418
373	=item C<EVBACKEND_EPOLL> (value 4, Linux)	419	=item C<EVBACKEND_EPOLL> (value 4, Linux)
		420
		421	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
		422	kernels).
374		423
375	For few fds, this backend is a bit little slower than poll and select,	424	For few fds, this backend is a bit little slower than poll and select,
376	but it scales phenomenally better. While poll and select usually scale	425	but it scales phenomenally better. While poll and select usually scale
377	like O(total_fds) where n is the total number of fds (or the highest fd),	426	like O(total_fds) where n is the total number of fds (or the highest fd),
378	epoll scales either O(1) or O(active_fds). The epoll design has a number	427	epoll scales either O(1) or O(active_fds).
379	of shortcomings, such as silently dropping events in some hard-to-detect	428
380	cases and requiring a system call per fd change, no fork support and bad	429	The epoll mechanism deserves honorable mention as the most misdesigned
381	support for dup.	430	of the more advanced event mechanisms: mere annoyances include silently
		431	dropping file descriptors, requiring a system call per change per file
		432	descriptor (and unnecessary guessing of parameters), problems with dup and
		433	so on. The biggest issue is fork races, however - if a program forks then
		434	I<both> parent and child process have to recreate the epoll set, which can
		435	take considerable time (one syscall per file descriptor) and is of course
		436	hard to detect.
		437
		438	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
		439	of course I<doesn't>, and epoll just loves to report events for totally
		440	I<different> file descriptors (even already closed ones, so one cannot
		441	even remove them from the set) than registered in the set (especially
		442	on SMP systems). Libev tries to counter these spurious notifications by
		443	employing an additional generation counter and comparing that against the
		444	events to filter out spurious ones, recreating the set when required.
382		445
383	While stopping, setting and starting an I/O watcher in the same iteration	446	While stopping, setting and starting an I/O watcher in the same iteration
384	will result in some caching, there is still a system call per such incident	447	will result in some caching, there is still a system call per such
385	(because the fd could point to a different file description now), so its	448	incident (because the same I<file descriptor> could point to a different
386	best to avoid that. Also, C<dup ()>'ed file descriptors might not work	449	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
387	very well if you register events for both fds.	450	file descriptors might not work very well if you register events for both
388		451	file descriptors.
389	Please note that epoll sometimes generates spurious notifications, so you
390	need to use non-blocking I/O or other means to avoid blocking when no data
391	(or space) is available.
392		452
393	Best performance from this backend is achieved by not unregistering all	453	Best performance from this backend is achieved by not unregistering all
394	watchers for a file descriptor until it has been closed, if possible, i.e.	454	watchers for a file descriptor until it has been closed, if possible,
395	keep at least one watcher active per fd at all times.	455	i.e. keep at least one watcher active per fd at all times. Stopping and
		456	starting a watcher (without re-setting it) also usually doesn't cause
		457	extra overhead. A fork can both result in spurious notifications as well
		458	as in libev having to destroy and recreate the epoll object, which can
		459	take considerable time and thus should be avoided.
		460
		461	All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or
		462	faster than epoll for maybe up to a hundred file descriptors, depending on
		463	the usage. So sad.
396		464
397	While nominally embeddable in other event loops, this feature is broken in	465	While nominally embeddable in other event loops, this feature is broken in
398	all kernel versions tested so far.	466	all kernel versions tested so far.
		467
		468	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		469	C<EVBACKEND_POLL>.
399		470
400	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	471	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
401		472
402	Kqueue deserves special mention, as at the time of this writing, it	473	Kqueue deserves special mention, as at the time of this writing, it
403	was broken on all BSDs except NetBSD (usually it doesn't work reliably	474	was broken on all BSDs except NetBSD (usually it doesn't work reliably
404	with anything but sockets and pipes, except on Darwin, where of course	475	with anything but sockets and pipes, except on Darwin, where of course
405	it's completely useless). For this reason it's not being "auto-detected"	476	it's completely useless). Unlike epoll, however, whose brokenness
		477	is by design, these kqueue bugs can (and eventually will) be fixed
		478	without API changes to existing programs. For this reason it's not being
406	unless you explicitly specify it explicitly in the flags (i.e. using	479	"auto-detected" unless you explicitly specify it in the flags (i.e. using
407	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)	480	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
408	system like NetBSD.	481	system like NetBSD.
409		482
410	You still can embed kqueue into a normal poll or select backend and use it	483	You still can embed kqueue into a normal poll or select backend and use it
411	only for sockets (after having made sure that sockets work with kqueue on	484	only for sockets (after having made sure that sockets work with kqueue on
…		…
413		486
414	It scales in the same way as the epoll backend, but the interface to the	487	It scales in the same way as the epoll backend, but the interface to the
415	kernel is more efficient (which says nothing about its actual speed, of	488	kernel is more efficient (which says nothing about its actual speed, of
416	course). While stopping, setting and starting an I/O watcher does never	489	course). While stopping, setting and starting an I/O watcher does never
417	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to	490	cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to
418	two event changes per incident, support for C<fork ()> is very bad and it	491	two event changes per incident. Support for C<fork ()> is very bad (but
419	drops fds silently in similarly hard-to-detect cases.	492	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect
		493	cases
420		494
421	This backend usually performs well under most conditions.	495	This backend usually performs well under most conditions.
422		496
423	While nominally embeddable in other event loops, this doesn't work	497	While nominally embeddable in other event loops, this doesn't work
424	everywhere, so you might need to test for this. And since it is broken	498	everywhere, so you might need to test for this. And since it is broken
425	almost everywhere, you should only use it when you have a lot of sockets	499	almost everywhere, you should only use it when you have a lot of sockets
426	(for which it usually works), by embedding it into another event loop	500	(for which it usually works), by embedding it into another event loop
427	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and using it only for	501	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course
428	sockets.	502	also broken on OS X)) and, did I mention it, using it only for sockets.
		503
		504	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with
		505	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with
		506	C<NOTE_EOF>.
429		507
430	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)	508	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
431		509
432	This is not implemented yet (and might never be, unless you send me an	510	This is not implemented yet (and might never be, unless you send me an
433	implementation). According to reports, C</dev/poll> only supports sockets	511	implementation). According to reports, C</dev/poll> only supports sockets
…		…
446	While this backend scales well, it requires one system call per active	524	While this backend scales well, it requires one system call per active
447	file descriptor per loop iteration. For small and medium numbers of file	525	file descriptor per loop iteration. For small and medium numbers of file
448	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	526	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
449	might perform better.	527	might perform better.
450		528
451	On the positive side, ignoring the spurious readiness notifications, this	529	On the positive side, with the exception of the spurious readiness
452	backend actually performed to specification in all tests and is fully	530	notifications, this backend actually performed fully to specification
453	embeddable, which is a rare feat among the OS-specific backends.	531	in all tests and is fully embeddable, which is a rare feat among the
		532	OS-specific backends (I vastly prefer correctness over speed hacks).
		533
		534	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		535	C<EVBACKEND_POLL>.
454		536
455	=item C<EVBACKEND_ALL>	537	=item C<EVBACKEND_ALL>
456		538
457	Try all backends (even potentially broken ones that wouldn't be tried	539	Try all backends (even potentially broken ones that wouldn't be tried
458	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as	540	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
…		…
460		542
461	It is definitely not recommended to use this flag.	543	It is definitely not recommended to use this flag.
462		544
463	=back	545	=back
464		546
465	If one or more of these are or'ed into the flags value, then only these	547	If one or more of the backend flags are or'ed into the flags value,
466	backends will be tried (in the reverse order as listed here). If none are	548	then only these backends will be tried (in the reverse order as listed
467	specified, all backends in C<ev_recommended_backends ()> will be tried.	549	here). If none are specified, all backends in C<ev_recommended_backends
		550	()> will be tried.
468		551
469	The most typical usage is like this:	552	Example: This is the most typical usage.
470		553
471	if (!ev_default_loop (0))	554	if (!ev_default_loop (0))
472	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");	555	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
473		556
474	Restrict libev to the select and poll backends, and do not allow	557	Example: Restrict libev to the select and poll backends, and do not allow
475	environment settings to be taken into account:	558	environment settings to be taken into account:
476		559
477	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);	560	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
478		561
479	Use whatever libev has to offer, but make sure that kqueue is used if	562	Example: Use whatever libev has to offer, but make sure that kqueue is
480	available (warning, breaks stuff, best use only with your own private	563	used if available (warning, breaks stuff, best use only with your own
481	event loop and only if you know the OS supports your types of fds):	564	private event loop and only if you know the OS supports your types of
		565	fds):
482		566
483	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);	567	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
484		568
485	=item struct ev_loop *ev_loop_new (unsigned int flags)	569	=item struct ev_loop *ev_loop_new (unsigned int flags)
486		570
…		…
507	responsibility to either stop all watchers cleanly yourself I<before>	591	responsibility to either stop all watchers cleanly yourself I<before>
508	calling this function, or cope with the fact afterwards (which is usually	592	calling this function, or cope with the fact afterwards (which is usually
509	the easiest thing, you can just ignore the watchers and/or C<free ()> them	593	the easiest thing, you can just ignore the watchers and/or C<free ()> them
510	for example).	594	for example).
511		595
512	Note that certain global state, such as signal state, will not be freed by	596	Note that certain global state, such as signal state (and installed signal
513	this function, and related watchers (such as signal and child watchers)	597	handlers), will not be freed by this function, and related watchers (such
514	would need to be stopped manually.	598	as signal and child watchers) would need to be stopped manually.
515		599
516	In general it is not advisable to call this function except in the	600	In general it is not advisable to call this function except in the
517	rare occasion where you really need to free e.g. the signal handling	601	rare occasion where you really need to free e.g. the signal handling
518	pipe fds. If you need dynamically allocated loops it is better to use	602	pipe fds. If you need dynamically allocated loops it is better to use
519	C<ev_loop_new> and C<ev_loop_destroy>).	603	C<ev_loop_new> and C<ev_loop_destroy>.
520		604
521	=item ev_loop_destroy (loop)	605	=item ev_loop_destroy (loop)
522		606
523	Like C<ev_default_destroy>, but destroys an event loop created by an	607	Like C<ev_default_destroy>, but destroys an event loop created by an
524	earlier call to C<ev_loop_new>.	608	earlier call to C<ev_loop_new>.
…		…
544		628
545	=item ev_loop_fork (loop)	629	=item ev_loop_fork (loop)
546		630
547	Like C<ev_default_fork>, but acts on an event loop created by	631	Like C<ev_default_fork>, but acts on an event loop created by
548	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	632	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
549	after fork, and how you do this is entirely your own problem.	633	after fork that you want to re-use in the child, and how you do this is
		634	entirely your own problem.
550		635
551	=item int ev_is_default_loop (loop)	636	=item int ev_is_default_loop (loop)
552		637
553	Returns true when the given loop actually is the default loop, false otherwise.	638	Returns true when the given loop is, in fact, the default loop, and false
		639	otherwise.
554		640
555	=item unsigned int ev_loop_count (loop)	641	=item unsigned int ev_loop_count (loop)
556		642
557	Returns the count of loop iterations for the loop, which is identical to	643	Returns the count of loop iterations for the loop, which is identical to
558	the number of times libev did poll for new events. It starts at C<0> and	644	the number of times libev did poll for new events. It starts at C<0> and
559	happily wraps around with enough iterations.	645	happily wraps around with enough iterations.
560		646
561	This value can sometimes be useful as a generation counter of sorts (it	647	This value can sometimes be useful as a generation counter of sorts (it
562	"ticks" the number of loop iterations), as it roughly corresponds with	648	"ticks" the number of loop iterations), as it roughly corresponds with
563	C<ev_prepare> and C<ev_check> calls.	649	C<ev_prepare> and C<ev_check> calls.
		650
		651	=item unsigned int ev_loop_depth (loop)
		652
		653	Returns the number of times C<ev_loop> was entered minus the number of
		654	times C<ev_loop> was exited, in other words, the recursion depth.
		655
		656	Outside C<ev_loop>, this number is zero. In a callback, this number is
		657	C<1>, unless C<ev_loop> was invoked recursively (or from another thread),
		658	in which case it is higher.
		659
		660	Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread
		661	etc.), doesn't count as exit.
564		662
565	=item unsigned int ev_backend (loop)	663	=item unsigned int ev_backend (loop)
566		664
567	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	665	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
568	use.	666	use.
…		…
573	received events and started processing them. This timestamp does not	671	received events and started processing them. This timestamp does not
574	change as long as callbacks are being processed, and this is also the base	672	change as long as callbacks are being processed, and this is also the base
575	time used for relative timers. You can treat it as the timestamp of the	673	time used for relative timers. You can treat it as the timestamp of the
576	event occurring (or more correctly, libev finding out about it).	674	event occurring (or more correctly, libev finding out about it).
577		675
		676	=item ev_now_update (loop)
		677
		678	Establishes the current time by querying the kernel, updating the time
		679	returned by C<ev_now ()> in the progress. This is a costly operation and
		680	is usually done automatically within C<ev_loop ()>.
		681
		682	This function is rarely useful, but when some event callback runs for a
		683	very long time without entering the event loop, updating libev's idea of
		684	the current time is a good idea.
		685
		686	See also L<The special problem of time updates> in the C<ev_timer> section.
		687
		688	=item ev_suspend (loop)
		689
		690	=item ev_resume (loop)
		691
		692	These two functions suspend and resume a loop, for use when the loop is
		693	not used for a while and timeouts should not be processed.
		694
		695	A typical use case would be an interactive program such as a game: When
		696	the user presses C<^Z> to suspend the game and resumes it an hour later it
		697	would be best to handle timeouts as if no time had actually passed while
		698	the program was suspended. This can be achieved by calling C<ev_suspend>
		699	in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
		700	C<ev_resume> directly afterwards to resume timer processing.
		701
		702	Effectively, all C<ev_timer> watchers will be delayed by the time spend
		703	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers
		704	will be rescheduled (that is, they will lose any events that would have
		705	occured while suspended).
		706
		707	After calling C<ev_suspend> you B<must not> call I<any> function on the
		708	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>
		709	without a previous call to C<ev_suspend>.
		710
		711	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
		712	event loop time (see C<ev_now_update>).
		713
578	=item ev_loop (loop, int flags)	714	=item ev_loop (loop, int flags)
579		715
580	Finally, this is it, the event handler. This function usually is called	716	Finally, this is it, the event handler. This function usually is called
581	after you initialised all your watchers and you want to start handling	717	after you have initialised all your watchers and you want to start
582	events.	718	handling events.
583		719
584	If the flags argument is specified as C<0>, it will not return until	720	If the flags argument is specified as C<0>, it will not return until
585	either no event watchers are active anymore or C<ev_unloop> was called.	721	either no event watchers are active anymore or C<ev_unloop> was called.
586		722
587	Please note that an explicit C<ev_unloop> is usually better than	723	Please note that an explicit C<ev_unloop> is usually better than
588	relying on all watchers to be stopped when deciding when a program has	724	relying on all watchers to be stopped when deciding when a program has
589	finished (especially in interactive programs), but having a program that	725	finished (especially in interactive programs), but having a program
590	automatically loops as long as it has to and no longer by virtue of	726	that automatically loops as long as it has to and no longer by virtue
591	relying on its watchers stopping correctly is a thing of beauty.	727	of relying on its watchers stopping correctly, that is truly a thing of
		728	beauty.
592		729
593	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	730	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle
594	those events and any outstanding ones, but will not block your process in	731	those events and any already outstanding ones, but will not block your
595	case there are no events and will return after one iteration of the loop.	732	process in case there are no events and will return after one iteration of
		733	the loop.
596		734
597	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	735	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
598	necessary) and will handle those and any outstanding ones. It will block	736	necessary) and will handle those and any already outstanding ones. It
599	your process until at least one new event arrives, and will return after	737	will block your process until at least one new event arrives (which could
600	one iteration of the loop. This is useful if you are waiting for some	738	be an event internal to libev itself, so there is no guarantee that a
601	external event in conjunction with something not expressible using other	739	user-registered callback will be called), and will return after one
		740	iteration of the loop.
		741
		742	This is useful if you are waiting for some external event in conjunction
		743	with something not expressible using other libev watchers (i.e. "roll your
602	libev watchers. However, a pair of C<ev_prepare>/C<ev_check> watchers is	744	own C<ev_loop>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
603	usually a better approach for this kind of thing.	745	usually a better approach for this kind of thing.
604		746
605	Here are the gory details of what C<ev_loop> does:	747	Here are the gory details of what C<ev_loop> does:
606		748
607	- Before the first iteration, call any pending watchers.	749	- Before the first iteration, call any pending watchers.
…		…
617	any active watchers at all will result in not sleeping).	759	any active watchers at all will result in not sleeping).
618	- Sleep if the I/O and timer collect interval say so.	760	- Sleep if the I/O and timer collect interval say so.
619	- Block the process, waiting for any events.	761	- Block the process, waiting for any events.
620	- Queue all outstanding I/O (fd) events.	762	- Queue all outstanding I/O (fd) events.
621	- Update the "event loop time" (ev_now ()), and do time jump adjustments.	763	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
622	- Queue all outstanding timers.	764	- Queue all expired timers.
623	- Queue all outstanding periodics.	765	- Queue all expired periodics.
624	- Unless any events are pending now, queue all idle watchers.	766	- Unless any events are pending now, queue all idle watchers.
625	- Queue all check watchers.	767	- Queue all check watchers.
626	- Call all queued watchers in reverse order (i.e. check watchers first).	768	- Call all queued watchers in reverse order (i.e. check watchers first).
627	Signals and child watchers are implemented as I/O watchers, and will	769	Signals and child watchers are implemented as I/O watchers, and will
628	be handled here by queueing them when their watcher gets executed.	770	be handled here by queueing them when their watcher gets executed.
…		…
645	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	787	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or
646	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	788	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.
647		789
648	This "unloop state" will be cleared when entering C<ev_loop> again.	790	This "unloop state" will be cleared when entering C<ev_loop> again.
649		791
		792	It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls.
		793
650	=item ev_ref (loop)	794	=item ev_ref (loop)
651		795
652	=item ev_unref (loop)	796	=item ev_unref (loop)
653		797
654	Ref/unref can be used to add or remove a reference count on the event	798	Ref/unref can be used to add or remove a reference count on the event
655	loop: Every watcher keeps one reference, and as long as the reference	799	loop: Every watcher keeps one reference, and as long as the reference
656	count is nonzero, C<ev_loop> will not return on its own. If you have	800	count is nonzero, C<ev_loop> will not return on its own.
657	a watcher you never unregister that should not keep C<ev_loop> from	801
658	returning, ev_unref() after starting, and ev_ref() before stopping it. For	802	This is useful when you have a watcher that you never intend to
		803	unregister, but that nevertheless should not keep C<ev_loop> from
		804	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
		805	before stopping it.
		806
659	example, libev itself uses this for its internal signal pipe: It is not	807	As an example, libev itself uses this for its internal signal pipe: It
660	visible to the libev user and should not keep C<ev_loop> from exiting if	808	is not visible to the libev user and should not keep C<ev_loop> from
661	no event watchers registered by it are active. It is also an excellent	809	exiting if no event watchers registered by it are active. It is also an
662	way to do this for generic recurring timers or from within third-party	810	excellent way to do this for generic recurring timers or from within
663	libraries. Just remember to I<unref after start> and I<ref before stop>	811	third-party libraries. Just remember to I<unref after start> and I<ref
664	(but only if the watcher wasn't active before, or was active before,	812	before stop> (but only if the watcher wasn't active before, or was active
665	respectively).	813	before, respectively. Note also that libev might stop watchers itself
		814	(e.g. non-repeating timers) in which case you have to C<ev_ref>
		815	in the callback).
666		816
667	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	817	Example: Create a signal watcher, but keep it from keeping C<ev_loop>
668	running when nothing else is active.	818	running when nothing else is active.
669		819
670	struct ev_signal exitsig;	820	ev_signal exitsig;
671	ev_signal_init (&exitsig, sig_cb, SIGINT);	821	ev_signal_init (&exitsig, sig_cb, SIGINT);
672	ev_signal_start (loop, &exitsig);	822	ev_signal_start (loop, &exitsig);
673	evf_unref (loop);	823	evf_unref (loop);
674		824
675	Example: For some weird reason, unregister the above signal handler again.	825	Example: For some weird reason, unregister the above signal handler again.
…		…
689	Setting these to a higher value (the C<interval> I<must> be >= C<0>)	839	Setting these to a higher value (the C<interval> I<must> be >= C<0>)
690	allows libev to delay invocation of I/O and timer/periodic callbacks	840	allows libev to delay invocation of I/O and timer/periodic callbacks
691	to increase efficiency of loop iterations (or to increase power-saving	841	to increase efficiency of loop iterations (or to increase power-saving
692	opportunities).	842	opportunities).
693		843
694	The background is that sometimes your program runs just fast enough to	844	The idea is that sometimes your program runs just fast enough to handle
695	handle one (or very few) event(s) per loop iteration. While this makes	845	one (or very few) event(s) per loop iteration. While this makes the
696	the program responsive, it also wastes a lot of CPU time to poll for new	846	program responsive, it also wastes a lot of CPU time to poll for new
697	events, especially with backends like C<select ()> which have a high	847	events, especially with backends like C<select ()> which have a high
698	overhead for the actual polling but can deliver many events at once.	848	overhead for the actual polling but can deliver many events at once.
699		849
700	By setting a higher I<io collect interval> you allow libev to spend more	850	By setting a higher I<io collect interval> you allow libev to spend more
701	time collecting I/O events, so you can handle more events per iteration,	851	time collecting I/O events, so you can handle more events per iteration,
702	at the cost of increasing latency. Timeouts (both C<ev_periodic> and	852	at the cost of increasing latency. Timeouts (both C<ev_periodic> and
703	C<ev_timer>) will be not affected. Setting this to a non-null value will	853	C<ev_timer>) will be not affected. Setting this to a non-null value will
704	introduce an additional C<ev_sleep ()> call into most loop iterations.	854	introduce an additional C<ev_sleep ()> call into most loop iterations. The
		855	sleep time ensures that libev will not poll for I/O events more often then
		856	once per this interval, on average.
705		857
706	Likewise, by setting a higher I<timeout collect interval> you allow libev	858	Likewise, by setting a higher I<timeout collect interval> you allow libev
707	to spend more time collecting timeouts, at the expense of increased	859	to spend more time collecting timeouts, at the expense of increased
708	latency (the watcher callback will be called later). C<ev_io> watchers	860	latency/jitter/inexactness (the watcher callback will be called
709	will not be affected. Setting this to a non-null value will not introduce	861	later). C<ev_io> watchers will not be affected. Setting this to a non-null
710	any overhead in libev.	862	value will not introduce any overhead in libev.
711		863
712	Many (busy) programs can usually benefit by setting the I/O collect	864	Many (busy) programs can usually benefit by setting the I/O collect
713	interval to a value near C<0.1> or so, which is often enough for	865	interval to a value near C<0.1> or so, which is often enough for
714	interactive servers (of course not for games), likewise for timeouts. It	866	interactive servers (of course not for games), likewise for timeouts. It
715	usually doesn't make much sense to set it to a lower value than C<0.01>,	867	usually doesn't make much sense to set it to a lower value than C<0.01>,
716	as this approaches the timing granularity of most systems.	868	as this approaches the timing granularity of most systems. Note that if
		869	you do transactions with the outside world and you can't increase the
		870	parallelity, then this setting will limit your transaction rate (if you
		871	need to poll once per transaction and the I/O collect interval is 0.01,
		872	then you can't do more than 100 transations per second).
717		873
718	Setting the I<timeout collect interval> can improve the opportunity for	874	Setting the I<timeout collect interval> can improve the opportunity for
719	saving power, as the program will "bundle" timer callback invocations that	875	saving power, as the program will "bundle" timer callback invocations that
720	are "near" in time together, by delaying some, thus reducing the number of	876	are "near" in time together, by delaying some, thus reducing the number of
721	times the process sleeps and wakes up again. Another useful technique to	877	times the process sleeps and wakes up again. Another useful technique to
722	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure	878	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure
723	they fire on, say, one-second boundaries only.	879	they fire on, say, one-second boundaries only.
724		880
		881	Example: we only need 0.1s timeout granularity, and we wish not to poll
		882	more often than 100 times per second:
		883
		884	ev_set_timeout_collect_interval (EV_DEFAULT_UC_ 0.1);
		885	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
		886
		887	=item ev_invoke_pending (loop)
		888
		889	This call will simply invoke all pending watchers while resetting their
		890	pending state. Normally, C<ev_loop> does this automatically when required,
		891	but when overriding the invoke callback this call comes handy.
		892
		893	=item int ev_pending_count (loop)
		894
		895	Returns the number of pending watchers - zero indicates that no watchers
		896	are pending.
		897
		898	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
		899
		900	This overrides the invoke pending functionality of the loop: Instead of
		901	invoking all pending watchers when there are any, C<ev_loop> will call
		902	this callback instead. This is useful, for example, when you want to
		903	invoke the actual watchers inside another context (another thread etc.).
		904
		905	If you want to reset the callback, use C<ev_invoke_pending> as new
		906	callback.
		907
		908	=item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))
		909
		910	Sometimes you want to share the same loop between multiple threads. This
		911	can be done relatively simply by putting mutex_lock/unlock calls around
		912	each call to a libev function.
		913
		914	However, C<ev_loop> can run an indefinite time, so it is not feasible to
		915	wait for it to return. One way around this is to wake up the loop via
		916	C<ev_unloop> and C<av_async_send>, another way is to set these I<release>
		917	and I<acquire> callbacks on the loop.
		918
		919	When set, then C<release> will be called just before the thread is
		920	suspended waiting for new events, and C<acquire> is called just
		921	afterwards.
		922
		923	Ideally, C<release> will just call your mutex_unlock function, and
		924	C<acquire> will just call the mutex_lock function again.
		925
		926	While event loop modifications are allowed between invocations of
		927	C<release> and C<acquire> (that's their only purpose after all), no
		928	modifications done will affect the event loop, i.e. adding watchers will
		929	have no effect on the set of file descriptors being watched, or the time
		930	waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it
		931	to take note of any changes you made.
		932
		933	In theory, threads executing C<ev_loop> will be async-cancel safe between
		934	invocations of C<release> and C<acquire>.
		935
		936	See also the locking example in the C<THREADS> section later in this
		937	document.
		938
		939	=item ev_set_userdata (loop, void *data)
		940
		941	=item ev_userdata (loop)
		942
		943	Set and retrieve a single C<void *> associated with a loop. When
		944	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
		945	C<0.>
		946
		947	These two functions can be used to associate arbitrary data with a loop,
		948	and are intended solely for the C<invoke_pending_cb>, C<release> and
		949	C<acquire> callbacks described above, but of course can be (ab-)used for
		950	any other purpose as well.
		951
725	=item ev_loop_verify (loop)	952	=item ev_loop_verify (loop)
726		953
727	This function only does something when C<EV_VERIFY> support has been	954	This function only does something when C<EV_VERIFY> support has been
728	compiled in. It tries to go through all internal structures and checks	955	compiled in, which is the default for non-minimal builds. It tries to go
729	them for validity. If anything is found to be inconsistent, it will print	956	through all internal structures and checks them for validity. If anything
730	an error message to standard error and call C<abort ()>.	957	is found to be inconsistent, it will print an error message to standard
		958	error and call C<abort ()>.
731		959
732	This can be used to catch bugs inside libev itself: under normal	960	This can be used to catch bugs inside libev itself: under normal
733	circumstances, this function will never abort as of course libev keeps its	961	circumstances, this function will never abort as of course libev keeps its
734	data structures consistent.	962	data structures consistent.
735		963
736	=back	964	=back
737		965
738		966
739	=head1 ANATOMY OF A WATCHER	967	=head1 ANATOMY OF A WATCHER
740		968
		969	In the following description, uppercase C<TYPE> in names stands for the
		970	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
		971	watchers and C<ev_io_start> for I/O watchers.
		972
741	A watcher is a structure that you create and register to record your	973	A watcher is a structure that you create and register to record your
742	interest in some event. For instance, if you want to wait for STDIN to	974	interest in some event. For instance, if you want to wait for STDIN to
743	become readable, you would create an C<ev_io> watcher for that:	975	become readable, you would create an C<ev_io> watcher for that:
744		976
745	static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)	977	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
746	{	978	{
747	ev_io_stop (w);	979	ev_io_stop (w);
748	ev_unloop (loop, EVUNLOOP_ALL);	980	ev_unloop (loop, EVUNLOOP_ALL);
749	}	981	}
750		982
751	struct ev_loop *loop = ev_default_loop (0);	983	struct ev_loop *loop = ev_default_loop (0);
		984
752	struct ev_io stdin_watcher;	985	ev_io stdin_watcher;
		986
753	ev_init (&stdin_watcher, my_cb);	987	ev_init (&stdin_watcher, my_cb);
754	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	988	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
755	ev_io_start (loop, &stdin_watcher);	989	ev_io_start (loop, &stdin_watcher);
		990
756	ev_loop (loop, 0);	991	ev_loop (loop, 0);
757		992
758	As you can see, you are responsible for allocating the memory for your	993	As you can see, you are responsible for allocating the memory for your
759	watcher structures (and it is usually a bad idea to do this on the stack,	994	watcher structures (and it is I<usually> a bad idea to do this on the
760	although this can sometimes be quite valid).	995	stack).
		996
		997	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
		998	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
761		999
762	Each watcher structure must be initialised by a call to C<ev_init	1000	Each watcher structure must be initialised by a call to C<ev_init
763	(watcher *, callback)>, which expects a callback to be provided. This	1001	(watcher *, callback)>, which expects a callback to be provided. This
764	callback gets invoked each time the event occurs (or, in the case of I/O	1002	callback gets invoked each time the event occurs (or, in the case of I/O
765	watchers, each time the event loop detects that the file descriptor given	1003	watchers, each time the event loop detects that the file descriptor given
766	is readable and/or writable).	1004	is readable and/or writable).
767		1005
768	Each watcher type has its own C<< ev_<type>_set (watcher *, ...) >> macro	1006	Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >>
769	with arguments specific to this watcher type. There is also a macro	1007	macro to configure it, with arguments specific to the watcher type. There
770	to combine initialisation and setting in one call: C<< ev_<type>_init	1008	is also a macro to combine initialisation and setting in one call: C<<
771	(watcher *, callback, ...) >>.	1009	ev_TYPE_init (watcher *, callback, ...) >>.
772		1010
773	To make the watcher actually watch out for events, you have to start it	1011	To make the watcher actually watch out for events, you have to start it
774	with a watcher-specific start function (C<< ev_<type>_start (loop, watcher	1012	with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher
775	*) >>), and you can stop watching for events at any time by calling the	1013	*) >>), and you can stop watching for events at any time by calling the
776	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	1014	corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>.
777		1015
778	As long as your watcher is active (has been started but not stopped) you	1016	As long as your watcher is active (has been started but not stopped) you
779	must not touch the values stored in it. Most specifically you must never	1017	must not touch the values stored in it. Most specifically you must never
780	reinitialise it or call its C<set> macro.	1018	reinitialise it or call its C<ev_TYPE_set> macro.
781		1019
782	Each and every callback receives the event loop pointer as first, the	1020	Each and every callback receives the event loop pointer as first, the
783	registered watcher structure as second, and a bitset of received events as	1021	registered watcher structure as second, and a bitset of received events as
784	third argument.	1022	third argument.
785		1023
…		…
843		1081
844	=item C<EV_ASYNC>	1082	=item C<EV_ASYNC>
845		1083
846	The given async watcher has been asynchronously notified (see C<ev_async>).	1084	The given async watcher has been asynchronously notified (see C<ev_async>).
847		1085
		1086	=item C<EV_CUSTOM>
		1087
		1088	Not ever sent (or otherwise used) by libev itself, but can be freely used
		1089	by libev users to signal watchers (e.g. via C<ev_feed_event>).
		1090
848	=item C<EV_ERROR>	1091	=item C<EV_ERROR>
849		1092
850	An unspecified error has occurred, the watcher has been stopped. This might	1093	An unspecified error has occurred, the watcher has been stopped. This might
851	happen because the watcher could not be properly started because libev	1094	happen because the watcher could not be properly started because libev
852	ran out of memory, a file descriptor was found to be closed or any other	1095	ran out of memory, a file descriptor was found to be closed or any other
		1096	problem. Libev considers these application bugs.
		1097
853	problem. You best act on it by reporting the problem and somehow coping	1098	You best act on it by reporting the problem and somehow coping with the
854	with the watcher being stopped.	1099	watcher being stopped. Note that well-written programs should not receive
		1100	an error ever, so when your watcher receives it, this usually indicates a
		1101	bug in your program.
855		1102
856	Libev will usually signal a few "dummy" events together with an error,	1103	Libev will usually signal a few "dummy" events together with an error, for
857	for example it might indicate that a fd is readable or writable, and if	1104	example it might indicate that a fd is readable or writable, and if your
858	your callbacks is well-written it can just attempt the operation and cope	1105	callbacks is well-written it can just attempt the operation and cope with
859	with the error from read() or write(). This will not work in multi-threaded	1106	the error from read() or write(). This will not work in multi-threaded
860	programs, though, so beware.	1107	programs, though, as the fd could already be closed and reused for another
		1108	thing, so beware.
861		1109
862	=back	1110	=back
863		1111
864	=head2 GENERIC WATCHER FUNCTIONS	1112	=head2 GENERIC WATCHER FUNCTIONS
865
866	In the following description, C<TYPE> stands for the watcher type,
867	e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers.
868		1113
869	=over 4	1114	=over 4
870		1115
871	=item C<ev_init> (ev_TYPE *watcher, callback)	1116	=item C<ev_init> (ev_TYPE *watcher, callback)
872		1117
…		…
878	which rolls both calls into one.	1123	which rolls both calls into one.
879		1124
880	You can reinitialise a watcher at any time as long as it has been stopped	1125	You can reinitialise a watcher at any time as long as it has been stopped
881	(or never started) and there are no pending events outstanding.	1126	(or never started) and there are no pending events outstanding.
882		1127
883	The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,	1128	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
884	int revents)>.	1129	int revents)>.
885		1130
		1131	Example: Initialise an C<ev_io> watcher in two steps.
		1132
		1133	ev_io w;
		1134	ev_init (&w, my_cb);
		1135	ev_io_set (&w, STDIN_FILENO, EV_READ);
		1136
886	=item C<ev_TYPE_set> (ev_TYPE *, [args])	1137	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
887		1138
888	This macro initialises the type-specific parts of a watcher. You need to	1139	This macro initialises the type-specific parts of a watcher. You need to
889	call C<ev_init> at least once before you call this macro, but you can	1140	call C<ev_init> at least once before you call this macro, but you can
890	call C<ev_TYPE_set> any number of times. You must not, however, call this	1141	call C<ev_TYPE_set> any number of times. You must not, however, call this
891	macro on a watcher that is active (it can be pending, however, which is a	1142	macro on a watcher that is active (it can be pending, however, which is a
892	difference to the C<ev_init> macro).	1143	difference to the C<ev_init> macro).
893		1144
894	Although some watcher types do not have type-specific arguments	1145	Although some watcher types do not have type-specific arguments
895	(e.g. C<ev_prepare>) you still need to call its C<set> macro.	1146	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
896		1147
		1148	See C<ev_init>, above, for an example.
		1149
897	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])	1150	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
898		1151
899	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro	1152	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro
900	calls into a single call. This is the most convenient method to initialise	1153	calls into a single call. This is the most convenient method to initialise
901	a watcher. The same limitations apply, of course.	1154	a watcher. The same limitations apply, of course.
902		1155
		1156	Example: Initialise and set an C<ev_io> watcher in one step.
		1157
		1158	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
		1159
903	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)	1160	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
904		1161
905	Starts (activates) the given watcher. Only active watchers will receive	1162	Starts (activates) the given watcher. Only active watchers will receive
906	events. If the watcher is already active nothing will happen.	1163	events. If the watcher is already active nothing will happen.
907		1164
		1165	Example: Start the C<ev_io> watcher that is being abused as example in this
		1166	whole section.
		1167
		1168	ev_io_start (EV_DEFAULT_UC, &w);
		1169
908	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)	1170	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
909		1171
910	Stops the given watcher again (if active) and clears the pending	1172	Stops the given watcher if active, and clears the pending status (whether
		1173	the watcher was active or not).
		1174
911	status. It is possible that stopped watchers are pending (for example,	1175	It is possible that stopped watchers are pending - for example,
912	non-repeating timers are being stopped when they become pending), but	1176	non-repeating timers are being stopped when they become pending - but
913	C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If	1177	calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
914	you want to free or reuse the memory used by the watcher it is therefore a	1178	pending. If you want to free or reuse the memory used by the watcher it is
915	good idea to always call its C<ev_TYPE_stop> function.	1179	therefore a good idea to always call its C<ev_TYPE_stop> function.
916		1180
917	=item bool ev_is_active (ev_TYPE *watcher)	1181	=item bool ev_is_active (ev_TYPE *watcher)
918		1182
919	Returns a true value iff the watcher is active (i.e. it has been started	1183	Returns a true value iff the watcher is active (i.e. it has been started
920	and not yet been stopped). As long as a watcher is active you must not modify	1184	and not yet been stopped). As long as a watcher is active you must not modify
…		…
936	=item ev_cb_set (ev_TYPE *watcher, callback)	1200	=item ev_cb_set (ev_TYPE *watcher, callback)
937		1201
938	Change the callback. You can change the callback at virtually any time	1202	Change the callback. You can change the callback at virtually any time
939	(modulo threads).	1203	(modulo threads).
940		1204
941	=item ev_set_priority (ev_TYPE *watcher, priority)	1205	=item ev_set_priority (ev_TYPE *watcher, int priority)
942		1206
943	=item int ev_priority (ev_TYPE *watcher)	1207	=item int ev_priority (ev_TYPE *watcher)
944		1208
945	Set and query the priority of the watcher. The priority is a small	1209	Set and query the priority of the watcher. The priority is a small
946	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>	1210	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
947	(default: C<-2>). Pending watchers with higher priority will be invoked	1211	(default: C<-2>). Pending watchers with higher priority will be invoked
948	before watchers with lower priority, but priority will not keep watchers	1212	before watchers with lower priority, but priority will not keep watchers
949	from being executed (except for C<ev_idle> watchers).	1213	from being executed (except for C<ev_idle> watchers).
950		1214
951	This means that priorities are I<only> used for ordering callback
952	invocation after new events have been received. This is useful, for
953	example, to reduce latency after idling, or more often, to bind two
954	watchers on the same event and make sure one is called first.
955
956	If you need to suppress invocation when higher priority events are pending	1215	If you need to suppress invocation when higher priority events are pending
957	you need to look at C<ev_idle> watchers, which provide this functionality.	1216	you need to look at C<ev_idle> watchers, which provide this functionality.
958		1217
959	You I<must not> change the priority of a watcher as long as it is active or	1218	You I<must not> change the priority of a watcher as long as it is active or
960	pending.	1219	pending.
961		1220
		1221	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
		1222	fine, as long as you do not mind that the priority value you query might
		1223	or might not have been clamped to the valid range.
		1224
962	The default priority used by watchers when no priority has been set is	1225	The default priority used by watchers when no priority has been set is
963	always C<0>, which is supposed to not be too high and not be too low :).	1226	always C<0>, which is supposed to not be too high and not be too low :).
964		1227
965	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1228	See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of
966	fine, as long as you do not mind that the priority value you query might	1229	priorities.
967	or might not have been adjusted to be within valid range.
968		1230
969	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1231	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
970		1232
971	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1233	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither
972	C<loop> nor C<revents> need to be valid as long as the watcher callback	1234	C<loop> nor C<revents> need to be valid as long as the watcher callback
973	can deal with that fact.	1235	can deal with that fact, as both are simply passed through to the
		1236	callback.
974		1237
975	=item int ev_clear_pending (loop, ev_TYPE *watcher)	1238	=item int ev_clear_pending (loop, ev_TYPE *watcher)
976		1239
977	If the watcher is pending, this function returns clears its pending status	1240	If the watcher is pending, this function clears its pending status and
978	and returns its C<revents> bitset (as if its callback was invoked). If the	1241	returns its C<revents> bitset (as if its callback was invoked). If the
979	watcher isn't pending it does nothing and returns C<0>.	1242	watcher isn't pending it does nothing and returns C<0>.
980		1243
		1244	Sometimes it can be useful to "poll" a watcher instead of waiting for its
		1245	callback to be invoked, which can be accomplished with this function.
		1246
		1247	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
		1248
		1249	Feeds the given event set into the event loop, as if the specified event
		1250	had happened for the specified watcher (which must be a pointer to an
		1251	initialised but not necessarily started event watcher). Obviously you must
		1252	not free the watcher as long as it has pending events.
		1253
		1254	Stopping the watcher, letting libev invoke it, or calling
		1255	C<ev_clear_pending> will clear the pending event, even if the watcher was
		1256	not started in the first place.
		1257
		1258	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
		1259	functions that do not need a watcher.
		1260
981	=back	1261	=back
982		1262
983		1263
984	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1264	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
985		1265
986	Each watcher has, by default, a member C<void *data> that you can change	1266	Each watcher has, by default, a member C<void *data> that you can change
987	and read at any time, libev will completely ignore it. This can be used	1267	and read at any time: libev will completely ignore it. This can be used
988	to associate arbitrary data with your watcher. If you need more data and	1268	to associate arbitrary data with your watcher. If you need more data and
989	don't want to allocate memory and store a pointer to it in that data	1269	don't want to allocate memory and store a pointer to it in that data
990	member, you can also "subclass" the watcher type and provide your own	1270	member, you can also "subclass" the watcher type and provide your own
991	data:	1271	data:
992		1272
993	struct my_io	1273	struct my_io
994	{	1274	{
995	struct ev_io io;	1275	ev_io io;
996	int otherfd;	1276	int otherfd;
997	void *somedata;	1277	void *somedata;
998	struct whatever *mostinteresting;	1278	struct whatever *mostinteresting;
999	}	1279	};
		1280
		1281	...
		1282	struct my_io w;
		1283	ev_io_init (&w.io, my_cb, fd, EV_READ);
1000		1284
1001	And since your callback will be called with a pointer to the watcher, you	1285	And since your callback will be called with a pointer to the watcher, you
1002	can cast it back to your own type:	1286	can cast it back to your own type:
1003		1287
1004	static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents)	1288	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1005	{	1289	{
1006	struct my_io *w = (struct my_io *)w_;	1290	struct my_io *w = (struct my_io *)w_;
1007	...	1291	...
1008	}	1292	}
1009		1293
1010	More interesting and less C-conformant ways of casting your callback type	1294	More interesting and less C-conformant ways of casting your callback type
1011	instead have been omitted.	1295	instead have been omitted.
1012		1296
1013	Another common scenario is having some data structure with multiple	1297	Another common scenario is to use some data structure with multiple
1014	watchers:	1298	embedded watchers:
1015		1299
1016	struct my_biggy	1300	struct my_biggy
1017	{	1301	{
1018	int some_data;	1302	int some_data;
1019	ev_timer t1;	1303	ev_timer t1;
1020	ev_timer t2;	1304	ev_timer t2;
1021	}	1305	}
1022		1306
1023	In this case getting the pointer to C<my_biggy> is a bit more complicated,	1307	In this case getting the pointer to C<my_biggy> is a bit more
1024	you need to use C<offsetof>:	1308	complicated: Either you store the address of your C<my_biggy> struct
		1309	in the C<data> member of the watcher (for woozies), or you need to use
		1310	some pointer arithmetic using C<offsetof> inside your watchers (for real
		1311	programmers):
1025		1312
1026	#include <stddef.h>	1313	#include <stddef.h>
1027		1314
1028	static void	1315	static void
1029	t1_cb (EV_P_ struct ev_timer *w, int revents)	1316	t1_cb (EV_P_ ev_timer *w, int revents)
1030	{	1317	{
1031	struct my_biggy big = (struct my_biggy *	1318	struct my_biggy big = (struct my_biggy *)
1032	(((char *)w) - offsetof (struct my_biggy, t1));	1319	(((char *)w) - offsetof (struct my_biggy, t1));
1033	}	1320	}
1034		1321
1035	static void	1322	static void
1036	t2_cb (EV_P_ struct ev_timer *w, int revents)	1323	t2_cb (EV_P_ ev_timer *w, int revents)
1037	{	1324	{
1038	struct my_biggy big = (struct my_biggy *	1325	struct my_biggy big = (struct my_biggy *)
1039	(((char *)w) - offsetof (struct my_biggy, t2));	1326	(((char *)w) - offsetof (struct my_biggy, t2));
1040	}	1327	}
		1328
		1329	=head2 WATCHER PRIORITY MODELS
		1330
		1331	Many event loops support I<watcher priorities>, which are usually small
		1332	integers that influence the ordering of event callback invocation
		1333	between watchers in some way, all else being equal.
		1334
		1335	In libev, Watcher priorities can be set using C<ev_set_priority>. See its
		1336	description for the more technical details such as the actual priority
		1337	range.
		1338
		1339	There are two common ways how these these priorities are being interpreted
		1340	by event loops:
		1341
		1342	In the more common lock-out model, higher priorities "lock out" invocation
		1343	of lower priority watchers, which means as long as higher priority
		1344	watchers receive events, lower priority watchers are not being invoked.
		1345
		1346	The less common only-for-ordering model uses priorities solely to order
		1347	callback invocation within a single event loop iteration: Higher priority
		1348	watchers are invoked before lower priority ones, but they all get invoked
		1349	before polling for new events.
		1350
		1351	Libev uses the second (only-for-ordering) model for all its watchers
		1352	except for idle watchers (which use the lock-out model).
		1353
		1354	The rationale behind this is that implementing the lock-out model for
		1355	watchers is not well supported by most kernel interfaces, and most event
		1356	libraries will just poll for the same events again and again as long as
		1357	their callbacks have not been executed, which is very inefficient in the
		1358	common case of one high-priority watcher locking out a mass of lower
		1359	priority ones.
		1360
		1361	Static (ordering) priorities are most useful when you have two or more
		1362	watchers handling the same resource: a typical usage example is having an
		1363	C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle
		1364	timeouts. Under load, data might be received while the program handles
		1365	other jobs, but since timers normally get invoked first, the timeout
		1366	handler will be executed before checking for data. In that case, giving
		1367	the timer a lower priority than the I/O watcher ensures that I/O will be
		1368	handled first even under adverse conditions (which is usually, but not
		1369	always, what you want).
		1370
		1371	Since idle watchers use the "lock-out" model, meaning that idle watchers
		1372	will only be executed when no same or higher priority watchers have
		1373	received events, they can be used to implement the "lock-out" model when
		1374	required.
		1375
		1376	For example, to emulate how many other event libraries handle priorities,
		1377	you can associate an C<ev_idle> watcher to each such watcher, and in
		1378	the normal watcher callback, you just start the idle watcher. The real
		1379	processing is done in the idle watcher callback. This causes libev to
		1380	continously poll and process kernel event data for the watcher, but when
		1381	the lock-out case is known to be rare (which in turn is rare :), this is
		1382	workable.
		1383
		1384	Usually, however, the lock-out model implemented that way will perform
		1385	miserably under the type of load it was designed to handle. In that case,
		1386	it might be preferable to stop the real watcher before starting the
		1387	idle watcher, so the kernel will not have to process the event in case
		1388	the actual processing will be delayed for considerable time.
		1389
		1390	Here is an example of an I/O watcher that should run at a strictly lower
		1391	priority than the default, and which should only process data when no
		1392	other events are pending:
		1393
		1394	ev_idle idle; // actual processing watcher
		1395	ev_io io; // actual event watcher
		1396
		1397	static void
		1398	io_cb (EV_P_ ev_io *w, int revents)
		1399	{
		1400	// stop the I/O watcher, we received the event, but
		1401	// are not yet ready to handle it.
		1402	ev_io_stop (EV_A_ w);
		1403
		1404	// start the idle watcher to ahndle the actual event.
		1405	// it will not be executed as long as other watchers
		1406	// with the default priority are receiving events.
		1407	ev_idle_start (EV_A_ &idle);
		1408	}
		1409
		1410	static void
		1411	idle_cb (EV_P_ ev_idle *w, int revents)
		1412	{
		1413	// actual processing
		1414	read (STDIN_FILENO, ...);
		1415
		1416	// have to start the I/O watcher again, as
		1417	// we have handled the event
		1418	ev_io_start (EV_P_ &io);
		1419	}
		1420
		1421	// initialisation
		1422	ev_idle_init (&idle, idle_cb);
		1423	ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ);
		1424	ev_io_start (EV_DEFAULT_ &io);
		1425
		1426	In the "real" world, it might also be beneficial to start a timer, so that
		1427	low-priority connections can not be locked out forever under load. This
		1428	enables your program to keep a lower latency for important connections
		1429	during short periods of high load, while not completely locking out less
		1430	important ones.
1041		1431
1042		1432
1043	=head1 WATCHER TYPES	1433	=head1 WATCHER TYPES
1044		1434
1045	This section describes each watcher in detail, but will not repeat	1435	This section describes each watcher in detail, but will not repeat
…		…
1069	In general you can register as many read and/or write event watchers per	1459	In general you can register as many read and/or write event watchers per
1070	fd as you want (as long as you don't confuse yourself). Setting all file	1460	fd as you want (as long as you don't confuse yourself). Setting all file
1071	descriptors to non-blocking mode is also usually a good idea (but not	1461	descriptors to non-blocking mode is also usually a good idea (but not
1072	required if you know what you are doing).	1462	required if you know what you are doing).
1073		1463
1074	If you must do this, then force the use of a known-to-be-good backend	1464	If you cannot use non-blocking mode, then force the use of a
1075	(at the time of this writing, this includes only C<EVBACKEND_SELECT> and	1465	known-to-be-good backend (at the time of this writing, this includes only
1076	C<EVBACKEND_POLL>).	1466	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
		1467	descriptors for which non-blocking operation makes no sense (such as
		1468	files) - libev doesn't guarentee any specific behaviour in that case.
1077		1469
1078	Another thing you have to watch out for is that it is quite easy to	1470	Another thing you have to watch out for is that it is quite easy to
1079	receive "spurious" readiness notifications, that is your callback might	1471	receive "spurious" readiness notifications, that is your callback might
1080	be called with C<EV_READ> but a subsequent C<read>(2) will actually block	1472	be called with C<EV_READ> but a subsequent C<read>(2) will actually block
1081	because there is no data. Not only are some backends known to create a	1473	because there is no data. Not only are some backends known to create a
1082	lot of those (for example Solaris ports), it is very easy to get into	1474	lot of those (for example Solaris ports), it is very easy to get into
1083	this situation even with a relatively standard program structure. Thus	1475	this situation even with a relatively standard program structure. Thus
1084	it is best to always use non-blocking I/O: An extra C<read>(2) returning	1476	it is best to always use non-blocking I/O: An extra C<read>(2) returning
1085	C<EAGAIN> is far preferable to a program hanging until some data arrives.	1477	C<EAGAIN> is far preferable to a program hanging until some data arrives.
1086		1478
1087	If you cannot run the fd in non-blocking mode (for example you should not	1479	If you cannot run the fd in non-blocking mode (for example you should
1088	play around with an Xlib connection), then you have to separately re-test	1480	not play around with an Xlib connection), then you have to separately
1089	whether a file descriptor is really ready with a known-to-be good interface	1481	re-test whether a file descriptor is really ready with a known-to-be good
1090	such as poll (fortunately in our Xlib example, Xlib already does this on	1482	interface such as poll (fortunately in our Xlib example, Xlib already
1091	its own, so its quite safe to use).	1483	does this on its own, so its quite safe to use). Some people additionally
		1484	use C<SIGALRM> and an interval timer, just to be sure you won't block
		1485	indefinitely.
		1486
		1487	But really, best use non-blocking mode.
1092		1488
1093	=head3 The special problem of disappearing file descriptors	1489	=head3 The special problem of disappearing file descriptors
1094		1490
1095	Some backends (e.g. kqueue, epoll) need to be told about closing a file	1491	Some backends (e.g. kqueue, epoll) need to be told about closing a file
1096	descriptor (either by calling C<close> explicitly or by any other means,	1492	descriptor (either due to calling C<close> explicitly or any other means,
1097	such as C<dup>). The reason is that you register interest in some file	1493	such as C<dup2>). The reason is that you register interest in some file
1098	descriptor, but when it goes away, the operating system will silently drop	1494	descriptor, but when it goes away, the operating system will silently drop
1099	this interest. If another file descriptor with the same number then is	1495	this interest. If another file descriptor with the same number then is
1100	registered with libev, there is no efficient way to see that this is, in	1496	registered with libev, there is no efficient way to see that this is, in
1101	fact, a different file descriptor.	1497	fact, a different file descriptor.
1102		1498
…		…
1133	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1529	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or
1134	C<EVBACKEND_POLL>.	1530	C<EVBACKEND_POLL>.
1135		1531
1136	=head3 The special problem of SIGPIPE	1532	=head3 The special problem of SIGPIPE
1137		1533
1138	While not really specific to libev, it is easy to forget about SIGPIPE:	1534	While not really specific to libev, it is easy to forget about C<SIGPIPE>:
1139	when reading from a pipe whose other end has been closed, your program	1535	when writing to a pipe whose other end has been closed, your program gets
1140	gets send a SIGPIPE, which, by default, aborts your program. For most	1536	sent a SIGPIPE, which, by default, aborts your program. For most programs
1141	programs this is sensible behaviour, for daemons, this is usually	1537	this is sensible behaviour, for daemons, this is usually undesirable.
1142	undesirable.
1143		1538
1144	So when you encounter spurious, unexplained daemon exits, make sure you	1539	So when you encounter spurious, unexplained daemon exits, make sure you
1145	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon	1540	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1146	somewhere, as that would have given you a big clue).	1541	somewhere, as that would have given you a big clue).
1147		1542
		1543	=head3 The special problem of accept()ing when you can't
		1544
		1545	Many implementations of the POSIX C<accept> function (for example,
		1546	found in port-2004 Linux) have the peculiar behaviour of not removing a
		1547	connection from the pending queue in all error cases.
		1548
		1549	For example, larger servers often run out of file descriptors (because
		1550	of resource limits), causing C<accept> to fail with C<ENFILE> but not
		1551	rejecting the connection, leading to libev signalling readiness on
		1552	the next iteration again (the connection still exists after all), and
		1553	typically causing the program to loop at 100% CPU usage.
		1554
		1555	Unfortunately, the set of errors that cause this issue differs between
		1556	operating systems, there is usually little the app can do to remedy the
		1557	situation, and no known thread-safe method of removing the connection to
		1558	cope with overload is known (to me).
		1559
		1560	One of the easiest ways to handle this situation is to just ignore it
		1561	- when the program encounters an overload, it will just loop until the
		1562	situation is over. While this is a form of busy waiting, no OS offers an
		1563	event-based way to handle this situation, so it's the best one can do.
		1564
		1565	A better way to handle the situation is to log any errors other than
		1566	C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
		1567	messages, and continue as usual, which at least gives the user an idea of
		1568	what could be wrong ("raise the ulimit!"). For extra points one could stop
		1569	the C<ev_io> watcher on the listening fd "for a while", which reduces CPU
		1570	usage.
		1571
		1572	If your program is single-threaded, then you could also keep a dummy file
		1573	descriptor for overload situations (e.g. by opening F</dev/null>), and
		1574	when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>,
		1575	close that fd, and create a new dummy fd. This will gracefully refuse
		1576	clients under typical overload conditions.
		1577
		1578	The last way to handle it is to simply log the error and C<exit>, as
		1579	is often done with C<malloc> failures, but this results in an easy
		1580	opportunity for a DoS attack.
1148		1581
1149	=head3 Watcher-Specific Functions	1582	=head3 Watcher-Specific Functions
1150		1583
1151	=over 4	1584	=over 4
1152		1585
1153	=item ev_io_init (ev_io *, callback, int fd, int events)	1586	=item ev_io_init (ev_io *, callback, int fd, int events)
1154		1587
1155	=item ev_io_set (ev_io *, int fd, int events)	1588	=item ev_io_set (ev_io *, int fd, int events)
1156		1589
1157	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to	1590	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to
1158	receive events for and events is either C<EV_READ>, C<EV_WRITE> or	1591	receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or
1159	C<EV_READ | EV_WRITE> to receive the given events.	1592	C<EV_READ | EV_WRITE>, to express the desire to receive the given events.
1160		1593
1161	=item int fd [read-only]	1594	=item int fd [read-only]
1162		1595
1163	The file descriptor being watched.	1596	The file descriptor being watched.
1164		1597
…		…
1173	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well	1606	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well
1174	readable, but only once. Since it is likely line-buffered, you could	1607	readable, but only once. Since it is likely line-buffered, you could
1175	attempt to read a whole line in the callback.	1608	attempt to read a whole line in the callback.
1176		1609
1177	static void	1610	static void
1178	stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1611	stdin_readable_cb (struct ev_loop *loop, ev_io *w, int revents)
1179	{	1612	{
1180	ev_io_stop (loop, w);	1613	ev_io_stop (loop, w);
1181	.. read from stdin here (or from w->fd) and haqndle any I/O errors	1614	.. read from stdin here (or from w->fd) and handle any I/O errors
1182	}	1615	}
1183		1616
1184	...	1617	...
1185	struct ev_loop *loop = ev_default_init (0);	1618	struct ev_loop *loop = ev_default_init (0);
1186	struct ev_io stdin_readable;	1619	ev_io stdin_readable;
1187	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1620	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1188	ev_io_start (loop, &stdin_readable);	1621	ev_io_start (loop, &stdin_readable);
1189	ev_loop (loop, 0);	1622	ev_loop (loop, 0);
1190		1623
1191		1624
…		…
1194	Timer watchers are simple relative timers that generate an event after a	1627	Timer watchers are simple relative timers that generate an event after a
1195	given time, and optionally repeating in regular intervals after that.	1628	given time, and optionally repeating in regular intervals after that.
1196		1629
1197	The timers are based on real time, that is, if you register an event that	1630	The timers are based on real time, that is, if you register an event that
1198	times out after an hour and you reset your system clock to January last	1631	times out after an hour and you reset your system clock to January last
1199	year, it will still time out after (roughly) and hour. "Roughly" because	1632	year, it will still time out after (roughly) one hour. "Roughly" because
1200	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1633	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1201	monotonic clock option helps a lot here).	1634	monotonic clock option helps a lot here).
		1635
		1636	The callback is guaranteed to be invoked only I<after> its timeout has
		1637	passed (not I<at>, so on systems with very low-resolution clocks this
		1638	might introduce a small delay). If multiple timers become ready during the
		1639	same loop iteration then the ones with earlier time-out values are invoked
		1640	before ones of the same priority with later time-out values (but this is
		1641	no longer true when a callback calls C<ev_loop> recursively).
		1642
		1643	=head3 Be smart about timeouts
		1644
		1645	Many real-world problems involve some kind of timeout, usually for error
		1646	recovery. A typical example is an HTTP request - if the other side hangs,
		1647	you want to raise some error after a while.
		1648
		1649	What follows are some ways to handle this problem, from obvious and
		1650	inefficient to smart and efficient.
		1651
		1652	In the following, a 60 second activity timeout is assumed - a timeout that
		1653	gets reset to 60 seconds each time there is activity (e.g. each time some
		1654	data or other life sign was received).
		1655
		1656	=over 4
		1657
		1658	=item 1. Use a timer and stop, reinitialise and start it on activity.
		1659
		1660	This is the most obvious, but not the most simple way: In the beginning,
		1661	start the watcher:
		1662
		1663	ev_timer_init (timer, callback, 60., 0.);
		1664	ev_timer_start (loop, timer);
		1665
		1666	Then, each time there is some activity, C<ev_timer_stop> it, initialise it
		1667	and start it again:
		1668
		1669	ev_timer_stop (loop, timer);
		1670	ev_timer_set (timer, 60., 0.);
		1671	ev_timer_start (loop, timer);
		1672
		1673	This is relatively simple to implement, but means that each time there is
		1674	some activity, libev will first have to remove the timer from its internal
		1675	data structure and then add it again. Libev tries to be fast, but it's
		1676	still not a constant-time operation.
		1677
		1678	=item 2. Use a timer and re-start it with C<ev_timer_again> inactivity.
		1679
		1680	This is the easiest way, and involves using C<ev_timer_again> instead of
		1681	C<ev_timer_start>.
		1682
		1683	To implement this, configure an C<ev_timer> with a C<repeat> value
		1684	of C<60> and then call C<ev_timer_again> at start and each time you
		1685	successfully read or write some data. If you go into an idle state where
		1686	you do not expect data to travel on the socket, you can C<ev_timer_stop>
		1687	the timer, and C<ev_timer_again> will automatically restart it if need be.
		1688
		1689	That means you can ignore both the C<ev_timer_start> function and the
		1690	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
		1691	member and C<ev_timer_again>.
		1692
		1693	At start:
		1694
		1695	ev_init (timer, callback);
		1696	timer->repeat = 60.;
		1697	ev_timer_again (loop, timer);
		1698
		1699	Each time there is some activity:
		1700
		1701	ev_timer_again (loop, timer);
		1702
		1703	It is even possible to change the time-out on the fly, regardless of
		1704	whether the watcher is active or not:
		1705
		1706	timer->repeat = 30.;
		1707	ev_timer_again (loop, timer);
		1708
		1709	This is slightly more efficient then stopping/starting the timer each time
		1710	you want to modify its timeout value, as libev does not have to completely
		1711	remove and re-insert the timer from/into its internal data structure.
		1712
		1713	It is, however, even simpler than the "obvious" way to do it.
		1714
		1715	=item 3. Let the timer time out, but then re-arm it as required.
		1716
		1717	This method is more tricky, but usually most efficient: Most timeouts are
		1718	relatively long compared to the intervals between other activity - in
		1719	our example, within 60 seconds, there are usually many I/O events with
		1720	associated activity resets.
		1721
		1722	In this case, it would be more efficient to leave the C<ev_timer> alone,
		1723	but remember the time of last activity, and check for a real timeout only
		1724	within the callback:
		1725
		1726	ev_tstamp last_activity; // time of last activity
		1727
		1728	static void
		1729	callback (EV_P_ ev_timer *w, int revents)
		1730	{
		1731	ev_tstamp now = ev_now (EV_A);
		1732	ev_tstamp timeout = last_activity + 60.;
		1733
		1734	// if last_activity + 60. is older than now, we did time out
		1735	if (timeout < now)
		1736	{
		1737	// timeout occured, take action
		1738	}
		1739	else
		1740	{
		1741	// callback was invoked, but there was some activity, re-arm
		1742	// the watcher to fire in last_activity + 60, which is
		1743	// guaranteed to be in the future, so "again" is positive:
		1744	w->repeat = timeout - now;
		1745	ev_timer_again (EV_A_ w);
		1746	}
		1747	}
		1748
		1749	To summarise the callback: first calculate the real timeout (defined
		1750	as "60 seconds after the last activity"), then check if that time has
		1751	been reached, which means something I<did>, in fact, time out. Otherwise
		1752	the callback was invoked too early (C<timeout> is in the future), so
		1753	re-schedule the timer to fire at that future time, to see if maybe we have
		1754	a timeout then.
		1755
		1756	Note how C<ev_timer_again> is used, taking advantage of the
		1757	C<ev_timer_again> optimisation when the timer is already running.
		1758
		1759	This scheme causes more callback invocations (about one every 60 seconds
		1760	minus half the average time between activity), but virtually no calls to
		1761	libev to change the timeout.
		1762
		1763	To start the timer, simply initialise the watcher and set C<last_activity>
		1764	to the current time (meaning we just have some activity :), then call the
		1765	callback, which will "do the right thing" and start the timer:
		1766
		1767	ev_init (timer, callback);
		1768	last_activity = ev_now (loop);
		1769	callback (loop, timer, EV_TIMEOUT);
		1770
		1771	And when there is some activity, simply store the current time in
		1772	C<last_activity>, no libev calls at all:
		1773
		1774	last_actiivty = ev_now (loop);
		1775
		1776	This technique is slightly more complex, but in most cases where the
		1777	time-out is unlikely to be triggered, much more efficient.
		1778
		1779	Changing the timeout is trivial as well (if it isn't hard-coded in the
		1780	callback :) - just change the timeout and invoke the callback, which will
		1781	fix things for you.
		1782
		1783	=item 4. Wee, just use a double-linked list for your timeouts.
		1784
		1785	If there is not one request, but many thousands (millions...), all
		1786	employing some kind of timeout with the same timeout value, then one can
		1787	do even better:
		1788
		1789	When starting the timeout, calculate the timeout value and put the timeout
		1790	at the I<end> of the list.
		1791
		1792	Then use an C<ev_timer> to fire when the timeout at the I<beginning> of
		1793	the list is expected to fire (for example, using the technique #3).
		1794
		1795	When there is some activity, remove the timer from the list, recalculate
		1796	the timeout, append it to the end of the list again, and make sure to
		1797	update the C<ev_timer> if it was taken from the beginning of the list.
		1798
		1799	This way, one can manage an unlimited number of timeouts in O(1) time for
		1800	starting, stopping and updating the timers, at the expense of a major
		1801	complication, and having to use a constant timeout. The constant timeout
		1802	ensures that the list stays sorted.
		1803
		1804	=back
		1805
		1806	So which method the best?
		1807
		1808	Method #2 is a simple no-brain-required solution that is adequate in most
		1809	situations. Method #3 requires a bit more thinking, but handles many cases
		1810	better, and isn't very complicated either. In most case, choosing either
		1811	one is fine, with #3 being better in typical situations.
		1812
		1813	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is
		1814	rather complicated, but extremely efficient, something that really pays
		1815	off after the first million or so of active timers, i.e. it's usually
		1816	overkill :)
		1817
		1818	=head3 The special problem of time updates
		1819
		1820	Establishing the current time is a costly operation (it usually takes at
		1821	least two system calls): EV therefore updates its idea of the current
		1822	time only before and after C<ev_loop> collects new events, which causes a
		1823	growing difference between C<ev_now ()> and C<ev_time ()> when handling
		1824	lots of events in one iteration.
1202		1825
1203	The relative timeouts are calculated relative to the C<ev_now ()>	1826	The relative timeouts are calculated relative to the C<ev_now ()>
1204	time. This is usually the right thing as this timestamp refers to the time	1827	time. This is usually the right thing as this timestamp refers to the time
1205	of the event triggering whatever timeout you are modifying/starting. If	1828	of the event triggering whatever timeout you are modifying/starting. If
1206	you suspect event processing to be delayed and you I<need> to base the timeout	1829	you suspect event processing to be delayed and you I<need> to base the
1207	on the current time, use something like this to adjust for this:	1830	timeout on the current time, use something like this to adjust for this:
1208		1831
1209	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	1832	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
1210		1833
1211	The callback is guaranteed to be invoked only after its timeout has passed,	1834	If the event loop is suspended for a long time, you can also force an
1212	but if multiple timers become ready during the same loop iteration then	1835	update of the time returned by C<ev_now ()> by calling C<ev_now_update
1213	order of execution is undefined.	1836	()>.
		1837
		1838	=head3 The special problems of suspended animation
		1839
		1840	When you leave the server world it is quite customary to hit machines that
		1841	can suspend/hibernate - what happens to the clocks during such a suspend?
		1842
		1843	Some quick tests made with a Linux 2.6.28 indicate that a suspend freezes
		1844	all processes, while the clocks (C<times>, C<CLOCK_MONOTONIC>) continue
		1845	to run until the system is suspended, but they will not advance while the
		1846	system is suspended. That means, on resume, it will be as if the program
		1847	was frozen for a few seconds, but the suspend time will not be counted
		1848	towards C<ev_timer> when a monotonic clock source is used. The real time
		1849	clock advanced as expected, but if it is used as sole clocksource, then a
		1850	long suspend would be detected as a time jump by libev, and timers would
		1851	be adjusted accordingly.
		1852
		1853	I would not be surprised to see different behaviour in different between
		1854	operating systems, OS versions or even different hardware.
		1855
		1856	The other form of suspend (job control, or sending a SIGSTOP) will see a
		1857	time jump in the monotonic clocks and the realtime clock. If the program
		1858	is suspended for a very long time, and monotonic clock sources are in use,
		1859	then you can expect C<ev_timer>s to expire as the full suspension time
		1860	will be counted towards the timers. When no monotonic clock source is in
		1861	use, then libev will again assume a timejump and adjust accordingly.
		1862
		1863	It might be beneficial for this latter case to call C<ev_suspend>
		1864	and C<ev_resume> in code that handles C<SIGTSTP>, to at least get
		1865	deterministic behaviour in this case (you can do nothing against
		1866	C<SIGSTOP>).
1214		1867
1215	=head3 Watcher-Specific Functions and Data Members	1868	=head3 Watcher-Specific Functions and Data Members
1216		1869
1217	=over 4	1870	=over 4
1218		1871
…		…
1242	If the timer is started but non-repeating, stop it (as if it timed out).	1895	If the timer is started but non-repeating, stop it (as if it timed out).
1243		1896
1244	If the timer is repeating, either start it if necessary (with the	1897	If the timer is repeating, either start it if necessary (with the
1245	C<repeat> value), or reset the running timer to the C<repeat> value.	1898	C<repeat> value), or reset the running timer to the C<repeat> value.
1246		1899
1247	This sounds a bit complicated, but here is a useful and typical	1900	This sounds a bit complicated, see L<Be smart about timeouts>, above, for a
1248	example: Imagine you have a TCP connection and you want a so-called idle	1901	usage example.
1249	timeout, that is, you want to be called when there have been, say, 60
1250	seconds of inactivity on the socket. The easiest way to do this is to
1251	configure an C<ev_timer> with a C<repeat> value of C<60> and then call
1252	C<ev_timer_again> each time you successfully read or write some data. If
1253	you go into an idle state where you do not expect data to travel on the
1254	socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
1255	automatically restart it if need be.
1256		1902
1257	That means you can ignore the C<after> value and C<ev_timer_start>	1903	=item ev_tstamp ev_timer_remaining (loop, ev_timer *)
1258	altogether and only ever use the C<repeat> value and C<ev_timer_again>:
1259		1904
1260	ev_timer_init (timer, callback, 0., 5.);	1905	Returns the remaining time until a timer fires. If the timer is active,
1261	ev_timer_again (loop, timer);	1906	then this time is relative to the current event loop time, otherwise it's
1262	...	1907	the timeout value currently configured.
1263	timer->again = 17.;
1264	ev_timer_again (loop, timer);
1265	...
1266	timer->again = 10.;
1267	ev_timer_again (loop, timer);
1268		1908
1269	This is more slightly efficient then stopping/starting the timer each time	1909	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
1270	you want to modify its timeout value.	1910	C<5>. When the timer is started and one second passes, C<ev_timer_remaining>
		1911	will return C<4>. When the timer expires and is restarted, it will return
		1912	roughly C<7> (likely slightly less as callback invocation takes some time,
		1913	too), and so on.
1271		1914
1272	=item ev_tstamp repeat [read-write]	1915	=item ev_tstamp repeat [read-write]
1273		1916
1274	The current C<repeat> value. Will be used each time the watcher times out	1917	The current C<repeat> value. Will be used each time the watcher times out
1275	or C<ev_timer_again> is called and determines the next timeout (if any),	1918	or C<ev_timer_again> is called, and determines the next timeout (if any),
1276	which is also when any modifications are taken into account.	1919	which is also when any modifications are taken into account.
1277		1920
1278	=back	1921	=back
1279		1922
1280	=head3 Examples	1923	=head3 Examples
1281		1924
1282	Example: Create a timer that fires after 60 seconds.	1925	Example: Create a timer that fires after 60 seconds.
1283		1926
1284	static void	1927	static void
1285	one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1928	one_minute_cb (struct ev_loop *loop, ev_timer *w, int revents)
1286	{	1929	{
1287	.. one minute over, w is actually stopped right here	1930	.. one minute over, w is actually stopped right here
1288	}	1931	}
1289		1932
1290	struct ev_timer mytimer;	1933	ev_timer mytimer;
1291	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);	1934	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1292	ev_timer_start (loop, &mytimer);	1935	ev_timer_start (loop, &mytimer);
1293		1936
1294	Example: Create a timeout timer that times out after 10 seconds of	1937	Example: Create a timeout timer that times out after 10 seconds of
1295	inactivity.	1938	inactivity.
1296		1939
1297	static void	1940	static void
1298	timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	1941	timeout_cb (struct ev_loop *loop, ev_timer *w, int revents)
1299	{	1942	{
1300	.. ten seconds without any activity	1943	.. ten seconds without any activity
1301	}	1944	}
1302		1945
1303	struct ev_timer mytimer;	1946	ev_timer mytimer;
1304	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	1947	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1305	ev_timer_again (&mytimer); /* start timer */	1948	ev_timer_again (&mytimer); /* start timer */
1306	ev_loop (loop, 0);	1949	ev_loop (loop, 0);
1307		1950
1308	// and in some piece of code that gets executed on any "activity":	1951	// and in some piece of code that gets executed on any "activity":
…		…
1313	=head2 C<ev_periodic> - to cron or not to cron?	1956	=head2 C<ev_periodic> - to cron or not to cron?
1314		1957
1315	Periodic watchers are also timers of a kind, but they are very versatile	1958	Periodic watchers are also timers of a kind, but they are very versatile
1316	(and unfortunately a bit complex).	1959	(and unfortunately a bit complex).
1317		1960
1318	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	1961	Unlike C<ev_timer>, periodic watchers are not based on real time (or
1319	but on wall clock time (absolute time). You can tell a periodic watcher	1962	relative time, the physical time that passes) but on wall clock time
1320	to trigger after some specific point in time. For example, if you tell a	1963	(absolute time, the thing you can read on your calender or clock). The
1321	periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now ()	1964	difference is that wall clock time can run faster or slower than real
1322	+ 10.>, that is, an absolute time not a delay) and then reset your system	1965	time, and time jumps are not uncommon (e.g. when you adjust your
1323	clock to January of the previous year, then it will take more than year	1966	wrist-watch).
1324	to trigger the event (unlike an C<ev_timer>, which would still trigger
1325	roughly 10 seconds later as it uses a relative timeout).
1326		1967
		1968	You can tell a periodic watcher to trigger after some specific point
		1969	in time: for example, if you tell a periodic watcher to trigger "in 10
		1970	seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time
		1971	not a delay) and then reset your system clock to January of the previous
		1972	year, then it will take a year or more to trigger the event (unlike an
		1973	C<ev_timer>, which would still trigger roughly 10 seconds after starting
		1974	it, as it uses a relative timeout).
		1975
1327	C<ev_periodic>s can also be used to implement vastly more complex timers,	1976	C<ev_periodic> watchers can also be used to implement vastly more complex
1328	such as triggering an event on each "midnight, local time", or other	1977	timers, such as triggering an event on each "midnight, local time", or
1329	complicated, rules.	1978	other complicated rules. This cannot be done with C<ev_timer> watchers, as
		1979	those cannot react to time jumps.
1330		1980
1331	As with timers, the callback is guaranteed to be invoked only when the	1981	As with timers, the callback is guaranteed to be invoked only when the
1332	time (C<at>) has passed, but if multiple periodic timers become ready	1982	point in time where it is supposed to trigger has passed. If multiple
1333	during the same loop iteration then order of execution is undefined.	1983	timers become ready during the same loop iteration then the ones with
		1984	earlier time-out values are invoked before ones with later time-out values
		1985	(but this is no longer true when a callback calls C<ev_loop> recursively).
1334		1986
1335	=head3 Watcher-Specific Functions and Data Members	1987	=head3 Watcher-Specific Functions and Data Members
1336		1988
1337	=over 4	1989	=over 4
1338		1990
1339	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	1991	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1340		1992
1341	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	1993	=item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1342		1994
1343	Lots of arguments, lets sort it out... There are basically three modes of	1995	Lots of arguments, let's sort it out... There are basically three modes of
1344	operation, and we will explain them from simplest to complex:	1996	operation, and we will explain them from simplest to most complex:
1345		1997
1346	=over 4	1998	=over 4
1347		1999
1348	=item * absolute timer (at = time, interval = reschedule_cb = 0)	2000	=item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0)
1349		2001
1350	In this configuration the watcher triggers an event after the wall clock	2002	In this configuration the watcher triggers an event after the wall clock
1351	time C<at> has passed and doesn't repeat. It will not adjust when a time	2003	time C<offset> has passed. It will not repeat and will not adjust when a
1352	jump occurs, that is, if it is to be run at January 1st 2011 then it will	2004	time jump occurs, that is, if it is to be run at January 1st 2011 then it
1353	run when the system time reaches or surpasses this time.	2005	will be stopped and invoked when the system clock reaches or surpasses
		2006	this point in time.
1354		2007
1355	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)	2008	=item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0)
1356		2009
1357	In this mode the watcher will always be scheduled to time out at the next	2010	In this mode the watcher will always be scheduled to time out at the next
1358	C<at + N * interval> time (for some integer N, which can also be negative)	2011	C<offset + N * interval> time (for some integer N, which can also be
1359	and then repeat, regardless of any time jumps.	2012	negative) and then repeat, regardless of any time jumps. The C<offset>
		2013	argument is merely an offset into the C<interval> periods.
1360		2014
1361	This can be used to create timers that do not drift with respect to system	2015	This can be used to create timers that do not drift with respect to the
1362	time, for example, here is a C<ev_periodic> that triggers each hour, on	2016	system clock, for example, here is an C<ev_periodic> that triggers each
1363	the hour:	2017	hour, on the hour (with respect to UTC):
1364		2018
1365	ev_periodic_set (&periodic, 0., 3600., 0);	2019	ev_periodic_set (&periodic, 0., 3600., 0);
1366		2020
1367	This doesn't mean there will always be 3600 seconds in between triggers,	2021	This doesn't mean there will always be 3600 seconds in between triggers,
1368	but only that the callback will be called when the system time shows a	2022	but only that the callback will be called when the system time shows a
1369	full hour (UTC), or more correctly, when the system time is evenly divisible	2023	full hour (UTC), or more correctly, when the system time is evenly divisible
1370	by 3600.	2024	by 3600.
1371		2025
1372	Another way to think about it (for the mathematically inclined) is that	2026	Another way to think about it (for the mathematically inclined) is that
1373	C<ev_periodic> will try to run the callback in this mode at the next possible	2027	C<ev_periodic> will try to run the callback in this mode at the next possible
1374	time where C<time = at (mod interval)>, regardless of any time jumps.	2028	time where C<time = offset (mod interval)>, regardless of any time jumps.
1375		2029
1376	For numerical stability it is preferable that the C<at> value is near	2030	For numerical stability it is preferable that the C<offset> value is near
1377	C<ev_now ()> (the current time), but there is no range requirement for	2031	C<ev_now ()> (the current time), but there is no range requirement for
1378	this value, and in fact is often specified as zero.	2032	this value, and in fact is often specified as zero.
1379		2033
1380	Note also that there is an upper limit to how often a timer can fire (CPU	2034	Note also that there is an upper limit to how often a timer can fire (CPU
1381	speed for example), so if C<interval> is very small then timing stability	2035	speed for example), so if C<interval> is very small then timing stability
1382	will of course deteriorate. Libev itself tries to be exact to be about one	2036	will of course deteriorate. Libev itself tries to be exact to be about one
1383	millisecond (if the OS supports it and the machine is fast enough).	2037	millisecond (if the OS supports it and the machine is fast enough).
1384		2038
1385	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)	2039	=item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback)
1386		2040
1387	In this mode the values for C<interval> and C<at> are both being	2041	In this mode the values for C<interval> and C<offset> are both being
1388	ignored. Instead, each time the periodic watcher gets scheduled, the	2042	ignored. Instead, each time the periodic watcher gets scheduled, the
1389	reschedule callback will be called with the watcher as first, and the	2043	reschedule callback will be called with the watcher as first, and the
1390	current time as second argument.	2044	current time as second argument.
1391		2045
1392	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,	2046	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever,
1393	ever, or make ANY event loop modifications whatsoever>.	2047	or make ANY other event loop modifications whatsoever, unless explicitly
		2048	allowed by documentation here>.
1394		2049
1395	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop	2050	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop
1396	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the	2051	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
1397	only event loop modification you are allowed to do).	2052	only event loop modification you are allowed to do).
1398		2053
1399	The callback prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic	2054	The callback prototype is C<ev_tstamp (*reschedule_cb)(ev_periodic
1400	*w, ev_tstamp now)>, e.g.:	2055	*w, ev_tstamp now)>, e.g.:
1401		2056
		2057	static ev_tstamp
1402	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	2058	my_rescheduler (ev_periodic *w, ev_tstamp now)
1403	{	2059	{
1404	return now + 60.;	2060	return now + 60.;
1405	}	2061	}
1406		2062
1407	It must return the next time to trigger, based on the passed time value	2063	It must return the next time to trigger, based on the passed time value
…		…
1427	a different time than the last time it was called (e.g. in a crond like	2083	a different time than the last time it was called (e.g. in a crond like
1428	program when the crontabs have changed).	2084	program when the crontabs have changed).
1429		2085
1430	=item ev_tstamp ev_periodic_at (ev_periodic *)	2086	=item ev_tstamp ev_periodic_at (ev_periodic *)
1431		2087
1432	When active, returns the absolute time that the watcher is supposed to	2088	When active, returns the absolute time that the watcher is supposed
1433	trigger next.	2089	to trigger next. This is not the same as the C<offset> argument to
		2090	C<ev_periodic_set>, but indeed works even in interval and manual
		2091	rescheduling modes.
1434		2092
1435	=item ev_tstamp offset [read-write]	2093	=item ev_tstamp offset [read-write]
1436		2094
1437	When repeating, this contains the offset value, otherwise this is the	2095	When repeating, this contains the offset value, otherwise this is the
1438	absolute point in time (the C<at> value passed to C<ev_periodic_set>).	2096	absolute point in time (the C<offset> value passed to C<ev_periodic_set>,
		2097	although libev might modify this value for better numerical stability).
1439		2098
1440	Can be modified any time, but changes only take effect when the periodic	2099	Can be modified any time, but changes only take effect when the periodic
1441	timer fires or C<ev_periodic_again> is being called.	2100	timer fires or C<ev_periodic_again> is being called.
1442		2101
1443	=item ev_tstamp interval [read-write]	2102	=item ev_tstamp interval [read-write]
1444		2103
1445	The current interval value. Can be modified any time, but changes only	2104	The current interval value. Can be modified any time, but changes only
1446	take effect when the periodic timer fires or C<ev_periodic_again> is being	2105	take effect when the periodic timer fires or C<ev_periodic_again> is being
1447	called.	2106	called.
1448		2107
1449	=item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]	2108	=item ev_tstamp (*reschedule_cb)(ev_periodic *w, ev_tstamp now) [read-write]
1450		2109
1451	The current reschedule callback, or C<0>, if this functionality is	2110	The current reschedule callback, or C<0>, if this functionality is
1452	switched off. Can be changed any time, but changes only take effect when	2111	switched off. Can be changed any time, but changes only take effect when
1453	the periodic timer fires or C<ev_periodic_again> is being called.	2112	the periodic timer fires or C<ev_periodic_again> is being called.
1454		2113
1455	=back	2114	=back
1456		2115
1457	=head3 Examples	2116	=head3 Examples
1458		2117
1459	Example: Call a callback every hour, or, more precisely, whenever the	2118	Example: Call a callback every hour, or, more precisely, whenever the
1460	system clock is divisible by 3600. The callback invocation times have	2119	system time is divisible by 3600. The callback invocation times have
1461	potentially a lot of jitter, but good long-term stability.	2120	potentially a lot of jitter, but good long-term stability.
1462		2121
1463	static void	2122	static void
1464	clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)	2123	clock_cb (struct ev_loop *loop, ev_io *w, int revents)
1465	{	2124	{
1466	... its now a full hour (UTC, or TAI or whatever your clock follows)	2125	... its now a full hour (UTC, or TAI or whatever your clock follows)
1467	}	2126	}
1468		2127
1469	struct ev_periodic hourly_tick;	2128	ev_periodic hourly_tick;
1470	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);	2129	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1471	ev_periodic_start (loop, &hourly_tick);	2130	ev_periodic_start (loop, &hourly_tick);
1472		2131
1473	Example: The same as above, but use a reschedule callback to do it:	2132	Example: The same as above, but use a reschedule callback to do it:
1474		2133
1475	#include <math.h>	2134	#include <math.h>
1476		2135
1477	static ev_tstamp	2136	static ev_tstamp
1478	my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)	2137	my_scheduler_cb (ev_periodic *w, ev_tstamp now)
1479	{	2138	{
1480	return fmod (now, 3600.) + 3600.;	2139	return now + (3600. - fmod (now, 3600.));
1481	}	2140	}
1482		2141
1483	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);	2142	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1484		2143
1485	Example: Call a callback every hour, starting now:	2144	Example: Call a callback every hour, starting now:
1486		2145
1487	struct ev_periodic hourly_tick;	2146	ev_periodic hourly_tick;
1488	ev_periodic_init (&hourly_tick, clock_cb,	2147	ev_periodic_init (&hourly_tick, clock_cb,
1489	fmod (ev_now (loop), 3600.), 3600., 0);	2148	fmod (ev_now (loop), 3600.), 3600., 0);
1490	ev_periodic_start (loop, &hourly_tick);	2149	ev_periodic_start (loop, &hourly_tick);
1491		2150
1492		2151
…		…
1495	Signal watchers will trigger an event when the process receives a specific	2154	Signal watchers will trigger an event when the process receives a specific
1496	signal one or more times. Even though signals are very asynchronous, libev	2155	signal one or more times. Even though signals are very asynchronous, libev
1497	will try it's best to deliver signals synchronously, i.e. as part of the	2156	will try it's best to deliver signals synchronously, i.e. as part of the
1498	normal event processing, like any other event.	2157	normal event processing, like any other event.
1499		2158
		2159	If you want signals to be delivered truly asynchronously, just use
		2160	C<sigaction> as you would do without libev and forget about sharing
		2161	the signal. You can even use C<ev_async> from a signal handler to
		2162	synchronously wake up an event loop.
		2163
1500	You can configure as many watchers as you like per signal. Only when the	2164	You can configure as many watchers as you like for the same signal, but
		2165	only within the same loop, i.e. you can watch for C<SIGINT> in your
		2166	default loop and for C<SIGIO> in another loop, but you cannot watch for
		2167	C<SIGINT> in both the default loop and another loop at the same time. At
		2168	the moment, C<SIGCHLD> is permanently tied to the default loop.
		2169
1501	first watcher gets started will libev actually register a signal watcher	2170	When the first watcher gets started will libev actually register something
1502	with the kernel (thus it coexists with your own signal handlers as long	2171	with the kernel (thus it coexists with your own signal handlers as long as
1503	as you don't register any with libev). Similarly, when the last signal	2172	you don't register any with libev for the same signal).
1504	watcher for a signal is stopped libev will reset the signal handler to
1505	SIG_DFL (regardless of what it was set to before).
1506		2173
1507	If possible and supported, libev will install its handlers with	2174	If possible and supported, libev will install its handlers with
1508	C<SA_RESTART> behaviour enabled, so system calls should not be unduly	2175	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
1509	interrupted. If you have a problem with system calls getting interrupted by	2176	not be unduly interrupted. If you have a problem with system calls getting
1510	signals you can block all signals in an C<ev_check> watcher and unblock	2177	interrupted by signals you can block all signals in an C<ev_check> watcher
1511	them in an C<ev_prepare> watcher.	2178	and unblock them in an C<ev_prepare> watcher.
		2179
		2180	=head3 The special problem of inheritance over fork/execve/pthread_create
		2181
		2182	Both the signal mask (C<sigprocmask>) and the signal disposition
		2183	(C<sigaction>) are unspecified after starting a signal watcher (and after
		2184	stopping it again), that is, libev might or might not block the signal,
		2185	and might or might not set or restore the installed signal handler.
		2186
		2187	While this does not matter for the signal disposition (libev never
		2188	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
		2189	C<execve>), this matters for the signal mask: many programs do not expect
		2190	certain signals to be blocked.
		2191
		2192	This means that before calling C<exec> (from the child) you should reset
		2193	the signal mask to whatever "default" you expect (all clear is a good
		2194	choice usually).
		2195
		2196	The simplest way to ensure that the signal mask is reset in the child is
		2197	to install a fork handler with C<pthread_atfork> that resets it. That will
		2198	catch fork calls done by libraries (such as the libc) as well.
		2199
		2200	In current versions of libev, the signal will not be blocked indefinitely
		2201	unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces
		2202	the window of opportunity for problems, it will not go away, as libev
		2203	I<has> to modify the signal mask, at least temporarily.
		2204
		2205	So I can't stress this enough: I<If you do not reset your signal mask when
		2206	you expect it to be empty, you have a race condition in your code>. This
		2207	is not a libev-specific thing, this is true for most event libraries.
1512		2208
1513	=head3 Watcher-Specific Functions and Data Members	2209	=head3 Watcher-Specific Functions and Data Members
1514		2210
1515	=over 4	2211	=over 4
1516		2212
…		…
1527		2223
1528	=back	2224	=back
1529		2225
1530	=head3 Examples	2226	=head3 Examples
1531		2227
1532	Example: Try to exit cleanly on SIGINT and SIGTERM.	2228	Example: Try to exit cleanly on SIGINT.
1533		2229
1534	static void	2230	static void
1535	sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)	2231	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
1536	{	2232	{
1537	ev_unloop (loop, EVUNLOOP_ALL);	2233	ev_unloop (loop, EVUNLOOP_ALL);
1538	}	2234	}
1539		2235
1540	struct ev_signal signal_watcher;	2236	ev_signal signal_watcher;
1541	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2237	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1542	ev_signal_start (loop, &sigint_cb);	2238	ev_signal_start (loop, &signal_watcher);
1543		2239
1544		2240
1545	=head2 C<ev_child> - watch out for process status changes	2241	=head2 C<ev_child> - watch out for process status changes
1546		2242
1547	Child watchers trigger when your process receives a SIGCHLD in response to	2243	Child watchers trigger when your process receives a SIGCHLD in response to
1548	some child status changes (most typically when a child of yours dies). It	2244	some child status changes (most typically when a child of yours dies or
1549	is permissible to install a child watcher I<after> the child has been	2245	exits). It is permissible to install a child watcher I<after> the child
1550	forked (which implies it might have already exited), as long as the event	2246	has been forked (which implies it might have already exited), as long
1551	loop isn't entered (or is continued from a watcher).	2247	as the event loop isn't entered (or is continued from a watcher), i.e.,
		2248	forking and then immediately registering a watcher for the child is fine,
		2249	but forking and registering a watcher a few event loop iterations later or
		2250	in the next callback invocation is not.
1552		2251
1553	Only the default event loop is capable of handling signals, and therefore	2252	Only the default event loop is capable of handling signals, and therefore
1554	you can only register child watchers in the default event loop.	2253	you can only register child watchers in the default event loop.
1555		2254
		2255	Due to some design glitches inside libev, child watchers will always be
		2256	handled at maximum priority (their priority is set to C<EV_MAXPRI> by
		2257	libev)
		2258
1556	=head3 Process Interaction	2259	=head3 Process Interaction
1557		2260
1558	Libev grabs C<SIGCHLD> as soon as the default event loop is	2261	Libev grabs C<SIGCHLD> as soon as the default event loop is
1559	initialised. This is necessary to guarantee proper behaviour even if	2262	initialised. This is necessary to guarantee proper behaviour even if the
1560	the first child watcher is started after the child exits. The occurrence	2263	first child watcher is started after the child exits. The occurrence
1561	of C<SIGCHLD> is recorded asynchronously, but child reaping is done	2264	of C<SIGCHLD> is recorded asynchronously, but child reaping is done
1562	synchronously as part of the event loop processing. Libev always reaps all	2265	synchronously as part of the event loop processing. Libev always reaps all
1563	children, even ones not watched.	2266	children, even ones not watched.
1564		2267
1565	=head3 Overriding the Built-In Processing	2268	=head3 Overriding the Built-In Processing
…		…
1569	handler, you can override it easily by installing your own handler for	2272	handler, you can override it easily by installing your own handler for
1570	C<SIGCHLD> after initialising the default loop, and making sure the	2273	C<SIGCHLD> after initialising the default loop, and making sure the
1571	default loop never gets destroyed. You are encouraged, however, to use an	2274	default loop never gets destroyed. You are encouraged, however, to use an
1572	event-based approach to child reaping and thus use libev's support for	2275	event-based approach to child reaping and thus use libev's support for
1573	that, so other libev users can use C<ev_child> watchers freely.	2276	that, so other libev users can use C<ev_child> watchers freely.
		2277
		2278	=head3 Stopping the Child Watcher
		2279
		2280	Currently, the child watcher never gets stopped, even when the
		2281	child terminates, so normally one needs to stop the watcher in the
		2282	callback. Future versions of libev might stop the watcher automatically
		2283	when a child exit is detected (calling C<ev_child_stop> twice is not a
		2284	problem).
1574		2285
1575	=head3 Watcher-Specific Functions and Data Members	2286	=head3 Watcher-Specific Functions and Data Members
1576		2287
1577	=over 4	2288	=over 4
1578		2289
…		…
1610	its completion.	2321	its completion.
1611		2322
1612	ev_child cw;	2323	ev_child cw;
1613		2324
1614	static void	2325	static void
1615	child_cb (EV_P_ struct ev_child *w, int revents)	2326	child_cb (EV_P_ ev_child *w, int revents)
1616	{	2327	{
1617	ev_child_stop (EV_A_ w);	2328	ev_child_stop (EV_A_ w);
1618	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);	2329	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);
1619	}	2330	}
1620		2331
…		…
1635		2346
1636		2347
1637	=head2 C<ev_stat> - did the file attributes just change?	2348	=head2 C<ev_stat> - did the file attributes just change?
1638		2349
1639	This watches a file system path for attribute changes. That is, it calls	2350	This watches a file system path for attribute changes. That is, it calls
1640	C<stat> regularly (or when the OS says it changed) and sees if it changed	2351	C<stat> on that path in regular intervals (or when the OS says it changed)
1641	compared to the last time, invoking the callback if it did.	2352	and sees if it changed compared to the last time, invoking the callback if
		2353	it did.
1642		2354
1643	The path does not need to exist: changing from "path exists" to "path does	2355	The path does not need to exist: changing from "path exists" to "path does
1644	not exist" is a status change like any other. The condition "path does	2356	not exist" is a status change like any other. The condition "path does not
1645	not exist" is signified by the C<st_nlink> field being zero (which is	2357	exist" (or more correctly "path cannot be stat'ed") is signified by the
1646	otherwise always forced to be at least one) and all the other fields of	2358	C<st_nlink> field being zero (which is otherwise always forced to be at
1647	the stat buffer having unspecified contents.	2359	least one) and all the other fields of the stat buffer having unspecified
		2360	contents.
1648		2361
1649	The path I<should> be absolute and I<must not> end in a slash. If it is	2362	The path I<must not> end in a slash or contain special components such as
		2363	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1650	relative and your working directory changes, the behaviour is undefined.	2364	your working directory changes, then the behaviour is undefined.
1651		2365
1652	Since there is no standard to do this, the portable implementation simply	2366	Since there is no portable change notification interface available, the
1653	calls C<stat (2)> regularly on the path to see if it changed somehow. You	2367	portable implementation simply calls C<stat(2)> regularly on the path
1654	can specify a recommended polling interval for this case. If you specify	2368	to see if it changed somehow. You can specify a recommended polling
1655	a polling interval of C<0> (highly recommended!) then a I<suitable,	2369	interval for this case. If you specify a polling interval of C<0> (highly
1656	unspecified default> value will be used (which you can expect to be around	2370	recommended!) then a I<suitable, unspecified default> value will be used
1657	five seconds, although this might change dynamically). Libev will also	2371	(which you can expect to be around five seconds, although this might
1658	impose a minimum interval which is currently around C<0.1>, but thats	2372	change dynamically). Libev will also impose a minimum interval which is
1659	usually overkill.	2373	currently around C<0.1>, but that's usually overkill.
1660		2374
1661	This watcher type is not meant for massive numbers of stat watchers,	2375	This watcher type is not meant for massive numbers of stat watchers,
1662	as even with OS-supported change notifications, this can be	2376	as even with OS-supported change notifications, this can be
1663	resource-intensive.	2377	resource-intensive.
1664		2378
1665	At the time of this writing, only the Linux inotify interface is	2379	At the time of this writing, the only OS-specific interface implemented
1666	implemented (implementing kqueue support is left as an exercise for the	2380	is the Linux inotify interface (implementing kqueue support is left as an
1667	reader, note, however, that the author sees no way of implementing ev_stat	2381	exercise for the reader. Note, however, that the author sees no way of
1668	semantics with kqueue). Inotify will be used to give hints only and should	2382	implementing C<ev_stat> semantics with kqueue, except as a hint).
1669	not change the semantics of C<ev_stat> watchers, which means that libev
1670	sometimes needs to fall back to regular polling again even with inotify,
1671	but changes are usually detected immediately, and if the file exists there
1672	will be no polling.
1673		2383
1674	=head3 ABI Issues (Largefile Support)	2384	=head3 ABI Issues (Largefile Support)
1675		2385
1676	Libev by default (unless the user overrides this) uses the default	2386	Libev by default (unless the user overrides this) uses the default
1677	compilation environment, which means that on systems with large file	2387	compilation environment, which means that on systems with large file
1678	support disabled by default, you get the 32 bit version of the stat	2388	support disabled by default, you get the 32 bit version of the stat
1679	structure. When using the library from programs that change the ABI to	2389	structure. When using the library from programs that change the ABI to
1680	use 64 bit file offsets the programs will fail. In that case you have to	2390	use 64 bit file offsets the programs will fail. In that case you have to
1681	compile libev with the same flags to get binary compatibility. This is	2391	compile libev with the same flags to get binary compatibility. This is
1682	obviously the case with any flags that change the ABI, but the problem is	2392	obviously the case with any flags that change the ABI, but the problem is
1683	most noticeably disabled with ev_stat and large file support.	2393	most noticeably displayed with ev_stat and large file support.
1684		2394
1685	The solution for this is to lobby your distribution maker to make large	2395	The solution for this is to lobby your distribution maker to make large
1686	file interfaces available by default (as e.g. FreeBSD does) and not	2396	file interfaces available by default (as e.g. FreeBSD does) and not
1687	optional. Libev cannot simply switch on large file support because it has	2397	optional. Libev cannot simply switch on large file support because it has
1688	to exchange stat structures with application programs compiled using the	2398	to exchange stat structures with application programs compiled using the
1689	default compilation environment.	2399	default compilation environment.
1690		2400
1691	=head3 Inotify	2401	=head3 Inotify and Kqueue
1692		2402
1693	When C<inotify (7)> support has been compiled into libev (generally only	2403	When C<inotify (7)> support has been compiled into libev and present at
1694	available on Linux) and present at runtime, it will be used to speed up	2404	runtime, it will be used to speed up change detection where possible. The
1695	change detection where possible. The inotify descriptor will be created lazily	2405	inotify descriptor will be created lazily when the first C<ev_stat>
1696	when the first C<ev_stat> watcher is being started.	2406	watcher is being started.
1697		2407
1698	Inotify presence does not change the semantics of C<ev_stat> watchers	2408	Inotify presence does not change the semantics of C<ev_stat> watchers
1699	except that changes might be detected earlier, and in some cases, to avoid	2409	except that changes might be detected earlier, and in some cases, to avoid
1700	making regular C<stat> calls. Even in the presence of inotify support	2410	making regular C<stat> calls. Even in the presence of inotify support
1701	there are many cases where libev has to resort to regular C<stat> polling.	2411	there are many cases where libev has to resort to regular C<stat> polling,
		2412	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		2413	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		2414	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		2415	xfs are fully working) libev usually gets away without polling.
1702		2416
1703	(There is no support for kqueue, as apparently it cannot be used to	2417	There is no support for kqueue, as apparently it cannot be used to
1704	implement this functionality, due to the requirement of having a file	2418	implement this functionality, due to the requirement of having a file
1705	descriptor open on the object at all times).	2419	descriptor open on the object at all times, and detecting renames, unlinks
		2420	etc. is difficult.
		2421
		2422	=head3 C<stat ()> is a synchronous operation
		2423
		2424	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2425	the process. The exception are C<ev_stat> watchers - those call C<stat
		2426	()>, which is a synchronous operation.
		2427
		2428	For local paths, this usually doesn't matter: unless the system is very
		2429	busy or the intervals between stat's are large, a stat call will be fast,
		2430	as the path data is usually in memory already (except when starting the
		2431	watcher).
		2432
		2433	For networked file systems, calling C<stat ()> can block an indefinite
		2434	time due to network issues, and even under good conditions, a stat call
		2435	often takes multiple milliseconds.
		2436
		2437	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2438	paths, although this is fully supported by libev.
1706		2439
1707	=head3 The special problem of stat time resolution	2440	=head3 The special problem of stat time resolution
1708		2441
1709	The C<stat ()> system call only supports full-second resolution portably, and	2442	The C<stat ()> system call only supports full-second resolution portably,
1710	even on systems where the resolution is higher, many file systems still	2443	and even on systems where the resolution is higher, most file systems
1711	only support whole seconds.	2444	still only support whole seconds.
1712		2445
1713	That means that, if the time is the only thing that changes, you can	2446	That means that, if the time is the only thing that changes, you can
1714	easily miss updates: on the first update, C<ev_stat> detects a change and	2447	easily miss updates: on the first update, C<ev_stat> detects a change and
1715	calls your callback, which does something. When there is another update	2448	calls your callback, which does something. When there is another update
1716	within the same second, C<ev_stat> will be unable to detect it as the stat	2449	within the same second, C<ev_stat> will be unable to detect unless the
1717	data does not change.	2450	stat data does change in other ways (e.g. file size).
1718		2451
1719	The solution to this is to delay acting on a change for slightly more	2452	The solution to this is to delay acting on a change for slightly more
1720	than a second (or till slightly after the next full second boundary), using	2453	than a second (or till slightly after the next full second boundary), using
1721	a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);	2454	a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);
1722	ev_timer_again (loop, w)>).	2455	ev_timer_again (loop, w)>).
…		…
1742	C<path>. The C<interval> is a hint on how quickly a change is expected to	2475	C<path>. The C<interval> is a hint on how quickly a change is expected to
1743	be detected and should normally be specified as C<0> to let libev choose	2476	be detected and should normally be specified as C<0> to let libev choose
1744	a suitable value. The memory pointed to by C<path> must point to the same	2477	a suitable value. The memory pointed to by C<path> must point to the same
1745	path for as long as the watcher is active.	2478	path for as long as the watcher is active.
1746		2479
1747	The callback will receive C<EV_STAT> when a change was detected, relative	2480	The callback will receive an C<EV_STAT> event when a change was detected,
1748	to the attributes at the time the watcher was started (or the last change	2481	relative to the attributes at the time the watcher was started (or the
1749	was detected).	2482	last change was detected).
1750		2483
1751	=item ev_stat_stat (loop, ev_stat *)	2484	=item ev_stat_stat (loop, ev_stat *)
1752		2485
1753	Updates the stat buffer immediately with new values. If you change the	2486	Updates the stat buffer immediately with new values. If you change the
1754	watched path in your callback, you could call this function to avoid	2487	watched path in your callback, you could call this function to avoid
…		…
1837		2570
1838		2571
1839	=head2 C<ev_idle> - when you've got nothing better to do...	2572	=head2 C<ev_idle> - when you've got nothing better to do...
1840		2573
1841	Idle watchers trigger events when no other events of the same or higher	2574	Idle watchers trigger events when no other events of the same or higher
1842	priority are pending (prepare, check and other idle watchers do not	2575	priority are pending (prepare, check and other idle watchers do not count
1843	count).	2576	as receiving "events").
1844		2577
1845	That is, as long as your process is busy handling sockets or timeouts	2578	That is, as long as your process is busy handling sockets or timeouts
1846	(or even signals, imagine) of the same or higher priority it will not be	2579	(or even signals, imagine) of the same or higher priority it will not be
1847	triggered. But when your process is idle (or only lower-priority watchers	2580	triggered. But when your process is idle (or only lower-priority watchers
1848	are pending), the idle watchers are being called once per event loop	2581	are pending), the idle watchers are being called once per event loop
…		…
1859		2592
1860	=head3 Watcher-Specific Functions and Data Members	2593	=head3 Watcher-Specific Functions and Data Members
1861		2594
1862	=over 4	2595	=over 4
1863		2596
1864	=item ev_idle_init (ev_signal *, callback)	2597	=item ev_idle_init (ev_idle *, callback)
1865		2598
1866	Initialises and configures the idle watcher - it has no parameters of any	2599	Initialises and configures the idle watcher - it has no parameters of any
1867	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	2600	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
1868	believe me.	2601	believe me.
1869		2602
…		…
1873		2606
1874	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the	2607	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
1875	callback, free it. Also, use no error checking, as usual.	2608	callback, free it. Also, use no error checking, as usual.
1876		2609
1877	static void	2610	static void
1878	idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)	2611	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)
1879	{	2612	{
1880	free (w);	2613	free (w);
1881	// now do something you wanted to do when the program has	2614	// now do something you wanted to do when the program has
1882	// no longer anything immediate to do.	2615	// no longer anything immediate to do.
1883	}	2616	}
1884		2617
1885	struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));	2618	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
1886	ev_idle_init (idle_watcher, idle_cb);	2619	ev_idle_init (idle_watcher, idle_cb);
1887	ev_idle_start (loop, idle_cb);	2620	ev_idle_start (loop, idle_watcher);
1888		2621
1889		2622
1890	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2623	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
1891		2624
1892	Prepare and check watchers are usually (but not always) used in tandem:	2625	Prepare and check watchers are usually (but not always) used in pairs:
1893	prepare watchers get invoked before the process blocks and check watchers	2626	prepare watchers get invoked before the process blocks and check watchers
1894	afterwards.	2627	afterwards.
1895		2628
1896	You I<must not> call C<ev_loop> or similar functions that enter	2629	You I<must not> call C<ev_loop> or similar functions that enter
1897	the current event loop from either C<ev_prepare> or C<ev_check>	2630	the current event loop from either C<ev_prepare> or C<ev_check>
…		…
1900	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2633	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
1901	C<ev_check> so if you have one watcher of each kind they will always be	2634	C<ev_check> so if you have one watcher of each kind they will always be
1902	called in pairs bracketing the blocking call.	2635	called in pairs bracketing the blocking call.
1903		2636
1904	Their main purpose is to integrate other event mechanisms into libev and	2637	Their main purpose is to integrate other event mechanisms into libev and
1905	their use is somewhat advanced. This could be used, for example, to track	2638	their use is somewhat advanced. They could be used, for example, to track
1906	variable changes, implement your own watchers, integrate net-snmp or a	2639	variable changes, implement your own watchers, integrate net-snmp or a
1907	coroutine library and lots more. They are also occasionally useful if	2640	coroutine library and lots more. They are also occasionally useful if
1908	you cache some data and want to flush it before blocking (for example,	2641	you cache some data and want to flush it before blocking (for example,
1909	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>	2642	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>
1910	watcher).	2643	watcher).
1911		2644
1912	This is done by examining in each prepare call which file descriptors need	2645	This is done by examining in each prepare call which file descriptors
1913	to be watched by the other library, registering C<ev_io> watchers for	2646	need to be watched by the other library, registering C<ev_io> watchers
1914	them and starting an C<ev_timer> watcher for any timeouts (many libraries	2647	for them and starting an C<ev_timer> watcher for any timeouts (many
1915	provide just this functionality). Then, in the check watcher you check for	2648	libraries provide exactly this functionality). Then, in the check watcher,
1916	any events that occurred (by checking the pending status of all watchers	2649	you check for any events that occurred (by checking the pending status
1917	and stopping them) and call back into the library. The I/O and timer	2650	of all watchers and stopping them) and call back into the library. The
1918	callbacks will never actually be called (but must be valid nevertheless,	2651	I/O and timer callbacks will never actually be called (but must be valid
1919	because you never know, you know?).	2652	nevertheless, because you never know, you know?).
1920		2653
1921	As another example, the Perl Coro module uses these hooks to integrate	2654	As another example, the Perl Coro module uses these hooks to integrate
1922	coroutines into libev programs, by yielding to other active coroutines	2655	coroutines into libev programs, by yielding to other active coroutines
1923	during each prepare and only letting the process block if no coroutines	2656	during each prepare and only letting the process block if no coroutines
1924	are ready to run (it's actually more complicated: it only runs coroutines	2657	are ready to run (it's actually more complicated: it only runs coroutines
…		…
1927	loop from blocking if lower-priority coroutines are active, thus mapping	2660	loop from blocking if lower-priority coroutines are active, thus mapping
1928	low-priority coroutines to idle/background tasks).	2661	low-priority coroutines to idle/background tasks).
1929		2662
1930	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)	2663	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)
1931	priority, to ensure that they are being run before any other watchers	2664	priority, to ensure that they are being run before any other watchers
		2665	after the poll (this doesn't matter for C<ev_prepare> watchers).
		2666
1932	after the poll. Also, C<ev_check> watchers (and C<ev_prepare> watchers,	2667	Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not
1933	too) should not activate ("feed") events into libev. While libev fully	2668	activate ("feed") events into libev. While libev fully supports this, they
1934	supports this, they might get executed before other C<ev_check> watchers	2669	might get executed before other C<ev_check> watchers did their job. As
1935	did their job. As C<ev_check> watchers are often used to embed other	2670	C<ev_check> watchers are often used to embed other (non-libev) event
1936	(non-libev) event loops those other event loops might be in an unusable	2671	loops those other event loops might be in an unusable state until their
1937	state until their C<ev_check> watcher ran (always remind yourself to	2672	C<ev_check> watcher ran (always remind yourself to coexist peacefully with
1938	coexist peacefully with others).	2673	others).
1939		2674
1940	=head3 Watcher-Specific Functions and Data Members	2675	=head3 Watcher-Specific Functions and Data Members
1941		2676
1942	=over 4	2677	=over 4
1943		2678
…		…
1945		2680
1946	=item ev_check_init (ev_check *, callback)	2681	=item ev_check_init (ev_check *, callback)
1947		2682
1948	Initialises and configures the prepare or check watcher - they have no	2683	Initialises and configures the prepare or check watcher - they have no
1949	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>	2684	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>
1950	macros, but using them is utterly, utterly and completely pointless.	2685	macros, but using them is utterly, utterly, utterly and completely
		2686	pointless.
1951		2687
1952	=back	2688	=back
1953		2689
1954	=head3 Examples	2690	=head3 Examples
1955		2691
…		…
1968		2704
1969	static ev_io iow [nfd];	2705	static ev_io iow [nfd];
1970	static ev_timer tw;	2706	static ev_timer tw;
1971		2707
1972	static void	2708	static void
1973	io_cb (ev_loop *loop, ev_io *w, int revents)	2709	io_cb (struct ev_loop *loop, ev_io *w, int revents)
1974	{	2710	{
1975	}	2711	}
1976		2712
1977	// create io watchers for each fd and a timer before blocking	2713	// create io watchers for each fd and a timer before blocking
1978	static void	2714	static void
1979	adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)	2715	adns_prepare_cb (struct ev_loop *loop, ev_prepare *w, int revents)
1980	{	2716	{
1981	int timeout = 3600000;	2717	int timeout = 3600000;
1982	struct pollfd fds [nfd];	2718	struct pollfd fds [nfd];
1983	// actual code will need to loop here and realloc etc.	2719	// actual code will need to loop here and realloc etc.
1984	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	2720	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1985		2721
1986	/* the callback is illegal, but won't be called as we stop during check */	2722	/* the callback is illegal, but won't be called as we stop during check */
1987	ev_timer_init (&tw, 0, timeout * 1e-3);	2723	ev_timer_init (&tw, 0, timeout * 1e-3, 0.);
1988	ev_timer_start (loop, &tw);	2724	ev_timer_start (loop, &tw);
1989		2725
1990	// create one ev_io per pollfd	2726	// create one ev_io per pollfd
1991	for (int i = 0; i < nfd; ++i)	2727	for (int i = 0; i < nfd; ++i)
1992	{	2728	{
…		…
1999	}	2735	}
2000	}	2736	}
2001		2737
2002	// stop all watchers after blocking	2738	// stop all watchers after blocking
2003	static void	2739	static void
2004	adns_check_cb (ev_loop *loop, ev_check *w, int revents)	2740	adns_check_cb (struct ev_loop *loop, ev_check *w, int revents)
2005	{	2741	{
2006	ev_timer_stop (loop, &tw);	2742	ev_timer_stop (loop, &tw);
2007		2743
2008	for (int i = 0; i < nfd; ++i)	2744	for (int i = 0; i < nfd; ++i)
2009	{	2745	{
…		…
2048	}	2784	}
2049		2785
2050	// do not ever call adns_afterpoll	2786	// do not ever call adns_afterpoll
2051		2787
2052	Method 4: Do not use a prepare or check watcher because the module you	2788	Method 4: Do not use a prepare or check watcher because the module you
2053	want to embed is too inflexible to support it. Instead, you can override	2789	want to embed is not flexible enough to support it. Instead, you can
2054	their poll function. The drawback with this solution is that the main	2790	override their poll function. The drawback with this solution is that the
2055	loop is now no longer controllable by EV. The C<Glib::EV> module does	2791	main loop is now no longer controllable by EV. The C<Glib::EV> module uses
2056	this.	2792	this approach, effectively embedding EV as a client into the horrible
		2793	libglib event loop.
2057		2794
2058	static gint	2795	static gint
2059	event_poll_func (GPollFD *fds, guint nfds, gint timeout)	2796	event_poll_func (GPollFD *fds, guint nfds, gint timeout)
2060	{	2797	{
2061	int got_events = 0;	2798	int got_events = 0;
…		…
2092	prioritise I/O.	2829	prioritise I/O.
2093		2830
2094	As an example for a bug workaround, the kqueue backend might only support	2831	As an example for a bug workaround, the kqueue backend might only support
2095	sockets on some platform, so it is unusable as generic backend, but you	2832	sockets on some platform, so it is unusable as generic backend, but you
2096	still want to make use of it because you have many sockets and it scales	2833	still want to make use of it because you have many sockets and it scales
2097	so nicely. In this case, you would create a kqueue-based loop and embed it	2834	so nicely. In this case, you would create a kqueue-based loop and embed
2098	into your default loop (which might use e.g. poll). Overall operation will	2835	it into your default loop (which might use e.g. poll). Overall operation
2099	be a bit slower because first libev has to poll and then call kevent, but	2836	will be a bit slower because first libev has to call C<poll> and then
2100	at least you can use both at what they are best.	2837	C<kevent>, but at least you can use both mechanisms for what they are
		2838	best: C<kqueue> for scalable sockets and C<poll> if you want it to work :)
2101		2839
2102	As for prioritising I/O: rarely you have the case where some fds have	2840	As for prioritising I/O: under rare circumstances you have the case where
2103	to be watched and handled very quickly (with low latency), and even	2841	some fds have to be watched and handled very quickly (with low latency),
2104	priorities and idle watchers might have too much overhead. In this case	2842	and even priorities and idle watchers might have too much overhead. In
2105	you would put all the high priority stuff in one loop and all the rest in	2843	this case you would put all the high priority stuff in one loop and all
2106	a second one, and embed the second one in the first.	2844	the rest in a second one, and embed the second one in the first.
2107		2845
2108	As long as the watcher is active, the callback will be invoked every time	2846	As long as the watcher is active, the callback will be invoked every
2109	there might be events pending in the embedded loop. The callback must then	2847	time there might be events pending in the embedded loop. The callback
2110	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke	2848	must then call C<ev_embed_sweep (mainloop, watcher)> to make a single
2111	their callbacks (you could also start an idle watcher to give the embedded	2849	sweep and invoke their callbacks (the callback doesn't need to invoke the
2112	loop strictly lower priority for example). You can also set the callback	2850	C<ev_embed_sweep> function directly, it could also start an idle watcher
2113	to C<0>, in which case the embed watcher will automatically execute the	2851	to give the embedded loop strictly lower priority for example).
2114	embedded loop sweep.
2115		2852
2116	As long as the watcher is started it will automatically handle events. The	2853	You can also set the callback to C<0>, in which case the embed watcher
2117	callback will be invoked whenever some events have been handled. You can	2854	will automatically execute the embedded loop sweep whenever necessary.
2118	set the callback to C<0> to avoid having to specify one if you are not
2119	interested in that.
2120		2855
2121	Also, there have not currently been made special provisions for forking:	2856	Fork detection will be handled transparently while the C<ev_embed> watcher
2122	when you fork, you not only have to call C<ev_loop_fork> on both loops,	2857	is active, i.e., the embedded loop will automatically be forked when the
2123	but you will also have to stop and restart any C<ev_embed> watchers	2858	embedding loop forks. In other cases, the user is responsible for calling
2124	yourself.	2859	C<ev_loop_fork> on the embedded loop.
2125		2860
2126	Unfortunately, not all backends are embeddable, only the ones returned by	2861	Unfortunately, not all backends are embeddable: only the ones returned by
2127	C<ev_embeddable_backends> are, which, unfortunately, does not include any	2862	C<ev_embeddable_backends> are, which, unfortunately, does not include any
2128	portable one.	2863	portable one.
2129		2864
2130	So when you want to use this feature you will always have to be prepared	2865	So when you want to use this feature you will always have to be prepared
2131	that you cannot get an embeddable loop. The recommended way to get around	2866	that you cannot get an embeddable loop. The recommended way to get around
2132	this is to have a separate variables for your embeddable loop, try to	2867	this is to have a separate variables for your embeddable loop, try to
2133	create it, and if that fails, use the normal loop for everything.	2868	create it, and if that fails, use the normal loop for everything.
		2869
		2870	=head3 C<ev_embed> and fork
		2871
		2872	While the C<ev_embed> watcher is running, forks in the embedding loop will
		2873	automatically be applied to the embedded loop as well, so no special
		2874	fork handling is required in that case. When the watcher is not running,
		2875	however, it is still the task of the libev user to call C<ev_loop_fork ()>
		2876	as applicable.
2134		2877
2135	=head3 Watcher-Specific Functions and Data Members	2878	=head3 Watcher-Specific Functions and Data Members
2136		2879
2137	=over 4	2880	=over 4
2138		2881
…		…
2166	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be	2909	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be
2167	used).	2910	used).
2168		2911
2169	struct ev_loop *loop_hi = ev_default_init (0);	2912	struct ev_loop *loop_hi = ev_default_init (0);
2170	struct ev_loop *loop_lo = 0;	2913	struct ev_loop *loop_lo = 0;
2171	struct ev_embed embed;	2914	ev_embed embed;
2172		2915
2173	// see if there is a chance of getting one that works	2916	// see if there is a chance of getting one that works
2174	// (remember that a flags value of 0 means autodetection)	2917	// (remember that a flags value of 0 means autodetection)
2175	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()	2918	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
2176	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())	2919	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
…		…
2190	kqueue implementation). Store the kqueue/socket-only event loop in	2933	kqueue implementation). Store the kqueue/socket-only event loop in
2191	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).	2934	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
2192		2935
2193	struct ev_loop *loop = ev_default_init (0);	2936	struct ev_loop *loop = ev_default_init (0);
2194	struct ev_loop *loop_socket = 0;	2937	struct ev_loop *loop_socket = 0;
2195	struct ev_embed embed;	2938	ev_embed embed;
2196		2939
2197	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)	2940	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
2198	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))	2941	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
2199	{	2942	{
2200	ev_embed_init (&embed, 0, loop_socket);	2943	ev_embed_init (&embed, 0, loop_socket);
…		…
2215	event loop blocks next and before C<ev_check> watchers are being called,	2958	event loop blocks next and before C<ev_check> watchers are being called,
2216	and only in the child after the fork. If whoever good citizen calling	2959	and only in the child after the fork. If whoever good citizen calling
2217	C<ev_default_fork> cheats and calls it in the wrong process, the fork	2960	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2218	handlers will be invoked, too, of course.	2961	handlers will be invoked, too, of course.
2219		2962
		2963	=head3 The special problem of life after fork - how is it possible?
		2964
		2965	Most uses of C<fork()> consist of forking, then some simple calls to ste
		2966	up/change the process environment, followed by a call to C<exec()>. This
		2967	sequence should be handled by libev without any problems.
		2968
		2969	This changes when the application actually wants to do event handling
		2970	in the child, or both parent in child, in effect "continuing" after the
		2971	fork.
		2972
		2973	The default mode of operation (for libev, with application help to detect
		2974	forks) is to duplicate all the state in the child, as would be expected
		2975	when I<either> the parent I<or> the child process continues.
		2976
		2977	When both processes want to continue using libev, then this is usually the
		2978	wrong result. In that case, usually one process (typically the parent) is
		2979	supposed to continue with all watchers in place as before, while the other
		2980	process typically wants to start fresh, i.e. without any active watchers.
		2981
		2982	The cleanest and most efficient way to achieve that with libev is to
		2983	simply create a new event loop, which of course will be "empty", and
		2984	use that for new watchers. This has the advantage of not touching more
		2985	memory than necessary, and thus avoiding the copy-on-write, and the
		2986	disadvantage of having to use multiple event loops (which do not support
		2987	signal watchers).
		2988
		2989	When this is not possible, or you want to use the default loop for
		2990	other reasons, then in the process that wants to start "fresh", call
		2991	C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying
		2992	the default loop will "orphan" (not stop) all registered watchers, so you
		2993	have to be careful not to execute code that modifies those watchers. Note
		2994	also that in that case, you have to re-register any signal watchers.
		2995
2220	=head3 Watcher-Specific Functions and Data Members	2996	=head3 Watcher-Specific Functions and Data Members
2221		2997
2222	=over 4	2998	=over 4
2223		2999
2224	=item ev_fork_init (ev_signal *, callback)	3000	=item ev_fork_init (ev_signal *, callback)
…		…
2253	=head3 Queueing	3029	=head3 Queueing
2254		3030
2255	C<ev_async> does not support queueing of data in any way. The reason	3031	C<ev_async> does not support queueing of data in any way. The reason
2256	is that the author does not know of a simple (or any) algorithm for a	3032	is that the author does not know of a simple (or any) algorithm for a
2257	multiple-writer-single-reader queue that works in all cases and doesn't	3033	multiple-writer-single-reader queue that works in all cases and doesn't
2258	need elaborate support such as pthreads.	3034	need elaborate support such as pthreads or unportable memory access
		3035	semantics.
2259		3036
2260	That means that if you want to queue data, you have to provide your own	3037	That means that if you want to queue data, you have to provide your own
2261	queue. But at least I can tell you would implement locking around your	3038	queue. But at least I can tell you how to implement locking around your
2262	queue:	3039	queue:
2263		3040
2264	=over 4	3041	=over 4
2265		3042
2266	=item queueing from a signal handler context	3043	=item queueing from a signal handler context
2267		3044
2268	To implement race-free queueing, you simply add to the queue in the signal	3045	To implement race-free queueing, you simply add to the queue in the signal
2269	handler but you block the signal handler in the watcher callback. Here is an example that does that for	3046	handler but you block the signal handler in the watcher callback. Here is
2270	some fictitious SIGUSR1 handler:	3047	an example that does that for some fictitious SIGUSR1 handler:
2271		3048
2272	static ev_async mysig;	3049	static ev_async mysig;
2273		3050
2274	static void	3051	static void
2275	sigusr1_handler (void)	3052	sigusr1_handler (void)
…		…
2341	=over 4	3118	=over 4
2342		3119
2343	=item ev_async_init (ev_async *, callback)	3120	=item ev_async_init (ev_async *, callback)
2344		3121
2345	Initialises and configures the async watcher - it has no parameters of any	3122	Initialises and configures the async watcher - it has no parameters of any
2346	kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless,	3123	kind. There is a C<ev_async_set> macro, but using it is utterly pointless,
2347	believe me.	3124	trust me.
2348		3125
2349	=item ev_async_send (loop, ev_async *)	3126	=item ev_async_send (loop, ev_async *)
2350		3127
2351	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3128	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
2352	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3129	an C<EV_ASYNC> event on the watcher into the event loop. Unlike
2353	C<ev_feed_event>, this call is safe to do in other threads, signal or	3130	C<ev_feed_event>, this call is safe to do from other threads, signal or
2354	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3131	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding
2355	section below on what exactly this means).	3132	section below on what exactly this means).
2356		3133
		3134	Note that, as with other watchers in libev, multiple events might get
		3135	compressed into a single callback invocation (another way to look at this
		3136	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,
		3137	reset when the event loop detects that).
		3138
2357	This call incurs the overhead of a system call only once per loop iteration,	3139	This call incurs the overhead of a system call only once per event loop
2358	so while the overhead might be noticeable, it doesn't apply to repeated	3140	iteration, so while the overhead might be noticeable, it doesn't apply to
2359	calls to C<ev_async_send>.	3141	repeated calls to C<ev_async_send> for the same event loop.
2360		3142
2361	=item bool = ev_async_pending (ev_async *)	3143	=item bool = ev_async_pending (ev_async *)
2362		3144
2363	Returns a non-zero value when C<ev_async_send> has been called on the	3145	Returns a non-zero value when C<ev_async_send> has been called on the
2364	watcher but the event has not yet been processed (or even noted) by the	3146	watcher but the event has not yet been processed (or even noted) by the
…		…
2367	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When	3149	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When
2368	the loop iterates next and checks for the watcher to have become active,	3150	the loop iterates next and checks for the watcher to have become active,
2369	it will reset the flag again. C<ev_async_pending> can be used to very	3151	it will reset the flag again. C<ev_async_pending> can be used to very
2370	quickly check whether invoking the loop might be a good idea.	3152	quickly check whether invoking the loop might be a good idea.
2371		3153
2372	Not that this does I<not> check whether the watcher itself is pending, only	3154	Not that this does I<not> check whether the watcher itself is pending,
2373	whether it has been requested to make this watcher pending.	3155	only whether it has been requested to make this watcher pending: there
		3156	is a time window between the event loop checking and resetting the async
		3157	notification, and the callback being invoked.
2374		3158
2375	=back	3159	=back
2376		3160
2377		3161
2378	=head1 OTHER FUNCTIONS	3162	=head1 OTHER FUNCTIONS
…		…
2382	=over 4	3166	=over 4
2383		3167
2384	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)	3168	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)
2385		3169
2386	This function combines a simple timer and an I/O watcher, calls your	3170	This function combines a simple timer and an I/O watcher, calls your
2387	callback on whichever event happens first and automatically stop both	3171	callback on whichever event happens first and automatically stops both
2388	watchers. This is useful if you want to wait for a single event on an fd	3172	watchers. This is useful if you want to wait for a single event on an fd
2389	or timeout without having to allocate/configure/start/stop/free one or	3173	or timeout without having to allocate/configure/start/stop/free one or
2390	more watchers yourself.	3174	more watchers yourself.
2391		3175
2392	If C<fd> is less than 0, then no I/O watcher will be started and events	3176	If C<fd> is less than 0, then no I/O watcher will be started and the
2393	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and	3177	C<events> argument is being ignored. Otherwise, an C<ev_io> watcher for
2394	C<events> set will be created and started.	3178	the given C<fd> and C<events> set will be created and started.
2395		3179
2396	If C<timeout> is less than 0, then no timeout watcher will be	3180	If C<timeout> is less than 0, then no timeout watcher will be
2397	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	3181	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
2398	repeat = 0) will be started. While C<0> is a valid timeout, it is of	3182	repeat = 0) will be started. C<0> is a valid timeout.
2399	dubious value.
2400		3183
2401	The callback has the type C<void (*cb)(int revents, void *arg)> and gets	3184	The callback has the type C<void (*cb)(int revents, void *arg)> and gets
2402	passed an C<revents> set like normal event callbacks (a combination of	3185	passed an C<revents> set like normal event callbacks (a combination of
2403	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	3186	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>
2404	value passed to C<ev_once>:	3187	value passed to C<ev_once>. Note that it is possible to receive I<both>
		3188	a timeout and an io event at the same time - you probably should give io
		3189	events precedence.
		3190
		3191	Example: wait up to ten seconds for data to appear on STDIN_FILENO.
2405		3192
2406	static void stdin_ready (int revents, void *arg)	3193	static void stdin_ready (int revents, void *arg)
2407	{	3194	{
		3195	if (revents & EV_READ)
		3196	/* stdin might have data for us, joy! */;
2408	if (revents & EV_TIMEOUT)	3197	else if (revents & EV_TIMEOUT)
2409	/* doh, nothing entered */;	3198	/* doh, nothing entered */;
2410	else if (revents & EV_READ)
2411	/* stdin might have data for us, joy! */;
2412	}	3199	}
2413		3200
2414	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3201	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
2415		3202
2416	=item ev_feed_event (ev_loop *, watcher *, int revents)
2417
2418	Feeds the given event set into the event loop, as if the specified event
2419	had happened for the specified watcher (which must be a pointer to an
2420	initialised but not necessarily started event watcher).
2421
2422	=item ev_feed_fd_event (ev_loop *, int fd, int revents)	3203	=item ev_feed_fd_event (loop, int fd, int revents)
2423		3204
2424	Feed an event on the given fd, as if a file descriptor backend detected	3205	Feed an event on the given fd, as if a file descriptor backend detected
2425	the given events it.	3206	the given events it.
2426		3207
2427	=item ev_feed_signal_event (ev_loop *loop, int signum)	3208	=item ev_feed_signal_event (loop, int signum)
2428		3209
2429	Feed an event as if the given signal occurred (C<loop> must be the default	3210	Feed an event as if the given signal occurred (C<loop> must be the default
2430	loop!).	3211	loop!).
2431		3212
2432	=back	3213	=back
…		…
2512		3293
2513	=over 4	3294	=over 4
2514		3295
2515	=item ev::TYPE::TYPE ()	3296	=item ev::TYPE::TYPE ()
2516		3297
2517	=item ev::TYPE::TYPE (struct ev_loop *)	3298	=item ev::TYPE::TYPE (loop)
2518		3299
2519	=item ev::TYPE::~TYPE	3300	=item ev::TYPE::~TYPE
2520		3301
2521	The constructor (optionally) takes an event loop to associate the watcher	3302	The constructor (optionally) takes an event loop to associate the watcher
2522	with. If it is omitted, it will use C<EV_DEFAULT>.	3303	with. If it is omitted, it will use C<EV_DEFAULT>.
…		…
2554		3335
2555	myclass obj;	3336	myclass obj;
2556	ev::io iow;	3337	ev::io iow;
2557	iow.set <myclass, &myclass::io_cb> (&obj);	3338	iow.set <myclass, &myclass::io_cb> (&obj);
2558		3339
		3340	=item w->set (object *)
		3341
		3342	This is an B<experimental> feature that might go away in a future version.
		3343
		3344	This is a variation of a method callback - leaving out the method to call
		3345	will default the method to C<operator ()>, which makes it possible to use
		3346	functor objects without having to manually specify the C<operator ()> all
		3347	the time. Incidentally, you can then also leave out the template argument
		3348	list.
		3349
		3350	The C<operator ()> method prototype must be C<void operator ()(watcher &w,
		3351	int revents)>.
		3352
		3353	See the method-C<set> above for more details.
		3354
		3355	Example: use a functor object as callback.
		3356
		3357	struct myfunctor
		3358	{
		3359	void operator() (ev::io &w, int revents)
		3360	{
		3361	...
		3362	}
		3363	}
		3364
		3365	myfunctor f;
		3366
		3367	ev::io w;
		3368	w.set (&f);
		3369
2559	=item w->set<function> (void *data = 0)	3370	=item w->set<function> (void *data = 0)
2560		3371
2561	Also sets a callback, but uses a static method or plain function as	3372	Also sets a callback, but uses a static method or plain function as
2562	callback. The optional C<data> argument will be stored in the watcher's	3373	callback. The optional C<data> argument will be stored in the watcher's
2563	C<data> member and is free for you to use.	3374	C<data> member and is free for you to use.
2564		3375
2565	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.	3376	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.
2566		3377
2567	See the method-C<set> above for more details.	3378	See the method-C<set> above for more details.
2568		3379
2569	Example:	3380	Example: Use a plain function as callback.
2570		3381
2571	static void io_cb (ev::io &w, int revents) { }	3382	static void io_cb (ev::io &w, int revents) { }
2572	iow.set <io_cb> ();	3383	iow.set <io_cb> ();
2573		3384
2574	=item w->set (struct ev_loop *)	3385	=item w->set (loop)
2575		3386
2576	Associates a different C<struct ev_loop> with this watcher. You can only	3387	Associates a different C<struct ev_loop> with this watcher. You can only
2577	do this when the watcher is inactive (and not pending either).	3388	do this when the watcher is inactive (and not pending either).
2578		3389
2579	=item w->set ([arguments])	3390	=item w->set ([arguments])
…		…
2612	Example: Define a class with an IO and idle watcher, start one of them in	3423	Example: Define a class with an IO and idle watcher, start one of them in
2613	the constructor.	3424	the constructor.
2614		3425
2615	class myclass	3426	class myclass
2616	{	3427	{
2617	ev::io io; void io_cb (ev::io &w, int revents);	3428	ev::io io ; void io_cb (ev::io &w, int revents);
2618	ev:idle idle void idle_cb (ev::idle &w, int revents);	3429	ev::idle idle; void idle_cb (ev::idle &w, int revents);
2619		3430
2620	myclass (int fd)	3431	myclass (int fd)
2621	{	3432	{
2622	io .set <myclass, &myclass::io_cb > (this);	3433	io .set <myclass, &myclass::io_cb > (this);
2623	idle.set <myclass, &myclass::idle_cb> (this);	3434	idle.set <myclass, &myclass::idle_cb> (this);
…		…
2639	=item Perl	3450	=item Perl
2640		3451
2641	The EV module implements the full libev API and is actually used to test	3452	The EV module implements the full libev API and is actually used to test
2642	libev. EV is developed together with libev. Apart from the EV core module,	3453	libev. EV is developed together with libev. Apart from the EV core module,
2643	there are additional modules that implement libev-compatible interfaces	3454	there are additional modules that implement libev-compatible interfaces
2644	to C<libadns> (C<EV::ADNS>), C<Net::SNMP> (C<Net::SNMP::EV>) and the	3455	to C<libadns> (C<EV::ADNS>, but C<AnyEvent::DNS> is preferred nowadays),
2645	C<libglib> event core (C<Glib::EV> and C<EV::Glib>).	3456	C<Net::SNMP> (C<Net::SNMP::EV>) and the C<libglib> event core (C<Glib::EV>
		3457	and C<EV::Glib>).
2646		3458
2647	It can be found and installed via CPAN, its homepage is at	3459	It can be found and installed via CPAN, its homepage is at
2648	L<http://software.schmorp.de/pkg/EV>.	3460	L<http://software.schmorp.de/pkg/EV>.
2649		3461
2650	=item Python	3462	=item Python
2651		3463
2652	Python bindings can be found at L<http://code.google.com/p/pyev/>. It	3464	Python bindings can be found at L<http://code.google.com/p/pyev/>. It
2653	seems to be quite complete and well-documented. Note, however, that the	3465	seems to be quite complete and well-documented.
2654	patch they require for libev is outright dangerous as it breaks the ABI
2655	for everybody else, and therefore, should never be applied in an installed
2656	libev (if python requires an incompatible ABI then it needs to embed
2657	libev).
2658		3466
2659	=item Ruby	3467	=item Ruby
2660		3468
2661	Tony Arcieri has written a ruby extension that offers access to a subset	3469	Tony Arcieri has written a ruby extension that offers access to a subset
2662	of the libev API and adds file handle abstractions, asynchronous DNS and	3470	of the libev API and adds file handle abstractions, asynchronous DNS and
2663	more on top of it. It can be found via gem servers. Its homepage is at	3471	more on top of it. It can be found via gem servers. Its homepage is at
2664	L<http://rev.rubyforge.org/>.	3472	L<http://rev.rubyforge.org/>.
2665		3473
		3474	Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190>
		3475	makes rev work even on mingw.
		3476
		3477	=item Haskell
		3478
		3479	A haskell binding to libev is available at
		3480	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.
		3481
2666	=item D	3482	=item D
2667		3483
2668	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3484	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2669	be found at L<http://git.llucax.com.ar/?p=software/ev.d.git;a=summary>.	3485	be found at L<http://proj.llucax.com.ar/wiki/evd>.
		3486
		3487	=item Ocaml
		3488
		3489	Erkki Seppala has written Ocaml bindings for libev, to be found at
		3490	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
		3491
		3492	=item Lua
		3493
		3494	Brian Maher has written a partial interface to libev for lua (at the
		3495	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
		3496	L<http://github.com/brimworks/lua-ev>.
2670		3497
2671	=back	3498	=back
2672		3499
2673		3500
2674	=head1 MACRO MAGIC	3501	=head1 MACRO MAGIC
…		…
2775		3602
2776	#define EV_STANDALONE 1	3603	#define EV_STANDALONE 1
2777	#include "ev.h"	3604	#include "ev.h"
2778		3605
2779	Both header files and implementation files can be compiled with a C++	3606	Both header files and implementation files can be compiled with a C++
2780	compiler (at least, thats a stated goal, and breakage will be treated	3607	compiler (at least, that's a stated goal, and breakage will be treated
2781	as a bug).	3608	as a bug).
2782		3609
2783	You need the following files in your source tree, or in a directory	3610	You need the following files in your source tree, or in a directory
2784	in your include path (e.g. in libev/ when using -Ilibev):	3611	in your include path (e.g. in libev/ when using -Ilibev):
2785		3612
…		…
2828	libev.m4	3655	libev.m4
2829		3656
2830	=head2 PREPROCESSOR SYMBOLS/MACROS	3657	=head2 PREPROCESSOR SYMBOLS/MACROS
2831		3658
2832	Libev can be configured via a variety of preprocessor symbols you have to	3659	Libev can be configured via a variety of preprocessor symbols you have to
2833	define before including any of its files. The default in the absence of	3660	define before including (or compiling) any of its files. The default in
2834	autoconf is noted for every option.	3661	the absence of autoconf is documented for every option.
		3662
		3663	Symbols marked with "(h)" do not change the ABI, and can have different
		3664	values when compiling libev vs. including F<ev.h>, so it is permissible
		3665	to redefine them before including F<ev.h> without breakign compatibility
		3666	to a compiled library. All other symbols change the ABI, which means all
		3667	users of libev and the libev code itself must be compiled with compatible
		3668	settings.
2835		3669
2836	=over 4	3670	=over 4
2837		3671
2838	=item EV_STANDALONE	3672	=item EV_STANDALONE (h)
2839		3673
2840	Must always be C<1> if you do not use autoconf configuration, which	3674	Must always be C<1> if you do not use autoconf configuration, which
2841	keeps libev from including F<config.h>, and it also defines dummy	3675	keeps libev from including F<config.h>, and it also defines dummy
2842	implementations for some libevent functions (such as logging, which is not	3676	implementations for some libevent functions (such as logging, which is not
2843	supported). It will also not define any of the structs usually found in	3677	supported). It will also not define any of the structs usually found in
2844	F<event.h> that are not directly supported by the libev core alone.	3678	F<event.h> that are not directly supported by the libev core alone.
2845		3679
		3680	In standalone mode, libev will still try to automatically deduce the
		3681	configuration, but has to be more conservative.
		3682
2846	=item EV_USE_MONOTONIC	3683	=item EV_USE_MONOTONIC
2847		3684
2848	If defined to be C<1>, libev will try to detect the availability of the	3685	If defined to be C<1>, libev will try to detect the availability of the
2849	monotonic clock option at both compile time and runtime. Otherwise no use	3686	monotonic clock option at both compile time and runtime. Otherwise no
2850	of the monotonic clock option will be attempted. If you enable this, you	3687	use of the monotonic clock option will be attempted. If you enable this,
2851	usually have to link against librt or something similar. Enabling it when	3688	you usually have to link against librt or something similar. Enabling it
2852	the functionality isn't available is safe, though, although you have	3689	when the functionality isn't available is safe, though, although you have
2853	to make sure you link against any libraries where the C<clock_gettime>	3690	to make sure you link against any libraries where the C<clock_gettime>
2854	function is hiding in (often F<-lrt>).	3691	function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>.
2855		3692
2856	=item EV_USE_REALTIME	3693	=item EV_USE_REALTIME
2857		3694
2858	If defined to be C<1>, libev will try to detect the availability of the	3695	If defined to be C<1>, libev will try to detect the availability of the
2859	real-time clock option at compile time (and assume its availability at	3696	real-time clock option at compile time (and assume its availability
2860	runtime if successful). Otherwise no use of the real-time clock option will	3697	at runtime if successful). Otherwise no use of the real-time clock
2861	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	3698	option will be attempted. This effectively replaces C<gettimeofday>
2862	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	3699	by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect
2863	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	3700	correctness. See the note about libraries in the description of
		3701	C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of
		3702	C<EV_USE_CLOCK_SYSCALL>.
		3703
		3704	=item EV_USE_CLOCK_SYSCALL
		3705
		3706	If defined to be C<1>, libev will try to use a direct syscall instead
		3707	of calling the system-provided C<clock_gettime> function. This option
		3708	exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt>
		3709	unconditionally pulls in C<libpthread>, slowing down single-threaded
		3710	programs needlessly. Using a direct syscall is slightly slower (in
		3711	theory), because no optimised vdso implementation can be used, but avoids
		3712	the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or
		3713	higher, as it simplifies linking (no need for C<-lrt>).
2864		3714
2865	=item EV_USE_NANOSLEEP	3715	=item EV_USE_NANOSLEEP
2866		3716
2867	If defined to be C<1>, libev will assume that C<nanosleep ()> is available	3717	If defined to be C<1>, libev will assume that C<nanosleep ()> is available
2868	and will use it for delays. Otherwise it will use C<select ()>.	3718	and will use it for delays. Otherwise it will use C<select ()>.
…		…
2884		3734
2885	=item EV_SELECT_USE_FD_SET	3735	=item EV_SELECT_USE_FD_SET
2886		3736
2887	If defined to C<1>, then the select backend will use the system C<fd_set>	3737	If defined to C<1>, then the select backend will use the system C<fd_set>
2888	structure. This is useful if libev doesn't compile due to a missing	3738	structure. This is useful if libev doesn't compile due to a missing
2889	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on	3739	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout
2890	exotic systems. This usually limits the range of file descriptors to some	3740	on exotic systems. This usually limits the range of file descriptors to
2891	low limit such as 1024 or might have other limitations (winsocket only	3741	some low limit such as 1024 or might have other limitations (winsocket
2892	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	3742	only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
2893	influence the size of the C<fd_set> used.	3743	configures the maximum size of the C<fd_set>.
2894		3744
2895	=item EV_SELECT_IS_WINSOCKET	3745	=item EV_SELECT_IS_WINSOCKET
2896		3746
2897	When defined to C<1>, the select backend will assume that	3747	When defined to C<1>, the select backend will assume that
2898	select/socket/connect etc. don't understand file descriptors but	3748	select/socket/connect etc. don't understand file descriptors but
…		…
2900	be used is the winsock select). This means that it will call	3750	be used is the winsock select). This means that it will call
2901	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,	3751	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
2902	it is assumed that all these functions actually work on fds, even	3752	it is assumed that all these functions actually work on fds, even
2903	on win32. Should not be defined on non-win32 platforms.	3753	on win32. Should not be defined on non-win32 platforms.
2904		3754
2905	=item EV_FD_TO_WIN32_HANDLE	3755	=item EV_FD_TO_WIN32_HANDLE(fd)
2906		3756
2907	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map	3757	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map
2908	file descriptors to socket handles. When not defining this symbol (the	3758	file descriptors to socket handles. When not defining this symbol (the
2909	default), then libev will call C<_get_osfhandle>, which is usually	3759	default), then libev will call C<_get_osfhandle>, which is usually
2910	correct. In some cases, programs use their own file descriptor management,	3760	correct. In some cases, programs use their own file descriptor management,
2911	in which case they can provide this function to map fds to socket handles.	3761	in which case they can provide this function to map fds to socket handles.
		3762
		3763	=item EV_WIN32_HANDLE_TO_FD(handle)
		3764
		3765	If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors
		3766	using the standard C<_open_osfhandle> function. For programs implementing
		3767	their own fd to handle mapping, overwriting this function makes it easier
		3768	to do so. This can be done by defining this macro to an appropriate value.
		3769
		3770	=item EV_WIN32_CLOSE_FD(fd)
		3771
		3772	If programs implement their own fd to handle mapping on win32, then this
		3773	macro can be used to override the C<close> function, useful to unregister
		3774	file descriptors again. Note that the replacement function has to close
		3775	the underlying OS handle.
2912		3776
2913	=item EV_USE_POLL	3777	=item EV_USE_POLL
2914		3778
2915	If defined to be C<1>, libev will compile in support for the C<poll>(2)	3779	If defined to be C<1>, libev will compile in support for the C<poll>(2)
2916	backend. Otherwise it will be enabled on non-win32 platforms. It	3780	backend. Otherwise it will be enabled on non-win32 platforms. It
…		…
2963	as well as for signal and thread safety in C<ev_async> watchers.	3827	as well as for signal and thread safety in C<ev_async> watchers.
2964		3828
2965	In the absence of this define, libev will use C<sig_atomic_t volatile>	3829	In the absence of this define, libev will use C<sig_atomic_t volatile>
2966	(from F<signal.h>), which is usually good enough on most platforms.	3830	(from F<signal.h>), which is usually good enough on most platforms.
2967		3831
2968	=item EV_H	3832	=item EV_H (h)
2969		3833
2970	The name of the F<ev.h> header file used to include it. The default if	3834	The name of the F<ev.h> header file used to include it. The default if
2971	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be	3835	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
2972	used to virtually rename the F<ev.h> header file in case of conflicts.	3836	used to virtually rename the F<ev.h> header file in case of conflicts.
2973		3837
2974	=item EV_CONFIG_H	3838	=item EV_CONFIG_H (h)
2975		3839
2976	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override	3840	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
2977	F<ev.c>'s idea of where to find the F<config.h> file, similarly to	3841	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
2978	C<EV_H>, above.	3842	C<EV_H>, above.
2979		3843
2980	=item EV_EVENT_H	3844	=item EV_EVENT_H (h)
2981		3845
2982	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea	3846	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
2983	of how the F<event.h> header can be found, the default is C<"event.h">.	3847	of how the F<event.h> header can be found, the default is C<"event.h">.
2984		3848
2985	=item EV_PROTOTYPES	3849	=item EV_PROTOTYPES (h)
2986		3850
2987	If defined to be C<0>, then F<ev.h> will not define any function	3851	If defined to be C<0>, then F<ev.h> will not define any function
2988	prototypes, but still define all the structs and other symbols. This is	3852	prototypes, but still define all the structs and other symbols. This is
2989	occasionally useful if you want to provide your own wrapper functions	3853	occasionally useful if you want to provide your own wrapper functions
2990	around libev functions.	3854	around libev functions.
…		…
3009	When doing priority-based operations, libev usually has to linearly search	3873	When doing priority-based operations, libev usually has to linearly search
3010	all the priorities, so having many of them (hundreds) uses a lot of space	3874	all the priorities, so having many of them (hundreds) uses a lot of space
3011	and time, so using the defaults of five priorities (-2 .. +2) is usually	3875	and time, so using the defaults of five priorities (-2 .. +2) is usually
3012	fine.	3876	fine.
3013		3877
3014	If your embedding application does not need any priorities, defining these both to	3878	If your embedding application does not need any priorities, defining these
3015	C<0> will save some memory and CPU.	3879	both to C<0> will save some memory and CPU.
3016		3880
3017	=item EV_PERIODIC_ENABLE	3881	=item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE,
		3882	EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE,
		3883	EV_ASYNC_ENABLE, EV_CHILD_ENABLE.
3018		3884
3019	If undefined or defined to be C<1>, then periodic timers are supported. If	3885	If undefined or defined to be C<1> (and the platform supports it), then
3020	defined to be C<0>, then they are not. Disabling them saves a few kB of	3886	the respective watcher type is supported. If defined to be C<0>, then it
3021	code.	3887	is not. Disabling watcher types mainly saves codesize.
3022		3888
3023	=item EV_IDLE_ENABLE	3889	=item EV_FEATURES
3024
3025	If undefined or defined to be C<1>, then idle watchers are supported. If
3026	defined to be C<0>, then they are not. Disabling them saves a few kB of
3027	code.
3028
3029	=item EV_EMBED_ENABLE
3030
3031	If undefined or defined to be C<1>, then embed watchers are supported. If
3032	defined to be C<0>, then they are not.
3033
3034	=item EV_STAT_ENABLE
3035
3036	If undefined or defined to be C<1>, then stat watchers are supported. If
3037	defined to be C<0>, then they are not.
3038
3039	=item EV_FORK_ENABLE
3040
3041	If undefined or defined to be C<1>, then fork watchers are supported. If
3042	defined to be C<0>, then they are not.
3043
3044	=item EV_ASYNC_ENABLE
3045
3046	If undefined or defined to be C<1>, then async watchers are supported. If
3047	defined to be C<0>, then they are not.
3048
3049	=item EV_MINIMAL
3050		3890
3051	If you need to shave off some kilobytes of code at the expense of some	3891	If you need to shave off some kilobytes of code at the expense of some
3052	speed, define this symbol to C<1>. Currently this is used to override some	3892	speed (but with the full API), you can define this symbol to request
3053	inlining decisions, saves roughly 30% code size on amd64. It also selects a	3893	certain subsets of functionality. The default is to enable all features
3054	much smaller 2-heap for timer management over the default 4-heap.	3894	that can be enabled on the platform.
		3895
		3896	Note that using autoconf will usually override most of the features, so
		3897	using this symbol makes sense mostly when embedding libev.
		3898
		3899	A typical way to use this symbol is to define it to C<0> (or to a bitset
		3900	with some broad features you want) and then selectively re-enable
		3901	additional parts you want, for example if you want everything minimal,
		3902	but multiple event loop support, async and child watchers and the poll
		3903	backend, use this:
		3904
		3905	#define EV_FEATURES 0
		3906	#define EV_MULTIPLICITY 1
		3907	#define EV_USE_POLL 1
		3908	#define EV_CHILD_ENABLE 1
		3909	#define EV_ASYNC_ENABLE 1
		3910
		3911	The actual value is a bitset, it can be a combination of the following
		3912	values:
		3913
		3914	=over 4
		3915
		3916	=item C<1> - faster/larger code
		3917
		3918	Use larger code to speed up some operations.
		3919
		3920	Currently this is used to override some inlining decisions (enlarging the roughly
		3921	30% code size on amd64.
		3922
		3923	When optimising for size, use of compiler flags such as C<-Os> with
		3924	gcc recommended, as well as C<-DNDEBUG>, as libev contains a number of
		3925	assertions.
		3926
		3927	=item C<2> - faster/larger data structures
		3928
		3929	Replaces the small 2-heap for timer management by a faster 4-heap, larger
		3930	hash table sizes and so on. This will usually further increase codesize
		3931	and can additionally have an effect on the size of data structures at
		3932	runtime.
		3933
		3934	=item C<4> - full API configuration
		3935
		3936	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
		3937	enables multiplicity (C<EV_MULTIPLICITY>=1).
		3938
		3939	It also enables a lot of the "lesser used" core API functions. See C<ev.h>
		3940	for details on which parts of the API are still available without this
		3941	feature, and do not complain if this subset changes over time.
		3942
		3943	=item C<8> - enable all optional watcher types
		3944
		3945	Enables all optional watcher types. If you want to selectively enable
		3946	only some watcher types other than I/O and timers (e.g. prepare,
		3947	embed, async, child...) you can enable them manually by defining
		3948	C<EV_watchertype_ENABLE> to C<1> instead.
		3949
		3950	=item C<16> - enable all backends
		3951
		3952	This enables all backends - without this feature, you need to enable at
		3953	least one backend manually (C<EV_USE_SELECT> is a good choice).
		3954
		3955	=item C<32> - enable OS-specific "helper" APIs
		3956
		3957	Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by
		3958	default.
		3959
		3960	=back
		3961
		3962	Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0>
		3963	reduces the compiled size of libev from 24.7Kb to 6.5Kb on my GNU/Linux
		3964	amd64 system, while still giving you I/O watchers, timers and monotonic
		3965	clock support.
		3966
		3967	With an intelligent-enough linker (gcc+binutils are intelligent enough
		3968	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
		3969	your program might be left out as well - a binary starting a timer and an
		3970	I/O watcher then might come out at only 5Kb.
		3971
		3972	=item EV_AVOID_STDIO
		3973
		3974	If this is set to C<1> at compiletime, then libev will avoid using stdio
		3975	functions (printf, scanf, perror etc.). This will increase the codesize
		3976	somewhat, but if your program doesn't otherwise depend on stdio and your
		3977	libc allows it, this avoids linking in the stdio library which is quite
		3978	big.
		3979
		3980	Note that error messages might become less precise when this option is
		3981	enabled.
		3982
		3983	=item EV_NSIG
		3984
		3985	The highest supported signal number, +1 (or, the number of
		3986	signals): Normally, libev tries to deduce the maximum number of signals
		3987	automatically, but sometimes this fails, in which case it can be
		3988	specified. Also, using a lower number than detected (C<32> should be
		3989	good for about any system in existance) can save some memory, as libev
		3990	statically allocates some 12-24 bytes per signal number.
3055		3991
3056	=item EV_PID_HASHSIZE	3992	=item EV_PID_HASHSIZE
3057		3993
3058	C<ev_child> watchers use a small hash table to distribute workload by	3994	C<ev_child> watchers use a small hash table to distribute workload by
3059	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	3995	pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled),
3060	than enough. If you need to manage thousands of children you might want to	3996	usually more than enough. If you need to manage thousands of children you
3061	increase this value (I<must> be a power of two).	3997	might want to increase this value (I<must> be a power of two).
3062		3998
3063	=item EV_INOTIFY_HASHSIZE	3999	=item EV_INOTIFY_HASHSIZE
3064		4000
3065	C<ev_stat> watchers use a small hash table to distribute workload by	4001	C<ev_stat> watchers use a small hash table to distribute workload by
3066	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	4002	inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES>
3067	usually more than enough. If you need to manage thousands of C<ev_stat>	4003	disabled), usually more than enough. If you need to manage thousands of
3068	watchers you might want to increase this value (I<must> be a power of	4004	C<ev_stat> watchers you might want to increase this value (I<must> be a
3069	two).	4005	power of two).
3070		4006
3071	=item EV_USE_4HEAP	4007	=item EV_USE_4HEAP
3072		4008
3073	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4009	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3074	timer and periodics heap, libev uses a 4-heap when this symbol is defined	4010	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
3075	to C<1>. The 4-heap uses more complicated (longer) code but has	4011	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
3076	noticeably faster performance with many (thousands) of watchers.	4012	faster performance with many (thousands) of watchers.
3077		4013
3078	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4014	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3079	(disabled).	4015	will be C<0>.
3080		4016
3081	=item EV_HEAP_CACHE_AT	4017	=item EV_HEAP_CACHE_AT
3082		4018
3083	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4019	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3084	timer and periodics heap, libev can cache the timestamp (I<at>) within	4020	timer and periodics heaps, libev can cache the timestamp (I<at>) within
3085	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),	4021	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
3086	which uses 8-12 bytes more per watcher and a few hundred bytes more code,	4022	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
3087	but avoids random read accesses on heap changes. This improves performance	4023	but avoids random read accesses on heap changes. This improves performance
3088	noticeably with with many (hundreds) of watchers.	4024	noticeably with many (hundreds) of watchers.
3089		4025
3090	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4026	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3091	(disabled).	4027	will be C<0>.
3092		4028
3093	=item EV_VERIFY	4029	=item EV_VERIFY
3094		4030
3095	Controls how much internal verification (see C<ev_loop_verify ()>) will	4031	Controls how much internal verification (see C<ev_loop_verify ()>) will
3096	be done: If set to C<0>, no internal verification code will be compiled	4032	be done: If set to C<0>, no internal verification code will be compiled
…		…
3098	called. If set to C<2>, then the internal verification code will be	4034	called. If set to C<2>, then the internal verification code will be
3099	called once per loop, which can slow down libev. If set to C<3>, then the	4035	called once per loop, which can slow down libev. If set to C<3>, then the
3100	verification code will be called very frequently, which will slow down	4036	verification code will be called very frequently, which will slow down
3101	libev considerably.	4037	libev considerably.
3102		4038
3103	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be	4039	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3104	C<0.>	4040	will be C<0>.
3105		4041
3106	=item EV_COMMON	4042	=item EV_COMMON
3107		4043
3108	By default, all watchers have a C<void *data> member. By redefining	4044	By default, all watchers have a C<void *data> member. By redefining
3109	this macro to a something else you can include more and other types of	4045	this macro to a something else you can include more and other types of
…		…
3126	and the way callbacks are invoked and set. Must expand to a struct member	4062	and the way callbacks are invoked and set. Must expand to a struct member
3127	definition and a statement, respectively. See the F<ev.h> header file for	4063	definition and a statement, respectively. See the F<ev.h> header file for
3128	their default definitions. One possible use for overriding these is to	4064	their default definitions. One possible use for overriding these is to
3129	avoid the C<struct ev_loop *> as first argument in all cases, or to use	4065	avoid the C<struct ev_loop *> as first argument in all cases, or to use
3130	method calls instead of plain function calls in C++.	4066	method calls instead of plain function calls in C++.
		4067
		4068	=back
3131		4069
3132	=head2 EXPORTED API SYMBOLS	4070	=head2 EXPORTED API SYMBOLS
3133		4071
3134	If you need to re-export the API (e.g. via a DLL) and you need a list of	4072	If you need to re-export the API (e.g. via a DLL) and you need a list of
3135	exported symbols, you can use the provided F<Symbol.*> files which list	4073	exported symbols, you can use the provided F<Symbol.*> files which list
…		…
3165	file.	4103	file.
3166		4104
3167	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	4105	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
3168	that everybody includes and which overrides some configure choices:	4106	that everybody includes and which overrides some configure choices:
3169		4107
3170	#define EV_MINIMAL 1	4108	#define EV_FEATURES 0
3171	#define EV_USE_POLL 0	4109	#define EV_USE_SELECT 1
3172	#define EV_MULTIPLICITY 0
3173	#define EV_PERIODIC_ENABLE 0
3174	#define EV_STAT_ENABLE 0
3175	#define EV_FORK_ENABLE 0
3176	#define EV_CONFIG_H <config.h>	4110	#define EV_CONFIG_H <config.h>
3177	#define EV_MINPRI 0
3178	#define EV_MAXPRI 0
3179		4111
3180	#include "ev++.h"	4112	#include "ev++.h"
3181		4113
3182	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4114	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
3183		4115
3184	#include "ev_cpp.h"	4116	#include "ev_cpp.h"
3185	#include "ev.c"	4117	#include "ev.c"
3186		4118
		4119	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES
3187		4120
3188	=head1 THREADS AND COROUTINES	4121	=head2 THREADS AND COROUTINES
3189		4122
3190	=head2 THREADS	4123	=head3 THREADS
3191		4124
3192	Libev itself is completely thread-safe, but it uses no locking. This	4125	All libev functions are reentrant and thread-safe unless explicitly
		4126	documented otherwise, but libev implements no locking itself. This means
3193	means that you can use as many loops as you want in parallel, as long as	4127	that you can use as many loops as you want in parallel, as long as there
3194	only one thread ever calls into one libev function with the same loop	4128	are no concurrent calls into any libev function with the same loop
3195	parameter.	4129	parameter (C<ev_default_*> calls have an implicit default loop parameter,
		4130	of course): libev guarantees that different event loops share no data
		4131	structures that need any locking.
3196		4132
3197	Or put differently: calls with different loop parameters can be done in	4133	Or to put it differently: calls with different loop parameters can be done
3198	parallel from multiple threads, calls with the same loop parameter must be	4134	concurrently from multiple threads, calls with the same loop parameter
3199	done serially (but can be done from different threads, as long as only one	4135	must be done serially (but can be done from different threads, as long as
3200	thread ever is inside a call at any point in time, e.g. by using a mutex	4136	only one thread ever is inside a call at any point in time, e.g. by using
3201	per loop).	4137	a mutex per loop).
		4138
		4139	Specifically to support threads (and signal handlers), libev implements
		4140	so-called C<ev_async> watchers, which allow some limited form of
		4141	concurrency on the same event loop, namely waking it up "from the
		4142	outside".
3202		4143
3203	If you want to know which design (one loop, locking, or multiple loops	4144	If you want to know which design (one loop, locking, or multiple loops
3204	without or something else still) is best for your problem, then I cannot	4145	without or something else still) is best for your problem, then I cannot
3205	help you. I can give some generic advice however:	4146	help you, but here is some generic advice:
3206		4147
3207	=over 4	4148	=over 4
3208		4149
3209	=item * most applications have a main thread: use the default libev loop	4150	=item * most applications have a main thread: use the default libev loop
3210	in that thread, or create a separate thread running only the default loop.	4151	in that thread, or create a separate thread running only the default loop.
…		…
3222		4163
3223	Choosing a model is hard - look around, learn, know that usually you can do	4164	Choosing a model is hard - look around, learn, know that usually you can do
3224	better than you currently do :-)	4165	better than you currently do :-)
3225		4166
3226	=item * often you need to talk to some other thread which blocks in the	4167	=item * often you need to talk to some other thread which blocks in the
		4168	event loop.
		4169
3227	event loop - C<ev_async> watchers can be used to wake them up from other	4170	C<ev_async> watchers can be used to wake them up from other threads safely
3228	threads safely (or from signal contexts...).	4171	(or from signal contexts...).
		4172
		4173	An example use would be to communicate signals or other events that only
		4174	work in the default loop by registering the signal watcher with the
		4175	default loop and triggering an C<ev_async> watcher from the default loop
		4176	watcher callback into the event loop interested in the signal.
3229		4177
3230	=back	4178	=back
3231		4179
		4180	=head4 THREAD LOCKING EXAMPLE
		4181
		4182	Here is a fictitious example of how to run an event loop in a different
		4183	thread than where callbacks are being invoked and watchers are
		4184	created/added/removed.
		4185
		4186	For a real-world example, see the C<EV::Loop::Async> perl module,
		4187	which uses exactly this technique (which is suited for many high-level
		4188	languages).
		4189
		4190	The example uses a pthread mutex to protect the loop data, a condition
		4191	variable to wait for callback invocations, an async watcher to notify the
		4192	event loop thread and an unspecified mechanism to wake up the main thread.
		4193
		4194	First, you need to associate some data with the event loop:
		4195
		4196	typedef struct {
		4197	mutex_t lock; /* global loop lock */
		4198	ev_async async_w;
		4199	thread_t tid;
		4200	cond_t invoke_cv;
		4201	} userdata;
		4202
		4203	void prepare_loop (EV_P)
		4204	{
		4205	// for simplicity, we use a static userdata struct.
		4206	static userdata u;
		4207
		4208	ev_async_init (&u->async_w, async_cb);
		4209	ev_async_start (EV_A_ &u->async_w);
		4210
		4211	pthread_mutex_init (&u->lock, 0);
		4212	pthread_cond_init (&u->invoke_cv, 0);
		4213
		4214	// now associate this with the loop
		4215	ev_set_userdata (EV_A_ u);
		4216	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		4217	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		4218
		4219	// then create the thread running ev_loop
		4220	pthread_create (&u->tid, 0, l_run, EV_A);
		4221	}
		4222
		4223	The callback for the C<ev_async> watcher does nothing: the watcher is used
		4224	solely to wake up the event loop so it takes notice of any new watchers
		4225	that might have been added:
		4226
		4227	static void
		4228	async_cb (EV_P_ ev_async *w, int revents)
		4229	{
		4230	// just used for the side effects
		4231	}
		4232
		4233	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		4234	protecting the loop data, respectively.
		4235
		4236	static void
		4237	l_release (EV_P)
		4238	{
		4239	userdata *u = ev_userdata (EV_A);
		4240	pthread_mutex_unlock (&u->lock);
		4241	}
		4242
		4243	static void
		4244	l_acquire (EV_P)
		4245	{
		4246	userdata *u = ev_userdata (EV_A);
		4247	pthread_mutex_lock (&u->lock);
		4248	}
		4249
		4250	The event loop thread first acquires the mutex, and then jumps straight
		4251	into C<ev_loop>:
		4252
		4253	void *
		4254	l_run (void *thr_arg)
		4255	{
		4256	struct ev_loop *loop = (struct ev_loop *)thr_arg;
		4257
		4258	l_acquire (EV_A);
		4259	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		4260	ev_loop (EV_A_ 0);
		4261	l_release (EV_A);
		4262
		4263	return 0;
		4264	}
		4265
		4266	Instead of invoking all pending watchers, the C<l_invoke> callback will
		4267	signal the main thread via some unspecified mechanism (signals? pipe
		4268	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		4269	have been called (in a while loop because a) spurious wakeups are possible
		4270	and b) skipping inter-thread-communication when there are no pending
		4271	watchers is very beneficial):
		4272
		4273	static void
		4274	l_invoke (EV_P)
		4275	{
		4276	userdata *u = ev_userdata (EV_A);
		4277
		4278	while (ev_pending_count (EV_A))
		4279	{
		4280	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		4281	pthread_cond_wait (&u->invoke_cv, &u->lock);
		4282	}
		4283	}
		4284
		4285	Now, whenever the main thread gets told to invoke pending watchers, it
		4286	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		4287	thread to continue:
		4288
		4289	static void
		4290	real_invoke_pending (EV_P)
		4291	{
		4292	userdata *u = ev_userdata (EV_A);
		4293
		4294	pthread_mutex_lock (&u->lock);
		4295	ev_invoke_pending (EV_A);
		4296	pthread_cond_signal (&u->invoke_cv);
		4297	pthread_mutex_unlock (&u->lock);
		4298	}
		4299
		4300	Whenever you want to start/stop a watcher or do other modifications to an
		4301	event loop, you will now have to lock:
		4302
		4303	ev_timer timeout_watcher;
		4304	userdata *u = ev_userdata (EV_A);
		4305
		4306	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		4307
		4308	pthread_mutex_lock (&u->lock);
		4309	ev_timer_start (EV_A_ &timeout_watcher);
		4310	ev_async_send (EV_A_ &u->async_w);
		4311	pthread_mutex_unlock (&u->lock);
		4312
		4313	Note that sending the C<ev_async> watcher is required because otherwise
		4314	an event loop currently blocking in the kernel will have no knowledge
		4315	about the newly added timer. By waking up the loop it will pick up any new
		4316	watchers in the next event loop iteration.
		4317
3232	=head2 COROUTINES	4318	=head3 COROUTINES
3233		4319
3234	Libev is much more accommodating to coroutines ("cooperative threads"):	4320	Libev is very accommodating to coroutines ("cooperative threads"):
3235	libev fully supports nesting calls to it's functions from different	4321	libev fully supports nesting calls to its functions from different
3236	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4322	coroutines (e.g. you can call C<ev_loop> on the same loop from two
3237	different coroutines and switch freely between both coroutines running the	4323	different coroutines, and switch freely between both coroutines running
3238	loop, as long as you don't confuse yourself). The only exception is that	4324	the loop, as long as you don't confuse yourself). The only exception is
3239	you must not do this from C<ev_periodic> reschedule callbacks.	4325	that you must not do this from C<ev_periodic> reschedule callbacks.
3240		4326
3241	Care has been invested into making sure that libev does not keep local	4327	Care has been taken to ensure that libev does not keep local state inside
3242	state inside C<ev_loop>, and other calls do not usually allow coroutine	4328	C<ev_loop>, and other calls do not usually allow for coroutine switches as
3243	switches.	4329	they do not call any callbacks.
3244		4330
		4331	=head2 COMPILER WARNINGS
3245		4332
3246	=head1 COMPLEXITIES	4333	Depending on your compiler and compiler settings, you might get no or a
		4334	lot of warnings when compiling libev code. Some people are apparently
		4335	scared by this.
3247		4336
3248	In this section the complexities of (many of) the algorithms used inside	4337	However, these are unavoidable for many reasons. For one, each compiler
3249	libev will be explained. For complexity discussions about backends see the	4338	has different warnings, and each user has different tastes regarding
3250	documentation for C<ev_default_init>.	4339	warning options. "Warn-free" code therefore cannot be a goal except when
		4340	targeting a specific compiler and compiler-version.
3251		4341
3252	All of the following are about amortised time: If an array needs to be	4342	Another reason is that some compiler warnings require elaborate
3253	extended, libev needs to realloc and move the whole array, but this	4343	workarounds, or other changes to the code that make it less clear and less
3254	happens asymptotically never with higher number of elements, so O(1) might	4344	maintainable.
3255	mean it might do a lengthy realloc operation in rare cases, but on average
3256	it is much faster and asymptotically approaches constant time.
3257		4345
3258	=over 4	4346	And of course, some compiler warnings are just plain stupid, or simply
		4347	wrong (because they don't actually warn about the condition their message
		4348	seems to warn about). For example, certain older gcc versions had some
		4349	warnings that resulted an extreme number of false positives. These have
		4350	been fixed, but some people still insist on making code warn-free with
		4351	such buggy versions.
3259		4352
3260	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)	4353	While libev is written to generate as few warnings as possible,
		4354	"warn-free" code is not a goal, and it is recommended not to build libev
		4355	with any compiler warnings enabled unless you are prepared to cope with
		4356	them (e.g. by ignoring them). Remember that warnings are just that:
		4357	warnings, not errors, or proof of bugs.
3261		4358
3262	This means that, when you have a watcher that triggers in one hour and
3263	there are 100 watchers that would trigger before that then inserting will
3264	have to skip roughly seven (C<ld 100>) of these watchers.
3265		4359
3266	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)	4360	=head2 VALGRIND
3267		4361
3268	That means that changing a timer costs less than removing/adding them	4362	Valgrind has a special section here because it is a popular tool that is
3269	as only the relative motion in the event queue has to be paid for.	4363	highly useful. Unfortunately, valgrind reports are very hard to interpret.
3270		4364
3271	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)	4365	If you think you found a bug (memory leak, uninitialised data access etc.)
		4366	in libev, then check twice: If valgrind reports something like:
3272		4367
3273	These just add the watcher into an array or at the head of a list.	4368	==2274== definitely lost: 0 bytes in 0 blocks.
		4369	==2274== possibly lost: 0 bytes in 0 blocks.
		4370	==2274== still reachable: 256 bytes in 1 blocks.
3274		4371
3275	=item Stopping check/prepare/idle/fork/async watchers: O(1)	4372	Then there is no memory leak, just as memory accounted to global variables
		4373	is not a memleak - the memory is still being referenced, and didn't leak.
3276		4374
3277	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))	4375	Similarly, under some circumstances, valgrind might report kernel bugs
		4376	as if it were a bug in libev (e.g. in realloc or in the poll backend,
		4377	although an acceptable workaround has been found here), or it might be
		4378	confused.
3278		4379
3279	These watchers are stored in lists then need to be walked to find the	4380	Keep in mind that valgrind is a very good tool, but only a tool. Don't
3280	correct watcher to remove. The lists are usually short (you don't usually	4381	make it into some kind of religion.
3281	have many watchers waiting for the same fd or signal).
3282		4382
3283	=item Finding the next timer in each loop iteration: O(1)	4383	If you are unsure about something, feel free to contact the mailing list
		4384	with the full valgrind report and an explanation on why you think this
		4385	is a bug in libev (best check the archives, too :). However, don't be
		4386	annoyed when you get a brisk "this is no bug" answer and take the chance
		4387	of learning how to interpret valgrind properly.
3284		4388
3285	By virtue of using a binary or 4-heap, the next timer is always found at a	4389	If you need, for some reason, empty reports from valgrind for your project
3286	fixed position in the storage array.	4390	I suggest using suppression lists.
3287		4391
3288	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
3289		4392
3290	A change means an I/O watcher gets started or stopped, which requires	4393	=head1 PORTABILITY NOTES
3291	libev to recalculate its status (and possibly tell the kernel, depending
3292	on backend and whether C<ev_io_set> was used).
3293		4394
3294	=item Activating one watcher (putting it into the pending state): O(1)
3295
3296	=item Priority handling: O(number_of_priorities)
3297
3298	Priorities are implemented by allocating some space for each
3299	priority. When doing priority-based operations, libev usually has to
3300	linearly search all the priorities, but starting/stopping and activating
3301	watchers becomes O(1) w.r.t. priority handling.
3302
3303	=item Sending an ev_async: O(1)
3304
3305	=item Processing ev_async_send: O(number_of_async_watchers)
3306
3307	=item Processing signals: O(max_signal_number)
3308
3309	Sending involves a system call I<iff> there were no other C<ev_async_send>
3310	calls in the current loop iteration. Checking for async and signal events
3311	involves iterating over all running async watchers or all signal numbers.
3312
3313	=back
3314
3315
3316	=head1 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS	4395	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
3317		4396
3318	Win32 doesn't support any of the standards (e.g. POSIX) that libev	4397	Win32 doesn't support any of the standards (e.g. POSIX) that libev
3319	requires, and its I/O model is fundamentally incompatible with the POSIX	4398	requires, and its I/O model is fundamentally incompatible with the POSIX
3320	model. Libev still offers limited functionality on this platform in	4399	model. Libev still offers limited functionality on this platform in
3321	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	4400	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
…		…
3328	way (note also that glib is the slowest event library known to man).	4407	way (note also that glib is the slowest event library known to man).
3329		4408
3330	There is no supported compilation method available on windows except	4409	There is no supported compilation method available on windows except
3331	embedding it into other applications.	4410	embedding it into other applications.
3332		4411
		4412	Sensible signal handling is officially unsupported by Microsoft - libev
		4413	tries its best, but under most conditions, signals will simply not work.
		4414
3333	Not a libev limitation but worth mentioning: windows apparently doesn't	4415	Not a libev limitation but worth mentioning: windows apparently doesn't
3334	accept large writes: instead of resulting in a partial write, windows will	4416	accept large writes: instead of resulting in a partial write, windows will
3335	either accept everything or return C<ENOBUFS> if the buffer is too large,	4417	either accept everything or return C<ENOBUFS> if the buffer is too large,
3336	so make sure you only write small amounts into your sockets (less than a	4418	so make sure you only write small amounts into your sockets (less than a
3337	megabyte seems safe, but thsi apparently depends on the amount of memory	4419	megabyte seems safe, but this apparently depends on the amount of memory
3338	available).	4420	available).
3339		4421
3340	Due to the many, low, and arbitrary limits on the win32 platform and	4422	Due to the many, low, and arbitrary limits on the win32 platform and
3341	the abysmal performance of winsockets, using a large number of sockets	4423	the abysmal performance of winsockets, using a large number of sockets
3342	is not recommended (and not reasonable). If your program needs to use	4424	is not recommended (and not reasonable). If your program needs to use
3343	more than a hundred or so sockets, then likely it needs to use a totally	4425	more than a hundred or so sockets, then likely it needs to use a totally
3344	different implementation for windows, as libev offers the POSIX readiness	4426	different implementation for windows, as libev offers the POSIX readiness
3345	notification model, which cannot be implemented efficiently on windows	4427	notification model, which cannot be implemented efficiently on windows
3346	(Microsoft monopoly games).	4428	(due to Microsoft monopoly games).
3347		4429
3348	A typical way to use libev under windows is to embed it (see the embedding	4430	A typical way to use libev under windows is to embed it (see the embedding
3349	section for details) and use the following F<evwrap.h> header file instead	4431	section for details) and use the following F<evwrap.h> header file instead
3350	of F<ev.h>:	4432	of F<ev.h>:
3351		4433
…		…
3353	#define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */	4435	#define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */
3354		4436
3355	#include "ev.h"	4437	#include "ev.h"
3356		4438
3357	And compile the following F<evwrap.c> file into your project (make sure	4439	And compile the following F<evwrap.c> file into your project (make sure
3358	you do I<not> compile the F<ev.c> or any other embedded soruce files!):	4440	you do I<not> compile the F<ev.c> or any other embedded source files!):
3359		4441
3360	#include "evwrap.h"	4442	#include "evwrap.h"
3361	#include "ev.c"	4443	#include "ev.c"
3362		4444
3363	=over 4	4445	=over 4
…		…
3387		4469
3388	Early versions of winsocket's select only supported waiting for a maximum	4470	Early versions of winsocket's select only supported waiting for a maximum
3389	of C<64> handles (probably owning to the fact that all windows kernels	4471	of C<64> handles (probably owning to the fact that all windows kernels
3390	can only wait for C<64> things at the same time internally; Microsoft	4472	can only wait for C<64> things at the same time internally; Microsoft
3391	recommends spawning a chain of threads and wait for 63 handles and the	4473	recommends spawning a chain of threads and wait for 63 handles and the
3392	previous thread in each. Great).	4474	previous thread in each. Sounds great!).
3393		4475
3394	Newer versions support more handles, but you need to define C<FD_SETSIZE>	4476	Newer versions support more handles, but you need to define C<FD_SETSIZE>
3395	to some high number (e.g. C<2048>) before compiling the winsocket select	4477	to some high number (e.g. C<2048>) before compiling the winsocket select
3396	call (which might be in libev or elsewhere, for example, perl does its own	4478	call (which might be in libev or elsewhere, for example, perl and many
3397	select emulation on windows).	4479	other interpreters do their own select emulation on windows).
3398		4480
3399	Another limit is the number of file descriptors in the Microsoft runtime	4481	Another limit is the number of file descriptors in the Microsoft runtime
3400	libraries, which by default is C<64> (there must be a hidden I<64> fetish	4482	libraries, which by default is C<64> (there must be a hidden I<64>
3401	or something like this inside Microsoft). You can increase this by calling	4483	fetish or something like this inside Microsoft). You can increase this
3402	C<_setmaxstdio>, which can increase this limit to C<2048> (another	4484	by calling C<_setmaxstdio>, which can increase this limit to C<2048>
3403	arbitrary limit), but is broken in many versions of the Microsoft runtime	4485	(another arbitrary limit), but is broken in many versions of the Microsoft
3404	libraries.
3405
3406	This might get you to about C<512> or C<2048> sockets (depending on	4486	runtime libraries. This might get you to about C<512> or C<2048> sockets
3407	windows version and/or the phase of the moon). To get more, you need to	4487	(depending on windows version and/or the phase of the moon). To get more,
3408	wrap all I/O functions and provide your own fd management, but the cost of	4488	you need to wrap all I/O functions and provide your own fd management, but
3409	calling select (O(n²)) will likely make this unworkable.	4489	the cost of calling select (O(n²)) will likely make this unworkable.
3410		4490
3411	=back	4491	=back
3412		4492
3413
3414	=head1 PORTABILITY REQUIREMENTS	4493	=head2 PORTABILITY REQUIREMENTS
3415		4494
3416	In addition to a working ISO-C implementation, libev relies on a few	4495	In addition to a working ISO-C implementation and of course the
3417	additional extensions:	4496	backend-specific APIs, libev relies on a few additional extensions:
3418		4497
3419	=over 4	4498	=over 4
3420		4499
3421	=item C<void (*)(ev_watcher_type *, int revents)> must have compatible	4500	=item C<void (*)(ev_watcher_type *, int revents)> must have compatible
3422	calling conventions regardless of C<ev_watcher_type *>.	4501	calling conventions regardless of C<ev_watcher_type *>.
…		…
3428	calls them using an C<ev_watcher *> internally.	4507	calls them using an C<ev_watcher *> internally.
3429		4508
3430	=item C<sig_atomic_t volatile> must be thread-atomic as well	4509	=item C<sig_atomic_t volatile> must be thread-atomic as well
3431		4510
3432	The type C<sig_atomic_t volatile> (or whatever is defined as	4511	The type C<sig_atomic_t volatile> (or whatever is defined as
3433	C<EV_ATOMIC_T>) must be atomic w.r.t. accesses from different	4512	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
3434	threads. This is not part of the specification for C<sig_atomic_t>, but is	4513	threads. This is not part of the specification for C<sig_atomic_t>, but is
3435	believed to be sufficiently portable.	4514	believed to be sufficiently portable.
3436		4515
3437	=item C<sigprocmask> must work in a threaded environment	4516	=item C<sigprocmask> must work in a threaded environment
3438		4517
…		…
3447	except the initial one, and run the default loop in the initial thread as	4526	except the initial one, and run the default loop in the initial thread as
3448	well.	4527	well.
3449		4528
3450	=item C<long> must be large enough for common memory allocation sizes	4529	=item C<long> must be large enough for common memory allocation sizes
3451		4530
3452	To improve portability and simplify using libev, libev uses C<long>	4531	To improve portability and simplify its API, libev uses C<long> internally
3453	internally instead of C<size_t> when allocating its data structures. On	4532	instead of C<size_t> when allocating its data structures. On non-POSIX
3454	non-POSIX systems (Microsoft...) this might be unexpectedly low, but	4533	systems (Microsoft...) this might be unexpectedly low, but is still at
3455	is still at least 31 bits everywhere, which is enough for hundreds of	4534	least 31 bits everywhere, which is enough for hundreds of millions of
3456	millions of watchers.	4535	watchers.
3457		4536
3458	=item C<double> must hold a time value in seconds with enough accuracy	4537	=item C<double> must hold a time value in seconds with enough accuracy
3459		4538
3460	The type C<double> is used to represent timestamps. It is required to	4539	The type C<double> is used to represent timestamps. It is required to
3461	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	4540	have at least 51 bits of mantissa (and 9 bits of exponent), which is good
3462	enough for at least into the year 4000. This requirement is fulfilled by	4541	enough for at least into the year 4000. This requirement is fulfilled by
3463	implementations implementing IEEE 754 (basically all existing ones).	4542	implementations implementing IEEE 754, which is basically all existing
		4543	ones. With IEEE 754 doubles, you get microsecond accuracy until at least
		4544	2200.
3464		4545
3465	=back	4546	=back
3466		4547
3467	If you know of other additional requirements drop me a note.	4548	If you know of other additional requirements drop me a note.
3468		4549
3469		4550
3470	=head1 COMPILER WARNINGS	4551	=head1 ALGORITHMIC COMPLEXITIES
3471		4552
3472	Depending on your compiler and compiler settings, you might get no or a	4553	In this section the complexities of (many of) the algorithms used inside
3473	lot of warnings when compiling libev code. Some people are apparently	4554	libev will be documented. For complexity discussions about backends see
3474	scared by this.	4555	the documentation for C<ev_default_init>.
3475		4556
3476	However, these are unavoidable for many reasons. For one, each compiler	4557	All of the following are about amortised time: If an array needs to be
3477	has different warnings, and each user has different tastes regarding	4558	extended, libev needs to realloc and move the whole array, but this
3478	warning options. "Warn-free" code therefore cannot be a goal except when	4559	happens asymptotically rarer with higher number of elements, so O(1) might
3479	targeting a specific compiler and compiler-version.	4560	mean that libev does a lengthy realloc operation in rare cases, but on
		4561	average it is much faster and asymptotically approaches constant time.
3480		4562
3481	Another reason is that some compiler warnings require elaborate	4563	=over 4
3482	workarounds, or other changes to the code that make it less clear and less
3483	maintainable.
3484		4564
3485	And of course, some compiler warnings are just plain stupid, or simply	4565	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)
3486	wrong (because they don't actually warn about the condition their message
3487	seems to warn about).
3488		4566
3489	While libev is written to generate as few warnings as possible,	4567	This means that, when you have a watcher that triggers in one hour and
3490	"warn-free" code is not a goal, and it is recommended not to build libev	4568	there are 100 watchers that would trigger before that, then inserting will
3491	with any compiler warnings enabled unless you are prepared to cope with	4569	have to skip roughly seven (C<ld 100>) of these watchers.
3492	them (e.g. by ignoring them). Remember that warnings are just that:
3493	warnings, not errors, or proof of bugs.
3494		4570
		4571	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)
3495		4572
3496	=head1 VALGRIND	4573	That means that changing a timer costs less than removing/adding them,
		4574	as only the relative motion in the event queue has to be paid for.
3497		4575
3498	Valgrind has a special section here because it is a popular tool that is	4576	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
3499	highly useful, but valgrind reports are very hard to interpret.
3500		4577
3501	If you think you found a bug (memory leak, uninitialised data access etc.)	4578	These just add the watcher into an array or at the head of a list.
3502	in libev, then check twice: If valgrind reports something like:
3503		4579
3504	==2274== definitely lost: 0 bytes in 0 blocks.	4580	=item Stopping check/prepare/idle/fork/async watchers: O(1)
3505	==2274== possibly lost: 0 bytes in 0 blocks.
3506	==2274== still reachable: 256 bytes in 1 blocks.
3507		4581
3508	Then there is no memory leak. Similarly, under some circumstances,	4582	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
3509	valgrind might report kernel bugs as if it were a bug in libev, or it
3510	might be confused (it is a very good tool, but only a tool).
3511		4583
3512	If you are unsure about something, feel free to contact the mailing list	4584	These watchers are stored in lists, so they need to be walked to find the
3513	with the full valgrind report and an explanation on why you think this is	4585	correct watcher to remove. The lists are usually short (you don't usually
3514	a bug in libev. However, don't be annoyed when you get a brisk "this is	4586	have many watchers waiting for the same fd or signal: one is typical, two
3515	no bug" answer and take the chance of learning how to interpret valgrind	4587	is rare).
3516	properly.
3517		4588
3518	If you need, for some reason, empty reports from valgrind for your project	4589	=item Finding the next timer in each loop iteration: O(1)
3519	I suggest using suppression lists.
3520		4590
		4591	By virtue of using a binary or 4-heap, the next timer is always found at a
		4592	fixed position in the storage array.
		4593
		4594	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
		4595
		4596	A change means an I/O watcher gets started or stopped, which requires
		4597	libev to recalculate its status (and possibly tell the kernel, depending
		4598	on backend and whether C<ev_io_set> was used).
		4599
		4600	=item Activating one watcher (putting it into the pending state): O(1)
		4601
		4602	=item Priority handling: O(number_of_priorities)
		4603
		4604	Priorities are implemented by allocating some space for each
		4605	priority. When doing priority-based operations, libev usually has to
		4606	linearly search all the priorities, but starting/stopping and activating
		4607	watchers becomes O(1) with respect to priority handling.
		4608
		4609	=item Sending an ev_async: O(1)
		4610
		4611	=item Processing ev_async_send: O(number_of_async_watchers)
		4612
		4613	=item Processing signals: O(max_signal_number)
		4614
		4615	Sending involves a system call I<iff> there were no other C<ev_async_send>
		4616	calls in the current loop iteration. Checking for async and signal events
		4617	involves iterating over all running async watchers or all signal numbers.
		4618
		4619	=back
		4620
		4621
		4622	=head1 GLOSSARY
		4623
		4624	=over 4
		4625
		4626	=item active
		4627
		4628	A watcher is active as long as it has been started (has been attached to
		4629	an event loop) but not yet stopped (disassociated from the event loop).
		4630
		4631	=item application
		4632
		4633	In this document, an application is whatever is using libev.
		4634
		4635	=item callback
		4636
		4637	The address of a function that is called when some event has been
		4638	detected. Callbacks are being passed the event loop, the watcher that
		4639	received the event, and the actual event bitset.
		4640
		4641	=item callback invocation
		4642
		4643	The act of calling the callback associated with a watcher.
		4644
		4645	=item event
		4646
		4647	A change of state of some external event, such as data now being available
		4648	for reading on a file descriptor, time having passed or simply not having
		4649	any other events happening anymore.
		4650
		4651	In libev, events are represented as single bits (such as C<EV_READ> or
		4652	C<EV_TIMEOUT>).
		4653
		4654	=item event library
		4655
		4656	A software package implementing an event model and loop.
		4657
		4658	=item event loop
		4659
		4660	An entity that handles and processes external events and converts them
		4661	into callback invocations.
		4662
		4663	=item event model
		4664
		4665	The model used to describe how an event loop handles and processes
		4666	watchers and events.
		4667
		4668	=item pending
		4669
		4670	A watcher is pending as soon as the corresponding event has been detected,
		4671	and stops being pending as soon as the watcher will be invoked or its
		4672	pending status is explicitly cleared by the application.
		4673
		4674	A watcher can be pending, but not active. Stopping a watcher also clears
		4675	its pending status.
		4676
		4677	=item real time
		4678
		4679	The physical time that is observed. It is apparently strictly monotonic :)
		4680
		4681	=item wall-clock time
		4682
		4683	The time and date as shown on clocks. Unlike real time, it can actually
		4684	be wrong and jump forwards and backwards, e.g. when the you adjust your
		4685	clock.
		4686
		4687	=item watcher
		4688
		4689	A data structure that describes interest in certain events. Watchers need
		4690	to be started (attached to an event loop) before they can receive events.
		4691
		4692	=item watcher invocation
		4693
		4694	The act of calling the callback associated with a watcher.
		4695
		4696	=back
3521		4697
3522	=head1 AUTHOR	4698	=head1 AUTHOR
3523		4699
3524	Marc Lehmann <libev@schmorp.de>.	4700	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson.
3525		4701

Diff Legend

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