ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.173 by root, Thu Aug 7 19:24:56 2008 UTC vs.
Revision 1.344 by root, Wed Nov 10 13:41:48 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);
28		30
29	// this causes all nested ev_loop's to stop iterating	31	// this causes all nested ev_run's to stop iterating
30	ev_unloop (EV_A_ EVUNLOOP_ALL);	32	ev_break (EV_A_ EVBREAK_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_run to stop iterating
39	ev_unloop (EV_A_ EVUNLOOP_ONE);	41	ev_break (EV_A_ EVBREAK_ONE);
40	}	42	}
41		43
42	int	44	int
43	main (void)	45	main (void)
44	{	46	{
45	// use the default event loop unless you have special needs	47	// use the default event loop unless you have special needs
46	struct ev_loop *loop = ev_default_loop (0);	48	struct ev_loop *loop = EV_DEFAULT;
47		49
48	// initialise an io watcher, then start it	50	// initialise an io watcher, then start it
49	// this one will watch for stdin to become readable	51	// this one will watch for stdin to become readable
50	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);	52	ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
51	ev_io_start (loop, &stdin_watcher);	53	ev_io_start (loop, &stdin_watcher);
…		…
54	// simple non-repeating 5.5 second timeout	56	// simple non-repeating 5.5 second timeout
55	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);	57	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
56	ev_timer_start (loop, &timeout_watcher);	58	ev_timer_start (loop, &timeout_watcher);
57		59
58	// now wait for events to arrive	60	// now wait for events to arrive
59	ev_loop (loop, 0);	61	ev_run (loop, 0);
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	Familiarity with event based programming techniques in general is assumed
		81	throughout this document.
		82
		83	=head1 WHAT TO READ WHEN IN A HURRY
		84
		85	This manual tries to be very detailed, but unfortunately, this also makes
		86	it very long. If you just want to know the basics of libev, I suggest
		87	reading L<ANATOMY OF A WATCHER>, then the L<EXAMPLE PROGRAM> above and
		88	look up the missing functions in L<GLOBAL FUNCTIONS> and the C<ev_io> and
		89	C<ev_timer> sections in L<WATCHER TYPES>.
		90
		91	=head1 ABOUT LIBEV
70		92
71	Libev is an event loop: you register interest in certain events (such as a	93	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	94	file descriptor being readable or a timeout occurring), and it will manage
73	these event sources and provide your program with events.	95	these event sources and provide your program with events.
74		96
…		…
84	=head2 FEATURES	106	=head2 FEATURES
85		107
86	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the	108	Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the
87	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms	109	BSD-specific C<kqueue> and the Solaris-specific event port mechanisms
88	for file descriptor events (C<ev_io>), the Linux C<inotify> interface	110	for file descriptor events (C<ev_io>), the Linux C<inotify> interface
89	(for C<ev_stat>), relative timers (C<ev_timer>), absolute timers	111	(for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner
90	with customised rescheduling (C<ev_periodic>), synchronous signals	112	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	113	timers (C<ev_timer>), absolute timers with customised rescheduling
92	watchers dealing with the event loop mechanism itself (C<ev_idle>,	114	(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	115	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	116	loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and
95	(C<ev_fork>).	117	C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even
		118	limited support for fork events (C<ev_fork>).
96		119
97	It also is quite fast (see this	120	It also is quite fast (see this
98	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent	121	L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent
99	for example).	122	for example).
100		123
…		…
108	name C<loop> (which is always of type C<struct ev_loop *>) will not have	131	name C<loop> (which is always of type C<struct ev_loop *>) will not have
109	this argument.	132	this argument.
110		133
111	=head2 TIME REPRESENTATION	134	=head2 TIME REPRESENTATION
112		135
113	Libev represents time as a single floating point number, representing the	136	Libev represents time as a single floating point number, representing
114	(fractional) number of seconds since the (POSIX) epoch (somewhere near	137	the (fractional) number of seconds since the (POSIX) epoch (in practice
115	the beginning of 1970, details are complicated, don't ask). This type is	138	somewhere near the beginning of 1970, details are complicated, don't
116	called C<ev_tstamp>, which is what you should use too. It usually aliases	139	ask). This type is called C<ev_tstamp>, which is what you should use
117	to the C<double> type in C, and when you need to do any calculations on	140	too. It usually aliases to the C<double> type in C. When you need to do
118	it, you should treat it as some floating point value. Unlike the name	141	any calculations on it, you should treat it as some floating point value.
		142
119	component C<stamp> might indicate, it is also used for time differences	143	Unlike the name component C<stamp> might indicate, it is also used for
120	throughout libev.	144	time differences (e.g. delays) throughout libev.
121		145
122	=head1 ERROR HANDLING	146	=head1 ERROR HANDLING
123		147
124	Libev knows three classes of errors: operating system errors, usage errors	148	Libev knows three classes of errors: operating system errors, usage errors
125	and internal errors (bugs).	149	and internal errors (bugs).
…		…
149		173
150	=item ev_tstamp ev_time ()	174	=item ev_tstamp ev_time ()
151		175
152	Returns the current time as libev would use it. Please note that the	176	Returns the current time as libev would use it. Please note that the
153	C<ev_now> function is usually faster and also often returns the timestamp	177	C<ev_now> function is usually faster and also often returns the timestamp
154	you actually want to know.	178	you actually want to know. Also interesting is the combination of
		179	C<ev_update_now> and C<ev_now>.
155		180
156	=item ev_sleep (ev_tstamp interval)	181	=item ev_sleep (ev_tstamp interval)
157		182
158	Sleep for the given interval: The current thread will be blocked until	183	Sleep for the given interval: The current thread will be blocked until
159	either it is interrupted or the given time interval has passed. Basically	184	either it is interrupted or the given time interval has passed. Basically
…		…
176	as this indicates an incompatible change. Minor versions are usually	201	as this indicates an incompatible change. Minor versions are usually
177	compatible to older versions, so a larger minor version alone is usually	202	compatible to older versions, so a larger minor version alone is usually
178	not a problem.	203	not a problem.
179		204
180	Example: Make sure we haven't accidentally been linked against the wrong	205	Example: Make sure we haven't accidentally been linked against the wrong
181	version.	206	version (note, however, that this will not detect other ABI mismatches,
		207	such as LFS or reentrancy).
182		208
183	assert (("libev version mismatch",	209	assert (("libev version mismatch",
184	ev_version_major () == EV_VERSION_MAJOR	210	ev_version_major () == EV_VERSION_MAJOR
185	&& ev_version_minor () >= EV_VERSION_MINOR));	211	&& ev_version_minor () >= EV_VERSION_MINOR));
186		212
…		…
197	assert (("sorry, no epoll, no sex",	223	assert (("sorry, no epoll, no sex",
198	ev_supported_backends () & EVBACKEND_EPOLL));	224	ev_supported_backends () & EVBACKEND_EPOLL));
199		225
200	=item unsigned int ev_recommended_backends ()	226	=item unsigned int ev_recommended_backends ()
201		227
202	Return the set of all backends compiled into this binary of libev and also	228	Return the set of all backends compiled into this binary of libev and
203	recommended for this platform. This set is often smaller than the one	229	also recommended for this platform, meaning it will work for most file
		230	descriptor types. This set is often smaller than the one returned by
204	returned by C<ev_supported_backends>, as for example kqueue is broken on	231	C<ev_supported_backends>, as for example kqueue is broken on most BSDs
205	most BSDs and will not be auto-detected unless you explicitly request it	232	and will not be auto-detected unless you explicitly request it (assuming
206	(assuming you know what you are doing). This is the set of backends that	233	you know what you are doing). This is the set of backends that libev will
207	libev will probe for if you specify no backends explicitly.	234	probe for if you specify no backends explicitly.
208		235
209	=item unsigned int ev_embeddable_backends ()	236	=item unsigned int ev_embeddable_backends ()
210		237
211	Returns the set of backends that are embeddable in other event loops. This	238	Returns the set of backends that are embeddable in other event loops. This
212	is the theoretical, all-platform, value. To find which backends	239	value is platform-specific but can include backends not available on the
213	might be supported on the current system, you would need to look at	240	current system. To find which embeddable backends might be supported on
214	C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for	241	the current system, you would need to look at C<ev_embeddable_backends ()
215	recommended ones.	242	& ev_supported_backends ()>, likewise for recommended ones.
216		243
217	See the description of C<ev_embed> watchers for more info.	244	See the description of C<ev_embed> watchers for more info.
218		245
219	=item ev_set_allocator (void *(*cb)(void *ptr, long size))	246	=item ev_set_allocator (void *(*cb)(void *ptr, long size))
220		247
…		…
250	}	277	}
251		278
252	...	279	...
253	ev_set_allocator (persistent_realloc);	280	ev_set_allocator (persistent_realloc);
254		281
255	=item ev_set_syserr_cb (void (*cb)(const char *msg));	282	=item ev_set_syserr_cb (void (*cb)(const char *msg))
256		283
257	Set the callback function to call on a retryable system call error (such	284	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	285	as failed select, poll, epoll_wait). The message is a printable string
259	indicating the system call or subsystem causing the problem. If this	286	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	287	callback is set, then libev will expect it to remedy the situation, no
…		…
274	...	301	...
275	ev_set_syserr_cb (fatal_error);	302	ev_set_syserr_cb (fatal_error);
276		303
277	=back	304	=back
278		305
279	=head1 FUNCTIONS CONTROLLING THE EVENT LOOP	306	=head1 FUNCTIONS CONTROLLING EVENT LOOPS
280		307
281	An event loop is described by a C<struct ev_loop *>. The library knows two	308	An event loop is described by a C<struct ev_loop *> (the C<struct> is
282	types of such loops, the I<default> loop, which supports signals and child	309	I<not> optional in this case unless libev 3 compatibility is disabled, as
283	events, and dynamically created loops which do not.	310	libev 3 had an C<ev_loop> function colliding with the struct name).
		311
		312	The library knows two types of such loops, the I<default> loop, which
		313	supports child process events, and dynamically created event loops which
		314	do not.
284		315
285	=over 4	316	=over 4
286		317
287	=item struct ev_loop *ev_default_loop (unsigned int flags)	318	=item struct ev_loop *ev_default_loop (unsigned int flags)
288		319
289	This will initialise the default event loop if it hasn't been initialised	320	This returns the "default" event loop object, which is what you should
290	yet and return it. If the default loop could not be initialised, returns	321	normally use when you just need "the event loop". Event loop objects and
291	false. If it already was initialised it simply returns it (and ignores the	322	the C<flags> parameter are described in more detail in the entry for
292	flags. If that is troubling you, check C<ev_backend ()> afterwards).	323	C<ev_loop_new>.
		324
		325	If the default loop is already initialised then this function simply
		326	returns it (and ignores the flags. If that is troubling you, check
		327	C<ev_backend ()> afterwards). Otherwise it will create it with the given
		328	flags, which should almost always be C<0>, unless the caller is also the
		329	one calling C<ev_run> or otherwise qualifies as "the main program".
293		330
294	If you don't know what event loop to use, use the one returned from this	331	If you don't know what event loop to use, use the one returned from this
295	function.	332	function (or via the C<EV_DEFAULT> macro).
296		333
297	Note that this function is I<not> thread-safe, so if you want to use it	334	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,	335	from multiple threads, you have to employ some kind of mutex (note also
299	as loops cannot bes hared easily between threads anyway).	336	that this case is unlikely, as loops cannot be shared easily between
		337	threads anyway).
300		338
301	The default loop is the only loop that can handle C<ev_signal> and	339	The default loop is the only loop that can handle C<ev_child> watchers,
302	C<ev_child> watchers, and to do this, it always registers a handler	340	and to do this, it always registers a handler for C<SIGCHLD>. If this is
303	for C<SIGCHLD>. If this is a problem for your application you can either	341	a problem for your application you can either create a dynamic loop with
304	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	342	C<ev_loop_new> which doesn't do that, or you can simply overwrite the
305	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	343	C<SIGCHLD> signal handler I<after> calling C<ev_default_init>.
306	C<ev_default_init>.	344
		345	Example: This is the most typical usage.
		346
		347	if (!ev_default_loop (0))
		348	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
		349
		350	Example: Restrict libev to the select and poll backends, and do not allow
		351	environment settings to be taken into account:
		352
		353	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
		354
		355	=item struct ev_loop *ev_loop_new (unsigned int flags)
		356
		357	This will create and initialise a new event loop object. If the loop
		358	could not be initialised, returns false.
		359
		360	This function is thread-safe, and one common way to use libev with
		361	threads is indeed to create one loop per thread, and using the default
		362	loop in the "main" or "initial" thread.
307		363
308	The flags argument can be used to specify special behaviour or specific	364	The flags argument can be used to specify special behaviour or specific
309	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).	365	backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
310		366
311	The following flags are supported:	367	The following flags are supported:
…		…
326	useful to try out specific backends to test their performance, or to work	382	useful to try out specific backends to test their performance, or to work
327	around bugs.	383	around bugs.
328		384
329	=item C<EVFLAG_FORKCHECK>	385	=item C<EVFLAG_FORKCHECK>
330		386
331	Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after	387	Instead of calling C<ev_loop_fork> manually after a fork, you can also
332	a fork, you can also make libev check for a fork in each iteration by	388	make libev check for a fork in each iteration by enabling this flag.
333	enabling this flag.
334		389
335	This works by calling C<getpid ()> on every iteration of the loop,	390	This works by calling C<getpid ()> on every iteration of the loop,
336	and thus this might slow down your event loop if you do a lot of loop	391	and thus this might slow down your event loop if you do a lot of loop
337	iterations and little real work, but is usually not noticeable (on my	392	iterations and little real work, but is usually not noticeable (on my
338	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence	393	GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence
…		…
344	flag.	399	flag.
345		400
346	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>	401	This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
347	environment variable.	402	environment variable.
348		403
		404	=item C<EVFLAG_NOINOTIFY>
		405
		406	When this flag is specified, then libev will not attempt to use the
		407	I<inotify> API for its C<ev_stat> watchers. Apart from debugging and
		408	testing, this flag can be useful to conserve inotify file descriptors, as
		409	otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
		410
		411	=item C<EVFLAG_SIGNALFD>
		412
		413	When this flag is specified, then libev will attempt to use the
		414	I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API
		415	delivers signals synchronously, which makes it both faster and might make
		416	it possible to get the queued signal data. It can also simplify signal
		417	handling with threads, as long as you properly block signals in your
		418	threads that are not interested in handling them.
		419
		420	Signalfd will not be used by default as this changes your signal mask, and
		421	there are a lot of shoddy libraries and programs (glib's threadpool for
		422	example) that can't properly initialise their signal masks.
		423
349	=item C<EVBACKEND_SELECT> (value 1, portable select backend)	424	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
350		425
351	This is your standard select(2) backend. Not I<completely> standard, as	426	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,	427	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	428	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	434	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	435	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	436	a look at C<ev_set_io_collect_interval ()> to increase the amount of
362	readiness notifications you get per iteration.	437	readiness notifications you get per iteration.
363		438
		439	This backend maps C<EV_READ> to the C<readfds> set and C<EV_WRITE> to the
		440	C<writefds> set (and to work around Microsoft Windows bugs, also onto the
		441	C<exceptfds> set on that platform).
		442
364	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)	443	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
365		444
366	And this is your standard poll(2) backend. It's more complicated	445	And this is your standard poll(2) backend. It's more complicated
367	than select, but handles sparse fds better and has no artificial	446	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	447	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,	448	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	449	i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for
371	performance tips.	450	performance tips.
372		451
		452	This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and
		453	C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>.
		454
373	=item C<EVBACKEND_EPOLL> (value 4, Linux)	455	=item C<EVBACKEND_EPOLL> (value 4, Linux)
		456
		457	Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9
		458	kernels).
374		459
375	For few fds, this backend is a bit little slower than poll and select,	460	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	461	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),	462	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	463	epoll scales either O(1) or O(active_fds).
379	of shortcomings, such as silently dropping events in some hard-to-detect	464
380	cases and requiring a system call per fd change, no fork support and bad	465	The epoll mechanism deserves honorable mention as the most misdesigned
381	support for dup.	466	of the more advanced event mechanisms: mere annoyances include silently
		467	dropping file descriptors, requiring a system call per change per file
		468	descriptor (and unnecessary guessing of parameters), problems with dup,
		469	returning before the timeout value, resulting in additional iterations
		470	(and only giving 5ms accuracy while select on the same platform gives
		471	0.1ms) and so on. The biggest issue is fork races, however - if a program
		472	forks then I<both> parent and child process have to recreate the epoll
		473	set, which can take considerable time (one syscall per file descriptor)
		474	and is of course hard to detect.
		475
		476	Epoll is also notoriously buggy - embedding epoll fds I<should> work, but
		477	of course I<doesn't>, and epoll just loves to report events for totally
		478	I<different> file descriptors (even already closed ones, so one cannot
		479	even remove them from the set) than registered in the set (especially
		480	on SMP systems). Libev tries to counter these spurious notifications by
		481	employing an additional generation counter and comparing that against the
		482	events to filter out spurious ones, recreating the set when required. Last
		483	not least, it also refuses to work with some file descriptors which work
		484	perfectly fine with C<select> (files, many character devices...).
		485
		486	Epoll is truly the train wreck analog among event poll mechanisms.
382		487
383	While stopping, setting and starting an I/O watcher in the same iteration	488	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	489	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	490	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	491	I<file description> now), so its best to avoid that. Also, C<dup ()>'ed
387	very well if you register events for both fds.	492	file descriptors might not work very well if you register events for both
388		493	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		494
393	Best performance from this backend is achieved by not unregistering all	495	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.	496	watchers for a file descriptor until it has been closed, if possible,
395	keep at least one watcher active per fd at all times.	497	i.e. keep at least one watcher active per fd at all times. Stopping and
		498	starting a watcher (without re-setting it) also usually doesn't cause
		499	extra overhead. A fork can both result in spurious notifications as well
		500	as in libev having to destroy and recreate the epoll object, which can
		501	take considerable time and thus should be avoided.
		502
		503	All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or
		504	faster than epoll for maybe up to a hundred file descriptors, depending on
		505	the usage. So sad.
396		506
397	While nominally embeddable in other event loops, this feature is broken in	507	While nominally embeddable in other event loops, this feature is broken in
398	all kernel versions tested so far.	508	all kernel versions tested so far.
		509
		510	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		511	C<EVBACKEND_POLL>.
399		512
400	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)	513	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
401		514
402	Kqueue deserves special mention, as at the time of this writing, it	515	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	516	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	517	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"	518	it's completely useless). Unlike epoll, however, whose brokenness
		519	is by design, these kqueue bugs can (and eventually will) be fixed
		520	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	521	"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)	522	C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough)
408	system like NetBSD.	523	system like NetBSD.
409		524
410	You still can embed kqueue into a normal poll or select backend and use it	525	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	526	only for sockets (after having made sure that sockets work with kqueue on
…		…
413		528
414	It scales in the same way as the epoll backend, but the interface to the	529	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	530	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	531	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	532	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	533	two event changes per incident. Support for C<fork ()> is very bad (but
419	drops fds silently in similarly hard-to-detect cases.	534	sane, unlike epoll) and it drops fds silently in similarly hard-to-detect
		535	cases
420		536
421	This backend usually performs well under most conditions.	537	This backend usually performs well under most conditions.
422		538
423	While nominally embeddable in other event loops, this doesn't work	539	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	540	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	541	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	542	(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	543	(e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course
428	sockets.	544	also broken on OS X)) and, did I mention it, using it only for sockets.
		545
		546	This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with
		547	C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with
		548	C<NOTE_EOF>.
429		549
430	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)	550	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
431		551
432	This is not implemented yet (and might never be, unless you send me an	552	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	553	implementation). According to reports, C</dev/poll> only supports sockets
…		…
446	While this backend scales well, it requires one system call per active	566	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	567	file descriptor per loop iteration. For small and medium numbers of file
448	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend	568	descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
449	might perform better.	569	might perform better.
450		570
451	On the positive side, ignoring the spurious readiness notifications, this	571	On the positive side, with the exception of the spurious readiness
452	backend actually performed to specification in all tests and is fully	572	notifications, this backend actually performed fully to specification
453	embeddable, which is a rare feat among the OS-specific backends.	573	in all tests and is fully embeddable, which is a rare feat among the
		574	OS-specific backends (I vastly prefer correctness over speed hacks).
		575
		576	This backend maps C<EV_READ> and C<EV_WRITE> in the same way as
		577	C<EVBACKEND_POLL>.
454		578
455	=item C<EVBACKEND_ALL>	579	=item C<EVBACKEND_ALL>
456		580
457	Try all backends (even potentially broken ones that wouldn't be tried	581	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	582	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
…		…
460		584
461	It is definitely not recommended to use this flag.	585	It is definitely not recommended to use this flag.
462		586
463	=back	587	=back
464		588
465	If one or more of these are or'ed into the flags value, then only these	589	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	590	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.	591	here). If none are specified, all backends in C<ev_recommended_backends
468		592	()> will be tried.
469	The most typical usage is like this:
470
471	if (!ev_default_loop (0))
472	fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
473
474	Restrict libev to the select and poll backends, and do not allow
475	environment settings to be taken into account:
476
477	ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
478
479	Use whatever libev has to offer, but make sure that kqueue is used if
480	available (warning, breaks stuff, best use only with your own private
481	event loop and only if you know the OS supports your types of fds):
482
483	ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
484
485	=item struct ev_loop *ev_loop_new (unsigned int flags)
486
487	Similar to C<ev_default_loop>, but always creates a new event loop that is
488	always distinct from the default loop. Unlike the default loop, it cannot
489	handle signal and child watchers, and attempts to do so will be greeted by
490	undefined behaviour (or a failed assertion if assertions are enabled).
491
492	Note that this function I<is> thread-safe, and the recommended way to use
493	libev with threads is indeed to create one loop per thread, and using the
494	default loop in the "main" or "initial" thread.
495		593
496	Example: Try to create a event loop that uses epoll and nothing else.	594	Example: Try to create a event loop that uses epoll and nothing else.
497		595
498	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);	596	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
499	if (!epoller)	597	if (!epoller)
500	fatal ("no epoll found here, maybe it hides under your chair");	598	fatal ("no epoll found here, maybe it hides under your chair");
501		599
		600	Example: Use whatever libev has to offer, but make sure that kqueue is
		601	used if available.
		602
		603	struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE);
		604
502	=item ev_default_destroy ()	605	=item ev_loop_destroy (loop)
503		606
504	Destroys the default loop again (frees all memory and kernel state	607	Destroys an event loop object (frees all memory and kernel state
505	etc.). None of the active event watchers will be stopped in the normal	608	etc.). None of the active event watchers will be stopped in the normal
506	sense, so e.g. C<ev_is_active> might still return true. It is your	609	sense, so e.g. C<ev_is_active> might still return true. It is your
507	responsibility to either stop all watchers cleanly yourself I<before>	610	responsibility to either stop all watchers cleanly yourself I<before>
508	calling this function, or cope with the fact afterwards (which is usually	611	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	612	the easiest thing, you can just ignore the watchers and/or C<free ()> them
510	for example).	613	for example).
511		614
512	Note that certain global state, such as signal state, will not be freed by	615	Note that certain global state, such as signal state (and installed signal
513	this function, and related watchers (such as signal and child watchers)	616	handlers), will not be freed by this function, and related watchers (such
514	would need to be stopped manually.	617	as signal and child watchers) would need to be stopped manually.
515		618
516	In general it is not advisable to call this function except in the	619	This function is normally used on loop objects allocated by
517	rare occasion where you really need to free e.g. the signal handling	620	C<ev_loop_new>, but it can also be used on the default loop returned by
		621	C<ev_default_loop>, in which case it is not thread-safe.
		622
		623	Note that it is not advisable to call this function on the default loop
		624	except in the rare occasion where you really need to free its resources.
518	pipe fds. If you need dynamically allocated loops it is better to use	625	If you need dynamically allocated loops it is better to use C<ev_loop_new>
519	C<ev_loop_new> and C<ev_loop_destroy>).	626	and C<ev_loop_destroy>.
520		627
521	=item ev_loop_destroy (loop)	628	=item ev_loop_fork (loop)
522		629
523	Like C<ev_default_destroy>, but destroys an event loop created by an
524	earlier call to C<ev_loop_new>.
525
526	=item ev_default_fork ()
527
528	This function sets a flag that causes subsequent C<ev_loop> iterations	630	This function sets a flag that causes subsequent C<ev_run> iterations to
529	to reinitialise the kernel state for backends that have one. Despite the	631	reinitialise the kernel state for backends that have one. Despite the
530	name, you can call it anytime, but it makes most sense after forking, in	632	name, you can call it anytime, but it makes most sense after forking, in
531	the child process (or both child and parent, but that again makes little	633	the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
532	sense). You I<must> call it in the child before using any of the libev	634	child before resuming or calling C<ev_run>.
533	functions, and it will only take effect at the next C<ev_loop> iteration.	635
		636	Again, you I<have> to call it on I<any> loop that you want to re-use after
		637	a fork, I<even if you do not plan to use the loop in the parent>. This is
		638	because some kernel interfaces *cough* I<kqueue> *cough* do funny things
		639	during fork.
534		640
535	On the other hand, you only need to call this function in the child	641	On the other hand, you only need to call this function in the child
536	process if and only if you want to use the event library in the child. If	642	process if and only if you want to use the event loop in the child. If
537	you just fork+exec, you don't have to call it at all.	643	you just fork+exec or create a new loop in the child, you don't have to
		644	call it at all (in fact, C<epoll> is so badly broken that it makes a
		645	difference, but libev will usually detect this case on its own and do a
		646	costly reset of the backend).
538		647
539	The function itself is quite fast and it's usually not a problem to call	648	The function itself is quite fast and it's usually not a problem to call
540	it just in case after a fork. To make this easy, the function will fit in	649	it just in case after a fork.
541	quite nicely into a call to C<pthread_atfork>:
542		650
		651	Example: Automate calling C<ev_loop_fork> on the default loop when
		652	using pthreads.
		653
		654	static void
		655	post_fork_child (void)
		656	{
		657	ev_loop_fork (EV_DEFAULT);
		658	}
		659
		660	...
543	pthread_atfork (0, 0, ev_default_fork);	661	pthread_atfork (0, 0, post_fork_child);
544
545	=item ev_loop_fork (loop)
546
547	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
549	after fork, and how you do this is entirely your own problem.
550		662
551	=item int ev_is_default_loop (loop)	663	=item int ev_is_default_loop (loop)
552		664
553	Returns true when the given loop actually is the default loop, false otherwise.	665	Returns true when the given loop is, in fact, the default loop, and false
		666	otherwise.
554		667
555	=item unsigned int ev_loop_count (loop)	668	=item unsigned int ev_iteration (loop)
556		669
557	Returns the count of loop iterations for the loop, which is identical to	670	Returns the current iteration count for the event loop, which is identical
558	the number of times libev did poll for new events. It starts at C<0> and	671	to the number of times libev did poll for new events. It starts at C<0>
559	happily wraps around with enough iterations.	672	and happily wraps around with enough iterations.
560		673
561	This value can sometimes be useful as a generation counter of sorts (it	674	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	675	"ticks" the number of loop iterations), as it roughly corresponds with
563	C<ev_prepare> and C<ev_check> calls.	676	C<ev_prepare> and C<ev_check> calls - and is incremented between the
		677	prepare and check phases.
		678
		679	=item unsigned int ev_depth (loop)
		680
		681	Returns the number of times C<ev_run> was entered minus the number of
		682	times C<ev_run> was exited normally, in other words, the recursion depth.
		683
		684	Outside C<ev_run>, this number is zero. In a callback, this number is
		685	C<1>, unless C<ev_run> was invoked recursively (or from another thread),
		686	in which case it is higher.
		687
		688	Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread,
		689	throwing an exception etc.), doesn't count as "exit" - consider this
		690	as a hint to avoid such ungentleman-like behaviour unless it's really
		691	convenient, in which case it is fully supported.
564		692
565	=item unsigned int ev_backend (loop)	693	=item unsigned int ev_backend (loop)
566		694
567	Returns one of the C<EVBACKEND_*> flags indicating the event backend in	695	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
568	use.	696	use.
…		…
573	received events and started processing them. This timestamp does not	701	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	702	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	703	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).	704	event occurring (or more correctly, libev finding out about it).
577		705
		706	=item ev_now_update (loop)
		707
		708	Establishes the current time by querying the kernel, updating the time
		709	returned by C<ev_now ()> in the progress. This is a costly operation and
		710	is usually done automatically within C<ev_run ()>.
		711
		712	This function is rarely useful, but when some event callback runs for a
		713	very long time without entering the event loop, updating libev's idea of
		714	the current time is a good idea.
		715
		716	See also L<The special problem of time updates> in the C<ev_timer> section.
		717
		718	=item ev_suspend (loop)
		719
		720	=item ev_resume (loop)
		721
		722	These two functions suspend and resume an event loop, for use when the
		723	loop is not used for a while and timeouts should not be processed.
		724
		725	A typical use case would be an interactive program such as a game: When
		726	the user presses C<^Z> to suspend the game and resumes it an hour later it
		727	would be best to handle timeouts as if no time had actually passed while
		728	the program was suspended. This can be achieved by calling C<ev_suspend>
		729	in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
		730	C<ev_resume> directly afterwards to resume timer processing.
		731
		732	Effectively, all C<ev_timer> watchers will be delayed by the time spend
		733	between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers
		734	will be rescheduled (that is, they will lose any events that would have
		735	occurred while suspended).
		736
		737	After calling C<ev_suspend> you B<must not> call I<any> function on the
		738	given loop other than C<ev_resume>, and you B<must not> call C<ev_resume>
		739	without a previous call to C<ev_suspend>.
		740
		741	Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the
		742	event loop time (see C<ev_now_update>).
		743
578	=item ev_loop (loop, int flags)	744	=item ev_run (loop, int flags)
579		745
580	Finally, this is it, the event handler. This function usually is called	746	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	747	after you have initialised all your watchers and you want to start
582	events.	748	handling events. It will ask the operating system for any new events, call
		749	the watcher callbacks, an then repeat the whole process indefinitely: This
		750	is why event loops are called I<loops>.
583		751
584	If the flags argument is specified as C<0>, it will not return until	752	If the flags argument is specified as C<0>, it will keep handling events
585	either no event watchers are active anymore or C<ev_unloop> was called.	753	until either no event watchers are active anymore or C<ev_break> was
		754	called.
586		755
587	Please note that an explicit C<ev_unloop> is usually better than	756	Please note that an explicit C<ev_break> is usually better than
588	relying on all watchers to be stopped when deciding when a program has	757	relying on all watchers to be stopped when deciding when a program has
589	finished (especially in interactive programs), but having a program that	758	finished (especially in interactive programs), but having a program
590	automatically loops as long as it has to and no longer by virtue of	759	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.	760	of relying on its watchers stopping correctly, that is truly a thing of
		761	beauty.
592		762
		763	This function is also I<mostly> exception-safe - you can break out of
		764	a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++
		765	exception and so on. This does not decrement the C<ev_depth> value, nor
		766	will it clear any outstanding C<EVBREAK_ONE> breaks.
		767
593	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	768	A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
594	those events and any outstanding ones, but will not block your process in	769	those events and any already outstanding ones, but will not wait and
595	case there are no events and will return after one iteration of the loop.	770	block your process in case there are no events and will return after one
		771	iteration of the loop. This is sometimes useful to poll and handle new
		772	events while doing lengthy calculations, to keep the program responsive.
596		773
597	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	774	A flags value of C<EVRUN_ONCE> will look for new events (waiting if
598	necessary) and will handle those and any outstanding ones. It will block	775	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	776	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	777	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	778	user-registered callback will be called), and will return after one
		779	iteration of the loop.
		780
		781	This is useful if you are waiting for some external event in conjunction
		782	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	783	own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is
603	usually a better approach for this kind of thing.	784	usually a better approach for this kind of thing.
604		785
605	Here are the gory details of what C<ev_loop> does:	786	Here are the gory details of what C<ev_run> does:
606		787
		788	- Increment loop depth.
		789	- Reset the ev_break status.
607	- Before the first iteration, call any pending watchers.	790	- Before the first iteration, call any pending watchers.
		791	LOOP:
608	* If EVFLAG_FORKCHECK was used, check for a fork.	792	- If EVFLAG_FORKCHECK was used, check for a fork.
609	- If a fork was detected (by any means), queue and call all fork watchers.	793	- If a fork was detected (by any means), queue and call all fork watchers.
610	- Queue and call all prepare watchers.	794	- Queue and call all prepare watchers.
		795	- If ev_break was called, goto FINISH.
611	- If we have been forked, detach and recreate the kernel state	796	- If we have been forked, detach and recreate the kernel state
612	as to not disturb the other process.	797	as to not disturb the other process.
613	- Update the kernel state with all outstanding changes.	798	- Update the kernel state with all outstanding changes.
614	- Update the "event loop time" (ev_now ()).	799	- Update the "event loop time" (ev_now ()).
615	- Calculate for how long to sleep or block, if at all	800	- Calculate for how long to sleep or block, if at all
616	(active idle watchers, EVLOOP_NONBLOCK or not having	801	(active idle watchers, EVRUN_NOWAIT or not having
617	any active watchers at all will result in not sleeping).	802	any active watchers at all will result in not sleeping).
618	- Sleep if the I/O and timer collect interval say so.	803	- Sleep if the I/O and timer collect interval say so.
		804	- Increment loop iteration counter.
619	- Block the process, waiting for any events.	805	- Block the process, waiting for any events.
620	- Queue all outstanding I/O (fd) events.	806	- Queue all outstanding I/O (fd) events.
621	- Update the "event loop time" (ev_now ()), and do time jump adjustments.	807	- Update the "event loop time" (ev_now ()), and do time jump adjustments.
622	- Queue all outstanding timers.	808	- Queue all expired timers.
623	- Queue all outstanding periodics.	809	- Queue all expired periodics.
624	- Unless any events are pending now, queue all idle watchers.	810	- Queue all idle watchers with priority higher than that of pending events.
625	- Queue all check watchers.	811	- Queue all check watchers.
626	- Call all queued watchers in reverse order (i.e. check watchers first).	812	- 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	813	Signals and child watchers are implemented as I/O watchers, and will
628	be handled here by queueing them when their watcher gets executed.	814	be handled here by queueing them when their watcher gets executed.
629	- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK	815	- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT
630	were used, or there are no active watchers, return, otherwise	816	were used, or there are no active watchers, goto FINISH, otherwise
631	continue with step *.	817	continue with step LOOP.
		818	FINISH:
		819	- Reset the ev_break status iff it was EVBREAK_ONE.
		820	- Decrement the loop depth.
		821	- Return.
632		822
633	Example: Queue some jobs and then loop until no events are outstanding	823	Example: Queue some jobs and then loop until no events are outstanding
634	anymore.	824	anymore.
635		825
636	... queue jobs here, make sure they register event watchers as long	826	... queue jobs here, make sure they register event watchers as long
637	... as they still have work to do (even an idle watcher will do..)	827	... as they still have work to do (even an idle watcher will do..)
638	ev_loop (my_loop, 0);	828	ev_run (my_loop, 0);
639	... jobs done or somebody called unloop. yeah!	829	... jobs done or somebody called unloop. yeah!
640		830
641	=item ev_unloop (loop, how)	831	=item ev_break (loop, how)
642		832
643	Can be used to make a call to C<ev_loop> return early (but only after it	833	Can be used to make a call to C<ev_run> return early (but only after it
644	has processed all outstanding events). The C<how> argument must be either	834	has processed all outstanding events). The C<how> argument must be either
645	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or	835	C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or
646	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	836	C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return.
647		837
648	This "unloop state" will be cleared when entering C<ev_loop> again.	838	This "break state" will be cleared on the next call to C<ev_run>.
		839
		840	It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in
		841	which case it will have no effect.
649		842
650	=item ev_ref (loop)	843	=item ev_ref (loop)
651		844
652	=item ev_unref (loop)	845	=item ev_unref (loop)
653		846
654	Ref/unref can be used to add or remove a reference count on the event	847	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	848	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	849	count is nonzero, C<ev_run> will not return on its own.
657	a watcher you never unregister that should not keep C<ev_loop> from	850
658	returning, ev_unref() after starting, and ev_ref() before stopping it. For	851	This is useful when you have a watcher that you never intend to
		852	unregister, but that nevertheless should not keep C<ev_run> from
		853	returning. In such a case, call C<ev_unref> after starting, and C<ev_ref>
		854	before stopping it.
		855
659	example, libev itself uses this for its internal signal pipe: It is not	856	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	857	is not visible to the libev user and should not keep C<ev_run> from
661	no event watchers registered by it are active. It is also an excellent	858	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	859	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>	860	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,	861	before stop> (but only if the watcher wasn't active before, or was active
665	respectively).	862	before, respectively. Note also that libev might stop watchers itself
		863	(e.g. non-repeating timers) in which case you have to C<ev_ref>
		864	in the callback).
666		865
667	Example: Create a signal watcher, but keep it from keeping C<ev_loop>	866	Example: Create a signal watcher, but keep it from keeping C<ev_run>
668	running when nothing else is active.	867	running when nothing else is active.
669		868
670	struct ev_signal exitsig;	869	ev_signal exitsig;
671	ev_signal_init (&exitsig, sig_cb, SIGINT);	870	ev_signal_init (&exitsig, sig_cb, SIGINT);
672	ev_signal_start (loop, &exitsig);	871	ev_signal_start (loop, &exitsig);
673	evf_unref (loop);	872	evf_unref (loop);
674		873
675	Example: For some weird reason, unregister the above signal handler again.	874	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>)	888	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	889	allows libev to delay invocation of I/O and timer/periodic callbacks
691	to increase efficiency of loop iterations (or to increase power-saving	890	to increase efficiency of loop iterations (or to increase power-saving
692	opportunities).	891	opportunities).
693		892
694	The background is that sometimes your program runs just fast enough to	893	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	894	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	895	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	896	events, especially with backends like C<select ()> which have a high
698	overhead for the actual polling but can deliver many events at once.	897	overhead for the actual polling but can deliver many events at once.
699		898
700	By setting a higher I<io collect interval> you allow libev to spend more	899	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,	900	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	901	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	902	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.	903	introduce an additional C<ev_sleep ()> call into most loop iterations. The
		904	sleep time ensures that libev will not poll for I/O events more often then
		905	once per this interval, on average.
705		906
706	Likewise, by setting a higher I<timeout collect interval> you allow libev	907	Likewise, by setting a higher I<timeout collect interval> you allow libev
707	to spend more time collecting timeouts, at the expense of increased	908	to spend more time collecting timeouts, at the expense of increased
708	latency (the watcher callback will be called later). C<ev_io> watchers	909	latency/jitter/inexactness (the watcher callback will be called
709	will not be affected. Setting this to a non-null value will not introduce	910	later). C<ev_io> watchers will not be affected. Setting this to a non-null
710	any overhead in libev.	911	value will not introduce any overhead in libev.
711		912
712	Many (busy) programs can usually benefit by setting the I/O collect	913	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	914	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	915	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>,	916	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.	917	as this approaches the timing granularity of most systems. Note that if
		918	you do transactions with the outside world and you can't increase the
		919	parallelity, then this setting will limit your transaction rate (if you
		920	need to poll once per transaction and the I/O collect interval is 0.01,
		921	then you can't do more than 100 transactions per second).
717		922
718	Setting the I<timeout collect interval> can improve the opportunity for	923	Setting the I<timeout collect interval> can improve the opportunity for
719	saving power, as the program will "bundle" timer callback invocations that	924	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	925	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	926	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	927	reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure
723	they fire on, say, one-second boundaries only.	928	they fire on, say, one-second boundaries only.
724		929
		930	Example: we only need 0.1s timeout granularity, and we wish not to poll
		931	more often than 100 times per second:
		932
		933	ev_set_timeout_collect_interval (EV_DEFAULT_UC_ 0.1);
		934	ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01);
		935
		936	=item ev_invoke_pending (loop)
		937
		938	This call will simply invoke all pending watchers while resetting their
		939	pending state. Normally, C<ev_run> does this automatically when required,
		940	but when overriding the invoke callback this call comes handy. This
		941	function can be invoked from a watcher - this can be useful for example
		942	when you want to do some lengthy calculation and want to pass further
		943	event handling to another thread (you still have to make sure only one
		944	thread executes within C<ev_invoke_pending> or C<ev_run> of course).
		945
		946	=item int ev_pending_count (loop)
		947
		948	Returns the number of pending watchers - zero indicates that no watchers
		949	are pending.
		950
		951	=item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P))
		952
		953	This overrides the invoke pending functionality of the loop: Instead of
		954	invoking all pending watchers when there are any, C<ev_run> will call
		955	this callback instead. This is useful, for example, when you want to
		956	invoke the actual watchers inside another context (another thread etc.).
		957
		958	If you want to reset the callback, use C<ev_invoke_pending> as new
		959	callback.
		960
		961	=item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))
		962
		963	Sometimes you want to share the same loop between multiple threads. This
		964	can be done relatively simply by putting mutex_lock/unlock calls around
		965	each call to a libev function.
		966
		967	However, C<ev_run> can run an indefinite time, so it is not feasible
		968	to wait for it to return. One way around this is to wake up the event
		969	loop via C<ev_break> and C<av_async_send>, another way is to set these
		970	I<release> and I<acquire> callbacks on the loop.
		971
		972	When set, then C<release> will be called just before the thread is
		973	suspended waiting for new events, and C<acquire> is called just
		974	afterwards.
		975
		976	Ideally, C<release> will just call your mutex_unlock function, and
		977	C<acquire> will just call the mutex_lock function again.
		978
		979	While event loop modifications are allowed between invocations of
		980	C<release> and C<acquire> (that's their only purpose after all), no
		981	modifications done will affect the event loop, i.e. adding watchers will
		982	have no effect on the set of file descriptors being watched, or the time
		983	waited. Use an C<ev_async> watcher to wake up C<ev_run> when you want it
		984	to take note of any changes you made.
		985
		986	In theory, threads executing C<ev_run> will be async-cancel safe between
		987	invocations of C<release> and C<acquire>.
		988
		989	See also the locking example in the C<THREADS> section later in this
		990	document.
		991
		992	=item ev_set_userdata (loop, void *data)
		993
		994	=item void *ev_userdata (loop)
		995
		996	Set and retrieve a single C<void *> associated with a loop. When
		997	C<ev_set_userdata> has never been called, then C<ev_userdata> returns
		998	C<0>.
		999
		1000	These two functions can be used to associate arbitrary data with a loop,
		1001	and are intended solely for the C<invoke_pending_cb>, C<release> and
		1002	C<acquire> callbacks described above, but of course can be (ab-)used for
		1003	any other purpose as well.
		1004
725	=item ev_loop_verify (loop)	1005	=item ev_verify (loop)
726		1006
727	This function only does something when C<EV_VERIFY> support has been	1007	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	1008	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	1009	through all internal structures and checks them for validity. If anything
730	an error message to standard error and call C<abort ()>.	1010	is found to be inconsistent, it will print an error message to standard
		1011	error and call C<abort ()>.
731		1012
732	This can be used to catch bugs inside libev itself: under normal	1013	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	1014	circumstances, this function will never abort as of course libev keeps its
734	data structures consistent.	1015	data structures consistent.
735		1016
736	=back	1017	=back
737		1018
738		1019
739	=head1 ANATOMY OF A WATCHER	1020	=head1 ANATOMY OF A WATCHER
740		1021
		1022	In the following description, uppercase C<TYPE> in names stands for the
		1023	watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
		1024	watchers and C<ev_io_start> for I/O watchers.
		1025
741	A watcher is a structure that you create and register to record your	1026	A watcher is an opaque structure that you allocate and register to record
742	interest in some event. For instance, if you want to wait for STDIN to	1027	your interest in some event. To make a concrete example, imagine you want
743	become readable, you would create an C<ev_io> watcher for that:	1028	to wait for STDIN to become readable, you would create an C<ev_io> watcher
		1029	for that:
744		1030
745	static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1031	static void my_cb (struct ev_loop *loop, ev_io *w, int revents)
746	{	1032	{
747	ev_io_stop (w);	1033	ev_io_stop (w);
748	ev_unloop (loop, EVUNLOOP_ALL);	1034	ev_break (loop, EVBREAK_ALL);
749	}	1035	}
750		1036
751	struct ev_loop *loop = ev_default_loop (0);	1037	struct ev_loop *loop = ev_default_loop (0);
		1038
752	struct ev_io stdin_watcher;	1039	ev_io stdin_watcher;
		1040
753	ev_init (&stdin_watcher, my_cb);	1041	ev_init (&stdin_watcher, my_cb);
754	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);	1042	ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ);
755	ev_io_start (loop, &stdin_watcher);	1043	ev_io_start (loop, &stdin_watcher);
		1044
756	ev_loop (loop, 0);	1045	ev_run (loop, 0);
757		1046
758	As you can see, you are responsible for allocating the memory for your	1047	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,	1048	watcher structures (and it is I<usually> a bad idea to do this on the
760	although this can sometimes be quite valid).	1049	stack).
761		1050
		1051	Each watcher has an associated watcher structure (called C<struct ev_TYPE>
		1052	or simply C<ev_TYPE>, as typedefs are provided for all watcher structs).
		1053
762	Each watcher structure must be initialised by a call to C<ev_init	1054	Each watcher structure must be initialised by a call to C<ev_init (watcher
763	(watcher *, callback)>, which expects a callback to be provided. This	1055	*, callback)>, which expects a callback to be provided. This callback is
764	callback gets invoked each time the event occurs (or, in the case of I/O	1056	invoked each time the event occurs (or, in the case of I/O watchers, each
765	watchers, each time the event loop detects that the file descriptor given	1057	time the event loop detects that the file descriptor given is readable
766	is readable and/or writable).	1058	and/or writable).
767		1059
768	Each watcher type has its own C<< ev_<type>_set (watcher *, ...) >> macro	1060	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	1061	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	1062	is also a macro to combine initialisation and setting in one call: C<<
771	(watcher *, callback, ...) >>.	1063	ev_TYPE_init (watcher *, callback, ...) >>.
772		1064
773	To make the watcher actually watch out for events, you have to start it	1065	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	1066	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	1067	*) >>), and you can stop watching for events at any time by calling the
776	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	1068	corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>.
777		1069
778	As long as your watcher is active (has been started but not stopped) you	1070	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	1071	must not touch the values stored in it. Most specifically you must never
780	reinitialise it or call its C<set> macro.	1072	reinitialise it or call its C<ev_TYPE_set> macro.
781		1073
782	Each and every callback receives the event loop pointer as first, the	1074	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	1075	registered watcher structure as second, and a bitset of received events as
784	third argument.	1076	third argument.
785		1077
…		…
794	=item C<EV_WRITE>	1086	=item C<EV_WRITE>
795		1087
796	The file descriptor in the C<ev_io> watcher has become readable and/or	1088	The file descriptor in the C<ev_io> watcher has become readable and/or
797	writable.	1089	writable.
798		1090
799	=item C<EV_TIMEOUT>	1091	=item C<EV_TIMER>
800		1092
801	The C<ev_timer> watcher has timed out.	1093	The C<ev_timer> watcher has timed out.
802		1094
803	=item C<EV_PERIODIC>	1095	=item C<EV_PERIODIC>
804		1096
…		…
822		1114
823	=item C<EV_PREPARE>	1115	=item C<EV_PREPARE>
824		1116
825	=item C<EV_CHECK>	1117	=item C<EV_CHECK>
826		1118
827	All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts	1119	All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts
828	to gather new events, and all C<ev_check> watchers are invoked just after	1120	to gather new events, and all C<ev_check> watchers are invoked just after
829	C<ev_loop> has gathered them, but before it invokes any callbacks for any	1121	C<ev_run> has gathered them, but before it invokes any callbacks for any
830	received events. Callbacks of both watcher types can start and stop as	1122	received events. Callbacks of both watcher types can start and stop as
831	many watchers as they want, and all of them will be taken into account	1123	many watchers as they want, and all of them will be taken into account
832	(for example, a C<ev_prepare> watcher might start an idle watcher to keep	1124	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
833	C<ev_loop> from blocking).	1125	C<ev_run> from blocking).
834		1126
835	=item C<EV_EMBED>	1127	=item C<EV_EMBED>
836		1128
837	The embedded event loop specified in the C<ev_embed> watcher needs attention.	1129	The embedded event loop specified in the C<ev_embed> watcher needs attention.
838		1130
839	=item C<EV_FORK>	1131	=item C<EV_FORK>
840		1132
841	The event loop has been resumed in the child process after fork (see	1133	The event loop has been resumed in the child process after fork (see
842	C<ev_fork>).	1134	C<ev_fork>).
843		1135
		1136	=item C<EV_CLEANUP>
		1137
		1138	The event loop is about to be destroyed (see C<ev_cleanup>).
		1139
844	=item C<EV_ASYNC>	1140	=item C<EV_ASYNC>
845		1141
846	The given async watcher has been asynchronously notified (see C<ev_async>).	1142	The given async watcher has been asynchronously notified (see C<ev_async>).
		1143
		1144	=item C<EV_CUSTOM>
		1145
		1146	Not ever sent (or otherwise used) by libev itself, but can be freely used
		1147	by libev users to signal watchers (e.g. via C<ev_feed_event>).
847		1148
848	=item C<EV_ERROR>	1149	=item C<EV_ERROR>
849		1150
850	An unspecified error has occurred, the watcher has been stopped. This might	1151	An unspecified error has occurred, the watcher has been stopped. This might
851	happen because the watcher could not be properly started because libev	1152	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	1153	ran out of memory, a file descriptor was found to be closed or any other
		1154	problem. Libev considers these application bugs.
		1155
853	problem. You best act on it by reporting the problem and somehow coping	1156	You best act on it by reporting the problem and somehow coping with the
854	with the watcher being stopped.	1157	watcher being stopped. Note that well-written programs should not receive
		1158	an error ever, so when your watcher receives it, this usually indicates a
		1159	bug in your program.
855		1160
856	Libev will usually signal a few "dummy" events together with an error,	1161	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	1162	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	1163	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	1164	the error from read() or write(). This will not work in multi-threaded
860	programs, though, so beware.	1165	programs, though, as the fd could already be closed and reused for another
		1166	thing, so beware.
861		1167
862	=back	1168	=back
863		1169
864	=head2 GENERIC WATCHER FUNCTIONS	1170	=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		1171
869	=over 4	1172	=over 4
870		1173
871	=item C<ev_init> (ev_TYPE *watcher, callback)	1174	=item C<ev_init> (ev_TYPE *watcher, callback)
872		1175
…		…
878	which rolls both calls into one.	1181	which rolls both calls into one.
879		1182
880	You can reinitialise a watcher at any time as long as it has been stopped	1183	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.	1184	(or never started) and there are no pending events outstanding.
882		1185
883	The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher,	1186	The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher,
884	int revents)>.	1187	int revents)>.
885		1188
		1189	Example: Initialise an C<ev_io> watcher in two steps.
		1190
		1191	ev_io w;
		1192	ev_init (&w, my_cb);
		1193	ev_io_set (&w, STDIN_FILENO, EV_READ);
		1194
886	=item C<ev_TYPE_set> (ev_TYPE *, [args])	1195	=item C<ev_TYPE_set> (ev_TYPE *watcher, [args])
887		1196
888	This macro initialises the type-specific parts of a watcher. You need to	1197	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	1198	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	1199	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	1200	macro on a watcher that is active (it can be pending, however, which is a
892	difference to the C<ev_init> macro).	1201	difference to the C<ev_init> macro).
893		1202
894	Although some watcher types do not have type-specific arguments	1203	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.	1204	(e.g. C<ev_prepare>) you still need to call its C<set> macro.
896		1205
		1206	See C<ev_init>, above, for an example.
		1207
897	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])	1208	=item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args])
898		1209
899	This convenience macro rolls both C<ev_init> and C<ev_TYPE_set> macro	1210	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	1211	calls into a single call. This is the most convenient method to initialise
901	a watcher. The same limitations apply, of course.	1212	a watcher. The same limitations apply, of course.
902		1213
		1214	Example: Initialise and set an C<ev_io> watcher in one step.
		1215
		1216	ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ);
		1217
903	=item C<ev_TYPE_start> (loop *, ev_TYPE *watcher)	1218	=item C<ev_TYPE_start> (loop, ev_TYPE *watcher)
904		1219
905	Starts (activates) the given watcher. Only active watchers will receive	1220	Starts (activates) the given watcher. Only active watchers will receive
906	events. If the watcher is already active nothing will happen.	1221	events. If the watcher is already active nothing will happen.
907		1222
		1223	Example: Start the C<ev_io> watcher that is being abused as example in this
		1224	whole section.
		1225
		1226	ev_io_start (EV_DEFAULT_UC, &w);
		1227
908	=item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher)	1228	=item C<ev_TYPE_stop> (loop, ev_TYPE *watcher)
909		1229
910	Stops the given watcher again (if active) and clears the pending	1230	Stops the given watcher if active, and clears the pending status (whether
		1231	the watcher was active or not).
		1232
911	status. It is possible that stopped watchers are pending (for example,	1233	It is possible that stopped watchers are pending - for example,
912	non-repeating timers are being stopped when they become pending), but	1234	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	1235	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	1236	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.	1237	therefore a good idea to always call its C<ev_TYPE_stop> function.
916		1238
917	=item bool ev_is_active (ev_TYPE *watcher)	1239	=item bool ev_is_active (ev_TYPE *watcher)
918		1240
919	Returns a true value iff the watcher is active (i.e. it has been started	1241	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	1242	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)	1258	=item ev_cb_set (ev_TYPE *watcher, callback)
937		1259
938	Change the callback. You can change the callback at virtually any time	1260	Change the callback. You can change the callback at virtually any time
939	(modulo threads).	1261	(modulo threads).
940		1262
941	=item ev_set_priority (ev_TYPE *watcher, priority)	1263	=item ev_set_priority (ev_TYPE *watcher, int priority)
942		1264
943	=item int ev_priority (ev_TYPE *watcher)	1265	=item int ev_priority (ev_TYPE *watcher)
944		1266
945	Set and query the priority of the watcher. The priority is a small	1267	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>	1268	integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI>
947	(default: C<-2>). Pending watchers with higher priority will be invoked	1269	(default: C<-2>). Pending watchers with higher priority will be invoked
948	before watchers with lower priority, but priority will not keep watchers	1270	before watchers with lower priority, but priority will not keep watchers
949	from being executed (except for C<ev_idle> watchers).	1271	from being executed (except for C<ev_idle> watchers).
950		1272
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	1273	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.	1274	you need to look at C<ev_idle> watchers, which provide this functionality.
958		1275
959	You I<must not> change the priority of a watcher as long as it is active or	1276	You I<must not> change the priority of a watcher as long as it is active or
960	pending.	1277	pending.
961		1278
		1279	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
		1280	fine, as long as you do not mind that the priority value you query might
		1281	or might not have been clamped to the valid range.
		1282
962	The default priority used by watchers when no priority has been set is	1283	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 :).	1284	always C<0>, which is supposed to not be too high and not be too low :).
964		1285
965	Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is	1286	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	1287	priorities.
967	or might not have been adjusted to be within valid range.
968		1288
969	=item ev_invoke (loop, ev_TYPE *watcher, int revents)	1289	=item ev_invoke (loop, ev_TYPE *watcher, int revents)
970		1290
971	Invoke the C<watcher> with the given C<loop> and C<revents>. Neither	1291	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	1292	C<loop> nor C<revents> need to be valid as long as the watcher callback
973	can deal with that fact.	1293	can deal with that fact, as both are simply passed through to the
		1294	callback.
974		1295
975	=item int ev_clear_pending (loop, ev_TYPE *watcher)	1296	=item int ev_clear_pending (loop, ev_TYPE *watcher)
976		1297
977	If the watcher is pending, this function returns clears its pending status	1298	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	1299	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>.	1300	watcher isn't pending it does nothing and returns C<0>.
980		1301
		1302	Sometimes it can be useful to "poll" a watcher instead of waiting for its
		1303	callback to be invoked, which can be accomplished with this function.
		1304
		1305	=item ev_feed_event (loop, ev_TYPE *watcher, int revents)
		1306
		1307	Feeds the given event set into the event loop, as if the specified event
		1308	had happened for the specified watcher (which must be a pointer to an
		1309	initialised but not necessarily started event watcher). Obviously you must
		1310	not free the watcher as long as it has pending events.
		1311
		1312	Stopping the watcher, letting libev invoke it, or calling
		1313	C<ev_clear_pending> will clear the pending event, even if the watcher was
		1314	not started in the first place.
		1315
		1316	See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related
		1317	functions that do not need a watcher.
		1318
981	=back	1319	=back
982		1320
983
984	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	1321	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
985		1322
986	Each watcher has, by default, a member C<void *data> that you can change	1323	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	1324	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	1325	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	1326	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	1327	member, you can also "subclass" the watcher type and provide your own
991	data:	1328	data:
992		1329
993	struct my_io	1330	struct my_io
994	{	1331	{
995	struct ev_io io;	1332	ev_io io;
996	int otherfd;	1333	int otherfd;
997	void *somedata;	1334	void *somedata;
998	struct whatever *mostinteresting;	1335	struct whatever *mostinteresting;
999	}	1336	};
		1337
		1338	...
		1339	struct my_io w;
		1340	ev_io_init (&w.io, my_cb, fd, EV_READ);
1000		1341
1001	And since your callback will be called with a pointer to the watcher, you	1342	And since your callback will be called with a pointer to the watcher, you
1002	can cast it back to your own type:	1343	can cast it back to your own type:
1003		1344
1004	static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents)	1345	static void my_cb (struct ev_loop *loop, ev_io *w_, int revents)
1005	{	1346	{
1006	struct my_io *w = (struct my_io *)w_;	1347	struct my_io *w = (struct my_io *)w_;
1007	...	1348	...
1008	}	1349	}
1009		1350
1010	More interesting and less C-conformant ways of casting your callback type	1351	More interesting and less C-conformant ways of casting your callback type
1011	instead have been omitted.	1352	instead have been omitted.
1012		1353
1013	Another common scenario is having some data structure with multiple	1354	Another common scenario is to use some data structure with multiple
1014	watchers:	1355	embedded watchers:
1015		1356
1016	struct my_biggy	1357	struct my_biggy
1017	{	1358	{
1018	int some_data;	1359	int some_data;
1019	ev_timer t1;	1360	ev_timer t1;
1020	ev_timer t2;	1361	ev_timer t2;
1021	}	1362	}
1022		1363
1023	In this case getting the pointer to C<my_biggy> is a bit more complicated,	1364	In this case getting the pointer to C<my_biggy> is a bit more
1024	you need to use C<offsetof>:	1365	complicated: Either you store the address of your C<my_biggy> struct
		1366	in the C<data> member of the watcher (for woozies), or you need to use
		1367	some pointer arithmetic using C<offsetof> inside your watchers (for real
		1368	programmers):
1025		1369
1026	#include <stddef.h>	1370	#include <stddef.h>
1027		1371
1028	static void	1372	static void
1029	t1_cb (EV_P_ struct ev_timer *w, int revents)	1373	t1_cb (EV_P_ ev_timer *w, int revents)
1030	{	1374	{
1031	struct my_biggy big = (struct my_biggy *	1375	struct my_biggy big = (struct my_biggy *)
1032	(((char *)w) - offsetof (struct my_biggy, t1));	1376	(((char *)w) - offsetof (struct my_biggy, t1));
1033	}	1377	}
1034		1378
1035	static void	1379	static void
1036	t2_cb (EV_P_ struct ev_timer *w, int revents)	1380	t2_cb (EV_P_ ev_timer *w, int revents)
1037	{	1381	{
1038	struct my_biggy big = (struct my_biggy *	1382	struct my_biggy big = (struct my_biggy *)
1039	(((char *)w) - offsetof (struct my_biggy, t2));	1383	(((char *)w) - offsetof (struct my_biggy, t2));
1040	}	1384	}
		1385
		1386	=head2 WATCHER STATES
		1387
		1388	There are various watcher states mentioned throughout this manual -
		1389	active, pending and so on. In this section these states and the rules to
		1390	transition between them will be described in more detail - and while these
		1391	rules might look complicated, they usually do "the right thing".
		1392
		1393	=over 4
		1394
		1395	=item initialiased
		1396
		1397	Before a watcher can be registered with the event looop it has to be
		1398	initialised. This can be done with a call to C<ev_TYPE_init>, or calls to
		1399	C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function.
		1400
		1401	In this state it is simply some block of memory that is suitable for use
		1402	in an event loop. It can be moved around, freed, reused etc. at will.
		1403
		1404	=item started/running/active
		1405
		1406	Once a watcher has been started with a call to C<ev_TYPE_start> it becomes
		1407	property of the event loop, and is actively waiting for events. While in
		1408	this state it cannot be accessed (except in a few documented ways), moved,
		1409	freed or anything else - the only legal thing is to keep a pointer to it,
		1410	and call libev functions on it that are documented to work on active watchers.
		1411
		1412	=item pending
		1413
		1414	If a watcher is active and libev determines that an event it is interested
		1415	in has occurred (such as a timer expiring), it will become pending. It will
		1416	stay in this pending state until either it is stopped or its callback is
		1417	about to be invoked, so it is not normally pending inside the watcher
		1418	callback.
		1419
		1420	The watcher might or might not be active while it is pending (for example,
		1421	an expired non-repeating timer can be pending but no longer active). If it
		1422	is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
		1423	but it is still property of the event loop at this time, so cannot be
		1424	moved, freed or reused. And if it is active the rules described in the
		1425	previous item still apply.
		1426
		1427	It is also possible to feed an event on a watcher that is not active (e.g.
		1428	via C<ev_feed_event>), in which case it becomes pending without being
		1429	active.
		1430
		1431	=item stopped
		1432
		1433	A watcher can be stopped implicitly by libev (in which case it might still
		1434	be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
		1435	latter will clear any pending state the watcher might be in, regardless
		1436	of whether it was active or not, so stopping a watcher explicitly before
		1437	freeing it is often a good idea.
		1438
		1439	While stopped (and not pending) the watcher is essentially in the
		1440	initialised state, that is it can be reused, moved, modified in any way
		1441	you wish.
		1442
		1443	=back
		1444
		1445	=head2 WATCHER PRIORITY MODELS
		1446
		1447	Many event loops support I<watcher priorities>, which are usually small
		1448	integers that influence the ordering of event callback invocation
		1449	between watchers in some way, all else being equal.
		1450
		1451	In libev, Watcher priorities can be set using C<ev_set_priority>. See its
		1452	description for the more technical details such as the actual priority
		1453	range.
		1454
		1455	There are two common ways how these these priorities are being interpreted
		1456	by event loops:
		1457
		1458	In the more common lock-out model, higher priorities "lock out" invocation
		1459	of lower priority watchers, which means as long as higher priority
		1460	watchers receive events, lower priority watchers are not being invoked.
		1461
		1462	The less common only-for-ordering model uses priorities solely to order
		1463	callback invocation within a single event loop iteration: Higher priority
		1464	watchers are invoked before lower priority ones, but they all get invoked
		1465	before polling for new events.
		1466
		1467	Libev uses the second (only-for-ordering) model for all its watchers
		1468	except for idle watchers (which use the lock-out model).
		1469
		1470	The rationale behind this is that implementing the lock-out model for
		1471	watchers is not well supported by most kernel interfaces, and most event
		1472	libraries will just poll for the same events again and again as long as
		1473	their callbacks have not been executed, which is very inefficient in the
		1474	common case of one high-priority watcher locking out a mass of lower
		1475	priority ones.
		1476
		1477	Static (ordering) priorities are most useful when you have two or more
		1478	watchers handling the same resource: a typical usage example is having an
		1479	C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle
		1480	timeouts. Under load, data might be received while the program handles
		1481	other jobs, but since timers normally get invoked first, the timeout
		1482	handler will be executed before checking for data. In that case, giving
		1483	the timer a lower priority than the I/O watcher ensures that I/O will be
		1484	handled first even under adverse conditions (which is usually, but not
		1485	always, what you want).
		1486
		1487	Since idle watchers use the "lock-out" model, meaning that idle watchers
		1488	will only be executed when no same or higher priority watchers have
		1489	received events, they can be used to implement the "lock-out" model when
		1490	required.
		1491
		1492	For example, to emulate how many other event libraries handle priorities,
		1493	you can associate an C<ev_idle> watcher to each such watcher, and in
		1494	the normal watcher callback, you just start the idle watcher. The real
		1495	processing is done in the idle watcher callback. This causes libev to
		1496	continuously poll and process kernel event data for the watcher, but when
		1497	the lock-out case is known to be rare (which in turn is rare :), this is
		1498	workable.
		1499
		1500	Usually, however, the lock-out model implemented that way will perform
		1501	miserably under the type of load it was designed to handle. In that case,
		1502	it might be preferable to stop the real watcher before starting the
		1503	idle watcher, so the kernel will not have to process the event in case
		1504	the actual processing will be delayed for considerable time.
		1505
		1506	Here is an example of an I/O watcher that should run at a strictly lower
		1507	priority than the default, and which should only process data when no
		1508	other events are pending:
		1509
		1510	ev_idle idle; // actual processing watcher
		1511	ev_io io; // actual event watcher
		1512
		1513	static void
		1514	io_cb (EV_P_ ev_io *w, int revents)
		1515	{
		1516	// stop the I/O watcher, we received the event, but
		1517	// are not yet ready to handle it.
		1518	ev_io_stop (EV_A_ w);
		1519
		1520	// start the idle watcher to handle the actual event.
		1521	// it will not be executed as long as other watchers
		1522	// with the default priority are receiving events.
		1523	ev_idle_start (EV_A_ &idle);
		1524	}
		1525
		1526	static void
		1527	idle_cb (EV_P_ ev_idle *w, int revents)
		1528	{
		1529	// actual processing
		1530	read (STDIN_FILENO, ...);
		1531
		1532	// have to start the I/O watcher again, as
		1533	// we have handled the event
		1534	ev_io_start (EV_P_ &io);
		1535	}
		1536
		1537	// initialisation
		1538	ev_idle_init (&idle, idle_cb);
		1539	ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ);
		1540	ev_io_start (EV_DEFAULT_ &io);
		1541
		1542	In the "real" world, it might also be beneficial to start a timer, so that
		1543	low-priority connections can not be locked out forever under load. This
		1544	enables your program to keep a lower latency for important connections
		1545	during short periods of high load, while not completely locking out less
		1546	important ones.
1041		1547
1042		1548
1043	=head1 WATCHER TYPES	1549	=head1 WATCHER TYPES
1044		1550
1045	This section describes each watcher in detail, but will not repeat	1551	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	1575	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	1576	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	1577	descriptors to non-blocking mode is also usually a good idea (but not
1072	required if you know what you are doing).	1578	required if you know what you are doing).
1073		1579
1074	If you must do this, then force the use of a known-to-be-good backend	1580	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	1581	known-to-be-good backend (at the time of this writing, this includes only
1076	C<EVBACKEND_POLL>).	1582	C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file
		1583	descriptors for which non-blocking operation makes no sense (such as
		1584	files) - libev doesn't guarantee any specific behaviour in that case.
1077		1585
1078	Another thing you have to watch out for is that it is quite easy to	1586	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	1587	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	1588	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	1589	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	1590	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	1591	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	1592	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.	1593	C<EAGAIN> is far preferable to a program hanging until some data arrives.
1086		1594
1087	If you cannot run the fd in non-blocking mode (for example you should not	1595	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	1596	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	1597	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	1598	interface such as poll (fortunately in our Xlib example, Xlib already
1091	its own, so its quite safe to use).	1599	does this on its own, so its quite safe to use). Some people additionally
		1600	use C<SIGALRM> and an interval timer, just to be sure you won't block
		1601	indefinitely.
		1602
		1603	But really, best use non-blocking mode.
1092		1604
1093	=head3 The special problem of disappearing file descriptors	1605	=head3 The special problem of disappearing file descriptors
1094		1606
1095	Some backends (e.g. kqueue, epoll) need to be told about closing a file	1607	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,	1608	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	1609	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	1610	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	1611	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	1612	registered with libev, there is no efficient way to see that this is, in
1101	fact, a different file descriptor.	1613	fact, a different file descriptor.
1102		1614
…		…
1133	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1645	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or
1134	C<EVBACKEND_POLL>.	1646	C<EVBACKEND_POLL>.
1135		1647
1136	=head3 The special problem of SIGPIPE	1648	=head3 The special problem of SIGPIPE
1137		1649
1138	While not really specific to libev, it is easy to forget about SIGPIPE:	1650	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	1651	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	1652	sent a SIGPIPE, which, by default, aborts your program. For most programs
1141	programs this is sensible behaviour, for daemons, this is usually	1653	this is sensible behaviour, for daemons, this is usually undesirable.
1142	undesirable.
1143		1654
1144	So when you encounter spurious, unexplained daemon exits, make sure you	1655	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	1656	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).	1657	somewhere, as that would have given you a big clue).
1147		1658
		1659	=head3 The special problem of accept()ing when you can't
		1660
		1661	Many implementations of the POSIX C<accept> function (for example,
		1662	found in post-2004 Linux) have the peculiar behaviour of not removing a
		1663	connection from the pending queue in all error cases.
		1664
		1665	For example, larger servers often run out of file descriptors (because
		1666	of resource limits), causing C<accept> to fail with C<ENFILE> but not
		1667	rejecting the connection, leading to libev signalling readiness on
		1668	the next iteration again (the connection still exists after all), and
		1669	typically causing the program to loop at 100% CPU usage.
		1670
		1671	Unfortunately, the set of errors that cause this issue differs between
		1672	operating systems, there is usually little the app can do to remedy the
		1673	situation, and no known thread-safe method of removing the connection to
		1674	cope with overload is known (to me).
		1675
		1676	One of the easiest ways to handle this situation is to just ignore it
		1677	- when the program encounters an overload, it will just loop until the
		1678	situation is over. While this is a form of busy waiting, no OS offers an
		1679	event-based way to handle this situation, so it's the best one can do.
		1680
		1681	A better way to handle the situation is to log any errors other than
		1682	C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
		1683	messages, and continue as usual, which at least gives the user an idea of
		1684	what could be wrong ("raise the ulimit!"). For extra points one could stop
		1685	the C<ev_io> watcher on the listening fd "for a while", which reduces CPU
		1686	usage.
		1687
		1688	If your program is single-threaded, then you could also keep a dummy file
		1689	descriptor for overload situations (e.g. by opening F</dev/null>), and
		1690	when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>,
		1691	close that fd, and create a new dummy fd. This will gracefully refuse
		1692	clients under typical overload conditions.
		1693
		1694	The last way to handle it is to simply log the error and C<exit>, as
		1695	is often done with C<malloc> failures, but this results in an easy
		1696	opportunity for a DoS attack.
1148		1697
1149	=head3 Watcher-Specific Functions	1698	=head3 Watcher-Specific Functions
1150		1699
1151	=over 4	1700	=over 4
1152		1701
1153	=item ev_io_init (ev_io *, callback, int fd, int events)	1702	=item ev_io_init (ev_io *, callback, int fd, int events)
1154		1703
1155	=item ev_io_set (ev_io *, int fd, int events)	1704	=item ev_io_set (ev_io *, int fd, int events)
1156		1705
1157	Configures an C<ev_io> watcher. The C<fd> is the file descriptor to	1706	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	1707	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.	1708	C<EV_READ | EV_WRITE>, to express the desire to receive the given events.
1160		1709
1161	=item int fd [read-only]	1710	=item int fd [read-only]
1162		1711
1163	The file descriptor being watched.	1712	The file descriptor being watched.
1164		1713
…		…
1173	Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well	1722	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	1723	readable, but only once. Since it is likely line-buffered, you could
1175	attempt to read a whole line in the callback.	1724	attempt to read a whole line in the callback.
1176		1725
1177	static void	1726	static void
1178	stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)	1727	stdin_readable_cb (struct ev_loop *loop, ev_io *w, int revents)
1179	{	1728	{
1180	ev_io_stop (loop, w);	1729	ev_io_stop (loop, w);
1181	.. read from stdin here (or from w->fd) and haqndle any I/O errors	1730	.. read from stdin here (or from w->fd) and handle any I/O errors
1182	}	1731	}
1183		1732
1184	...	1733	...
1185	struct ev_loop *loop = ev_default_init (0);	1734	struct ev_loop *loop = ev_default_init (0);
1186	struct ev_io stdin_readable;	1735	ev_io stdin_readable;
1187	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);	1736	ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1188	ev_io_start (loop, &stdin_readable);	1737	ev_io_start (loop, &stdin_readable);
1189	ev_loop (loop, 0);	1738	ev_run (loop, 0);
1190		1739
1191		1740
1192	=head2 C<ev_timer> - relative and optionally repeating timeouts	1741	=head2 C<ev_timer> - relative and optionally repeating timeouts
1193		1742
1194	Timer watchers are simple relative timers that generate an event after a	1743	Timer watchers are simple relative timers that generate an event after a
1195	given time, and optionally repeating in regular intervals after that.	1744	given time, and optionally repeating in regular intervals after that.
1196		1745
1197	The timers are based on real time, that is, if you register an event that	1746	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	1747	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	1748	year, it will still time out after (roughly) one hour. "Roughly" because
1200	detecting time jumps is hard, and some inaccuracies are unavoidable (the	1749	detecting time jumps is hard, and some inaccuracies are unavoidable (the
1201	monotonic clock option helps a lot here).	1750	monotonic clock option helps a lot here).
		1751
		1752	The callback is guaranteed to be invoked only I<after> its timeout has
		1753	passed (not I<at>, so on systems with very low-resolution clocks this
		1754	might introduce a small delay). If multiple timers become ready during the
		1755	same loop iteration then the ones with earlier time-out values are invoked
		1756	before ones of the same priority with later time-out values (but this is
		1757	no longer true when a callback calls C<ev_run> recursively).
		1758
		1759	=head3 Be smart about timeouts
		1760
		1761	Many real-world problems involve some kind of timeout, usually for error
		1762	recovery. A typical example is an HTTP request - if the other side hangs,
		1763	you want to raise some error after a while.
		1764
		1765	What follows are some ways to handle this problem, from obvious and
		1766	inefficient to smart and efficient.
		1767
		1768	In the following, a 60 second activity timeout is assumed - a timeout that
		1769	gets reset to 60 seconds each time there is activity (e.g. each time some
		1770	data or other life sign was received).
		1771
		1772	=over 4
		1773
		1774	=item 1. Use a timer and stop, reinitialise and start it on activity.
		1775
		1776	This is the most obvious, but not the most simple way: In the beginning,
		1777	start the watcher:
		1778
		1779	ev_timer_init (timer, callback, 60., 0.);
		1780	ev_timer_start (loop, timer);
		1781
		1782	Then, each time there is some activity, C<ev_timer_stop> it, initialise it
		1783	and start it again:
		1784
		1785	ev_timer_stop (loop, timer);
		1786	ev_timer_set (timer, 60., 0.);
		1787	ev_timer_start (loop, timer);
		1788
		1789	This is relatively simple to implement, but means that each time there is
		1790	some activity, libev will first have to remove the timer from its internal
		1791	data structure and then add it again. Libev tries to be fast, but it's
		1792	still not a constant-time operation.
		1793
		1794	=item 2. Use a timer and re-start it with C<ev_timer_again> inactivity.
		1795
		1796	This is the easiest way, and involves using C<ev_timer_again> instead of
		1797	C<ev_timer_start>.
		1798
		1799	To implement this, configure an C<ev_timer> with a C<repeat> value
		1800	of C<60> and then call C<ev_timer_again> at start and each time you
		1801	successfully read or write some data. If you go into an idle state where
		1802	you do not expect data to travel on the socket, you can C<ev_timer_stop>
		1803	the timer, and C<ev_timer_again> will automatically restart it if need be.
		1804
		1805	That means you can ignore both the C<ev_timer_start> function and the
		1806	C<after> argument to C<ev_timer_set>, and only ever use the C<repeat>
		1807	member and C<ev_timer_again>.
		1808
		1809	At start:
		1810
		1811	ev_init (timer, callback);
		1812	timer->repeat = 60.;
		1813	ev_timer_again (loop, timer);
		1814
		1815	Each time there is some activity:
		1816
		1817	ev_timer_again (loop, timer);
		1818
		1819	It is even possible to change the time-out on the fly, regardless of
		1820	whether the watcher is active or not:
		1821
		1822	timer->repeat = 30.;
		1823	ev_timer_again (loop, timer);
		1824
		1825	This is slightly more efficient then stopping/starting the timer each time
		1826	you want to modify its timeout value, as libev does not have to completely
		1827	remove and re-insert the timer from/into its internal data structure.
		1828
		1829	It is, however, even simpler than the "obvious" way to do it.
		1830
		1831	=item 3. Let the timer time out, but then re-arm it as required.
		1832
		1833	This method is more tricky, but usually most efficient: Most timeouts are
		1834	relatively long compared to the intervals between other activity - in
		1835	our example, within 60 seconds, there are usually many I/O events with
		1836	associated activity resets.
		1837
		1838	In this case, it would be more efficient to leave the C<ev_timer> alone,
		1839	but remember the time of last activity, and check for a real timeout only
		1840	within the callback:
		1841
		1842	ev_tstamp last_activity; // time of last activity
		1843
		1844	static void
		1845	callback (EV_P_ ev_timer *w, int revents)
		1846	{
		1847	ev_tstamp now = ev_now (EV_A);
		1848	ev_tstamp timeout = last_activity + 60.;
		1849
		1850	// if last_activity + 60. is older than now, we did time out
		1851	if (timeout < now)
		1852	{
		1853	// timeout occurred, take action
		1854	}
		1855	else
		1856	{
		1857	// callback was invoked, but there was some activity, re-arm
		1858	// the watcher to fire in last_activity + 60, which is
		1859	// guaranteed to be in the future, so "again" is positive:
		1860	w->repeat = timeout - now;
		1861	ev_timer_again (EV_A_ w);
		1862	}
		1863	}
		1864
		1865	To summarise the callback: first calculate the real timeout (defined
		1866	as "60 seconds after the last activity"), then check if that time has
		1867	been reached, which means something I<did>, in fact, time out. Otherwise
		1868	the callback was invoked too early (C<timeout> is in the future), so
		1869	re-schedule the timer to fire at that future time, to see if maybe we have
		1870	a timeout then.
		1871
		1872	Note how C<ev_timer_again> is used, taking advantage of the
		1873	C<ev_timer_again> optimisation when the timer is already running.
		1874
		1875	This scheme causes more callback invocations (about one every 60 seconds
		1876	minus half the average time between activity), but virtually no calls to
		1877	libev to change the timeout.
		1878
		1879	To start the timer, simply initialise the watcher and set C<last_activity>
		1880	to the current time (meaning we just have some activity :), then call the
		1881	callback, which will "do the right thing" and start the timer:
		1882
		1883	ev_init (timer, callback);
		1884	last_activity = ev_now (loop);
		1885	callback (loop, timer, EV_TIMER);
		1886
		1887	And when there is some activity, simply store the current time in
		1888	C<last_activity>, no libev calls at all:
		1889
		1890	last_activity = ev_now (loop);
		1891
		1892	This technique is slightly more complex, but in most cases where the
		1893	time-out is unlikely to be triggered, much more efficient.
		1894
		1895	Changing the timeout is trivial as well (if it isn't hard-coded in the
		1896	callback :) - just change the timeout and invoke the callback, which will
		1897	fix things for you.
		1898
		1899	=item 4. Wee, just use a double-linked list for your timeouts.
		1900
		1901	If there is not one request, but many thousands (millions...), all
		1902	employing some kind of timeout with the same timeout value, then one can
		1903	do even better:
		1904
		1905	When starting the timeout, calculate the timeout value and put the timeout
		1906	at the I<end> of the list.
		1907
		1908	Then use an C<ev_timer> to fire when the timeout at the I<beginning> of
		1909	the list is expected to fire (for example, using the technique #3).
		1910
		1911	When there is some activity, remove the timer from the list, recalculate
		1912	the timeout, append it to the end of the list again, and make sure to
		1913	update the C<ev_timer> if it was taken from the beginning of the list.
		1914
		1915	This way, one can manage an unlimited number of timeouts in O(1) time for
		1916	starting, stopping and updating the timers, at the expense of a major
		1917	complication, and having to use a constant timeout. The constant timeout
		1918	ensures that the list stays sorted.
		1919
		1920	=back
		1921
		1922	So which method the best?
		1923
		1924	Method #2 is a simple no-brain-required solution that is adequate in most
		1925	situations. Method #3 requires a bit more thinking, but handles many cases
		1926	better, and isn't very complicated either. In most case, choosing either
		1927	one is fine, with #3 being better in typical situations.
		1928
		1929	Method #1 is almost always a bad idea, and buys you nothing. Method #4 is
		1930	rather complicated, but extremely efficient, something that really pays
		1931	off after the first million or so of active timers, i.e. it's usually
		1932	overkill :)
		1933
		1934	=head3 The special problem of time updates
		1935
		1936	Establishing the current time is a costly operation (it usually takes at
		1937	least two system calls): EV therefore updates its idea of the current
		1938	time only before and after C<ev_run> collects new events, which causes a
		1939	growing difference between C<ev_now ()> and C<ev_time ()> when handling
		1940	lots of events in one iteration.
1202		1941
1203	The relative timeouts are calculated relative to the C<ev_now ()>	1942	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	1943	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	1944	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	1945	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:	1946	timeout on the current time, use something like this to adjust for this:
1208		1947
1209	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	1948	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
1210		1949
1211	The callback is guaranteed to be invoked only after its timeout has passed,	1950	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	1951	update of the time returned by C<ev_now ()> by calling C<ev_now_update
1213	order of execution is undefined.	1952	()>.
		1953
		1954	=head3 The special problems of suspended animation
		1955
		1956	When you leave the server world it is quite customary to hit machines that
		1957	can suspend/hibernate - what happens to the clocks during such a suspend?
		1958
		1959	Some quick tests made with a Linux 2.6.28 indicate that a suspend freezes
		1960	all processes, while the clocks (C<times>, C<CLOCK_MONOTONIC>) continue
		1961	to run until the system is suspended, but they will not advance while the
		1962	system is suspended. That means, on resume, it will be as if the program
		1963	was frozen for a few seconds, but the suspend time will not be counted
		1964	towards C<ev_timer> when a monotonic clock source is used. The real time
		1965	clock advanced as expected, but if it is used as sole clocksource, then a
		1966	long suspend would be detected as a time jump by libev, and timers would
		1967	be adjusted accordingly.
		1968
		1969	I would not be surprised to see different behaviour in different between
		1970	operating systems, OS versions or even different hardware.
		1971
		1972	The other form of suspend (job control, or sending a SIGSTOP) will see a
		1973	time jump in the monotonic clocks and the realtime clock. If the program
		1974	is suspended for a very long time, and monotonic clock sources are in use,
		1975	then you can expect C<ev_timer>s to expire as the full suspension time
		1976	will be counted towards the timers. When no monotonic clock source is in
		1977	use, then libev will again assume a timejump and adjust accordingly.
		1978
		1979	It might be beneficial for this latter case to call C<ev_suspend>
		1980	and C<ev_resume> in code that handles C<SIGTSTP>, to at least get
		1981	deterministic behaviour in this case (you can do nothing against
		1982	C<SIGSTOP>).
1214		1983
1215	=head3 Watcher-Specific Functions and Data Members	1984	=head3 Watcher-Specific Functions and Data Members
1216		1985
1217	=over 4	1986	=over 4
1218		1987
…		…
1242	If the timer is started but non-repeating, stop it (as if it timed out).	2011	If the timer is started but non-repeating, stop it (as if it timed out).
1243		2012
1244	If the timer is repeating, either start it if necessary (with the	2013	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.	2014	C<repeat> value), or reset the running timer to the C<repeat> value.
1246		2015
1247	This sounds a bit complicated, but here is a useful and typical	2016	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	2017	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		2018
1257	That means you can ignore the C<after> value and C<ev_timer_start>	2019	=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		2020
1260	ev_timer_init (timer, callback, 0., 5.);	2021	Returns the remaining time until a timer fires. If the timer is active,
1261	ev_timer_again (loop, timer);	2022	then this time is relative to the current event loop time, otherwise it's
1262	...	2023	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		2024
1269	This is more slightly efficient then stopping/starting the timer each time	2025	That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns
1270	you want to modify its timeout value.	2026	C<5>. When the timer is started and one second passes, C<ev_timer_remaining>
		2027	will return C<4>. When the timer expires and is restarted, it will return
		2028	roughly C<7> (likely slightly less as callback invocation takes some time,
		2029	too), and so on.
1271		2030
1272	=item ev_tstamp repeat [read-write]	2031	=item ev_tstamp repeat [read-write]
1273		2032
1274	The current C<repeat> value. Will be used each time the watcher times out	2033	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),	2034	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.	2035	which is also when any modifications are taken into account.
1277		2036
1278	=back	2037	=back
1279		2038
1280	=head3 Examples	2039	=head3 Examples
1281		2040
1282	Example: Create a timer that fires after 60 seconds.	2041	Example: Create a timer that fires after 60 seconds.
1283		2042
1284	static void	2043	static void
1285	one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	2044	one_minute_cb (struct ev_loop *loop, ev_timer *w, int revents)
1286	{	2045	{
1287	.. one minute over, w is actually stopped right here	2046	.. one minute over, w is actually stopped right here
1288	}	2047	}
1289		2048
1290	struct ev_timer mytimer;	2049	ev_timer mytimer;
1291	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);	2050	ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1292	ev_timer_start (loop, &mytimer);	2051	ev_timer_start (loop, &mytimer);
1293		2052
1294	Example: Create a timeout timer that times out after 10 seconds of	2053	Example: Create a timeout timer that times out after 10 seconds of
1295	inactivity.	2054	inactivity.
1296		2055
1297	static void	2056	static void
1298	timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)	2057	timeout_cb (struct ev_loop *loop, ev_timer *w, int revents)
1299	{	2058	{
1300	.. ten seconds without any activity	2059	.. ten seconds without any activity
1301	}	2060	}
1302		2061
1303	struct ev_timer mytimer;	2062	ev_timer mytimer;
1304	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */	2063	ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1305	ev_timer_again (&mytimer); /* start timer */	2064	ev_timer_again (&mytimer); /* start timer */
1306	ev_loop (loop, 0);	2065	ev_run (loop, 0);
1307		2066
1308	// and in some piece of code that gets executed on any "activity":	2067	// and in some piece of code that gets executed on any "activity":
1309	// reset the timeout to start ticking again at 10 seconds	2068	// reset the timeout to start ticking again at 10 seconds
1310	ev_timer_again (&mytimer);	2069	ev_timer_again (&mytimer);
1311		2070
…		…
1313	=head2 C<ev_periodic> - to cron or not to cron?	2072	=head2 C<ev_periodic> - to cron or not to cron?
1314		2073
1315	Periodic watchers are also timers of a kind, but they are very versatile	2074	Periodic watchers are also timers of a kind, but they are very versatile
1316	(and unfortunately a bit complex).	2075	(and unfortunately a bit complex).
1317		2076
1318	Unlike C<ev_timer>'s, they are not based on real time (or relative time)	2077	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	2078	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	2079	(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 ()	2080	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	2081	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	2082	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		2083
		2084	You can tell a periodic watcher to trigger after some specific point
		2085	in time: for example, if you tell a periodic watcher to trigger "in 10
		2086	seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time
		2087	not a delay) and then reset your system clock to January of the previous
		2088	year, then it will take a year or more to trigger the event (unlike an
		2089	C<ev_timer>, which would still trigger roughly 10 seconds after starting
		2090	it, as it uses a relative timeout).
		2091
1327	C<ev_periodic>s can also be used to implement vastly more complex timers,	2092	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	2093	timers, such as triggering an event on each "midnight, local time", or
1329	complicated, rules.	2094	other complicated rules. This cannot be done with C<ev_timer> watchers, as
		2095	those cannot react to time jumps.
1330		2096
1331	As with timers, the callback is guaranteed to be invoked only when the	2097	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	2098	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.	2099	timers become ready during the same loop iteration then the ones with
		2100	earlier time-out values are invoked before ones with later time-out values
		2101	(but this is no longer true when a callback calls C<ev_run> recursively).
1334		2102
1335	=head3 Watcher-Specific Functions and Data Members	2103	=head3 Watcher-Specific Functions and Data Members
1336		2104
1337	=over 4	2105	=over 4
1338		2106
1339	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	2107	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1340		2108
1341	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	2109	=item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb)
1342		2110
1343	Lots of arguments, lets sort it out... There are basically three modes of	2111	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:	2112	operation, and we will explain them from simplest to most complex:
1345		2113
1346	=over 4	2114	=over 4
1347		2115
1348	=item * absolute timer (at = time, interval = reschedule_cb = 0)	2116	=item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0)
1349		2117
1350	In this configuration the watcher triggers an event after the wall clock	2118	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	2119	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	2120	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.	2121	will be stopped and invoked when the system clock reaches or surpasses
		2122	this point in time.
1354		2123
1355	=item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)	2124	=item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0)
1356		2125
1357	In this mode the watcher will always be scheduled to time out at the next	2126	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)	2127	C<offset + N * interval> time (for some integer N, which can also be
1359	and then repeat, regardless of any time jumps.	2128	negative) and then repeat, regardless of any time jumps. The C<offset>
		2129	argument is merely an offset into the C<interval> periods.
1360		2130
1361	This can be used to create timers that do not drift with respect to system	2131	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	2132	system clock, for example, here is an C<ev_periodic> that triggers each
1363	the hour:	2133	hour, on the hour (with respect to UTC):
1364		2134
1365	ev_periodic_set (&periodic, 0., 3600., 0);	2135	ev_periodic_set (&periodic, 0., 3600., 0);
1366		2136
1367	This doesn't mean there will always be 3600 seconds in between triggers,	2137	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	2138	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	2139	full hour (UTC), or more correctly, when the system time is evenly divisible
1370	by 3600.	2140	by 3600.
1371		2141
1372	Another way to think about it (for the mathematically inclined) is that	2142	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	2143	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.	2144	time where C<time = offset (mod interval)>, regardless of any time jumps.
1375		2145
1376	For numerical stability it is preferable that the C<at> value is near	2146	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	2147	C<ev_now ()> (the current time), but there is no range requirement for
1378	this value, and in fact is often specified as zero.	2148	this value, and in fact is often specified as zero.
1379		2149
1380	Note also that there is an upper limit to how often a timer can fire (CPU	2150	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	2151	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	2152	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).	2153	millisecond (if the OS supports it and the machine is fast enough).
1384		2154
1385	=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)	2155	=item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback)
1386		2156
1387	In this mode the values for C<interval> and C<at> are both being	2157	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	2158	ignored. Instead, each time the periodic watcher gets scheduled, the
1389	reschedule callback will be called with the watcher as first, and the	2159	reschedule callback will be called with the watcher as first, and the
1390	current time as second argument.	2160	current time as second argument.
1391		2161
1392	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,	2162	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever,
1393	ever, or make ANY event loop modifications whatsoever>.	2163	or make ANY other event loop modifications whatsoever, unless explicitly
		2164	allowed by documentation here>.
1394		2165
1395	If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop	2166	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	2167	it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
1397	only event loop modification you are allowed to do).	2168	only event loop modification you are allowed to do).
1398		2169
1399	The callback prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic	2170	The callback prototype is C<ev_tstamp (*reschedule_cb)(ev_periodic
1400	*w, ev_tstamp now)>, e.g.:	2171	*w, ev_tstamp now)>, e.g.:
1401		2172
		2173	static ev_tstamp
1402	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	2174	my_rescheduler (ev_periodic *w, ev_tstamp now)
1403	{	2175	{
1404	return now + 60.;	2176	return now + 60.;
1405	}	2177	}
1406		2178
1407	It must return the next time to trigger, based on the passed time value	2179	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	2199	a different time than the last time it was called (e.g. in a crond like
1428	program when the crontabs have changed).	2200	program when the crontabs have changed).
1429		2201
1430	=item ev_tstamp ev_periodic_at (ev_periodic *)	2202	=item ev_tstamp ev_periodic_at (ev_periodic *)
1431		2203
1432	When active, returns the absolute time that the watcher is supposed to	2204	When active, returns the absolute time that the watcher is supposed
1433	trigger next.	2205	to trigger next. This is not the same as the C<offset> argument to
		2206	C<ev_periodic_set>, but indeed works even in interval and manual
		2207	rescheduling modes.
1434		2208
1435	=item ev_tstamp offset [read-write]	2209	=item ev_tstamp offset [read-write]
1436		2210
1437	When repeating, this contains the offset value, otherwise this is the	2211	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>).	2212	absolute point in time (the C<offset> value passed to C<ev_periodic_set>,
		2213	although libev might modify this value for better numerical stability).
1439		2214
1440	Can be modified any time, but changes only take effect when the periodic	2215	Can be modified any time, but changes only take effect when the periodic
1441	timer fires or C<ev_periodic_again> is being called.	2216	timer fires or C<ev_periodic_again> is being called.
1442		2217
1443	=item ev_tstamp interval [read-write]	2218	=item ev_tstamp interval [read-write]
1444		2219
1445	The current interval value. Can be modified any time, but changes only	2220	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	2221	take effect when the periodic timer fires or C<ev_periodic_again> is being
1447	called.	2222	called.
1448		2223
1449	=item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]	2224	=item ev_tstamp (*reschedule_cb)(ev_periodic *w, ev_tstamp now) [read-write]
1450		2225
1451	The current reschedule callback, or C<0>, if this functionality is	2226	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	2227	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.	2228	the periodic timer fires or C<ev_periodic_again> is being called.
1454		2229
1455	=back	2230	=back
1456		2231
1457	=head3 Examples	2232	=head3 Examples
1458		2233
1459	Example: Call a callback every hour, or, more precisely, whenever the	2234	Example: Call a callback every hour, or, more precisely, whenever the
1460	system clock is divisible by 3600. The callback invocation times have	2235	system time is divisible by 3600. The callback invocation times have
1461	potentially a lot of jitter, but good long-term stability.	2236	potentially a lot of jitter, but good long-term stability.
1462		2237
1463	static void	2238	static void
1464	clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)	2239	clock_cb (struct ev_loop *loop, ev_periodic *w, int revents)
1465	{	2240	{
1466	... its now a full hour (UTC, or TAI or whatever your clock follows)	2241	... its now a full hour (UTC, or TAI or whatever your clock follows)
1467	}	2242	}
1468		2243
1469	struct ev_periodic hourly_tick;	2244	ev_periodic hourly_tick;
1470	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);	2245	ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1471	ev_periodic_start (loop, &hourly_tick);	2246	ev_periodic_start (loop, &hourly_tick);
1472		2247
1473	Example: The same as above, but use a reschedule callback to do it:	2248	Example: The same as above, but use a reschedule callback to do it:
1474		2249
1475	#include <math.h>	2250	#include <math.h>
1476		2251
1477	static ev_tstamp	2252	static ev_tstamp
1478	my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)	2253	my_scheduler_cb (ev_periodic *w, ev_tstamp now)
1479	{	2254	{
1480	return fmod (now, 3600.) + 3600.;	2255	return now + (3600. - fmod (now, 3600.));
1481	}	2256	}
1482		2257
1483	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);	2258	ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1484		2259
1485	Example: Call a callback every hour, starting now:	2260	Example: Call a callback every hour, starting now:
1486		2261
1487	struct ev_periodic hourly_tick;	2262	ev_periodic hourly_tick;
1488	ev_periodic_init (&hourly_tick, clock_cb,	2263	ev_periodic_init (&hourly_tick, clock_cb,
1489	fmod (ev_now (loop), 3600.), 3600., 0);	2264	fmod (ev_now (loop), 3600.), 3600., 0);
1490	ev_periodic_start (loop, &hourly_tick);	2265	ev_periodic_start (loop, &hourly_tick);
1491		2266
1492		2267
1493	=head2 C<ev_signal> - signal me when a signal gets signalled!	2268	=head2 C<ev_signal> - signal me when a signal gets signalled!
1494		2269
1495	Signal watchers will trigger an event when the process receives a specific	2270	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	2271	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	2272	will try its best to deliver signals synchronously, i.e. as part of the
1498	normal event processing, like any other event.	2273	normal event processing, like any other event.
1499		2274
		2275	If you want signals to be delivered truly asynchronously, just use
		2276	C<sigaction> as you would do without libev and forget about sharing
		2277	the signal. You can even use C<ev_async> from a signal handler to
		2278	synchronously wake up an event loop.
		2279
1500	You can configure as many watchers as you like per signal. Only when the	2280	You can configure as many watchers as you like for the same signal, but
		2281	only within the same loop, i.e. you can watch for C<SIGINT> in your
		2282	default loop and for C<SIGIO> in another loop, but you cannot watch for
		2283	C<SIGINT> in both the default loop and another loop at the same time. At
		2284	the moment, C<SIGCHLD> is permanently tied to the default loop.
		2285
1501	first watcher gets started will libev actually register a signal watcher	2286	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	2287	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	2288	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		2289
1507	If possible and supported, libev will install its handlers with	2290	If possible and supported, libev will install its handlers with
1508	C<SA_RESTART> behaviour enabled, so system calls should not be unduly	2291	C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
1509	interrupted. If you have a problem with system calls getting interrupted by	2292	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	2293	interrupted by signals you can block all signals in an C<ev_check> watcher
1511	them in an C<ev_prepare> watcher.	2294	and unblock them in an C<ev_prepare> watcher.
		2295
		2296	=head3 The special problem of inheritance over fork/execve/pthread_create
		2297
		2298	Both the signal mask (C<sigprocmask>) and the signal disposition
		2299	(C<sigaction>) are unspecified after starting a signal watcher (and after
		2300	stopping it again), that is, libev might or might not block the signal,
		2301	and might or might not set or restore the installed signal handler.
		2302
		2303	While this does not matter for the signal disposition (libev never
		2304	sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
		2305	C<execve>), this matters for the signal mask: many programs do not expect
		2306	certain signals to be blocked.
		2307
		2308	This means that before calling C<exec> (from the child) you should reset
		2309	the signal mask to whatever "default" you expect (all clear is a good
		2310	choice usually).
		2311
		2312	The simplest way to ensure that the signal mask is reset in the child is
		2313	to install a fork handler with C<pthread_atfork> that resets it. That will
		2314	catch fork calls done by libraries (such as the libc) as well.
		2315
		2316	In current versions of libev, the signal will not be blocked indefinitely
		2317	unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces
		2318	the window of opportunity for problems, it will not go away, as libev
		2319	I<has> to modify the signal mask, at least temporarily.
		2320
		2321	So I can't stress this enough: I<If you do not reset your signal mask when
		2322	you expect it to be empty, you have a race condition in your code>. This
		2323	is not a libev-specific thing, this is true for most event libraries.
1512		2324
1513	=head3 Watcher-Specific Functions and Data Members	2325	=head3 Watcher-Specific Functions and Data Members
1514		2326
1515	=over 4	2327	=over 4
1516		2328
…		…
1527		2339
1528	=back	2340	=back
1529		2341
1530	=head3 Examples	2342	=head3 Examples
1531		2343
1532	Example: Try to exit cleanly on SIGINT and SIGTERM.	2344	Example: Try to exit cleanly on SIGINT.
1533		2345
1534	static void	2346	static void
1535	sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)	2347	sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
1536	{	2348	{
1537	ev_unloop (loop, EVUNLOOP_ALL);	2349	ev_break (loop, EVBREAK_ALL);
1538	}	2350	}
1539		2351
1540	struct ev_signal signal_watcher;	2352	ev_signal signal_watcher;
1541	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);	2353	ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1542	ev_signal_start (loop, &sigint_cb);	2354	ev_signal_start (loop, &signal_watcher);
1543		2355
1544		2356
1545	=head2 C<ev_child> - watch out for process status changes	2357	=head2 C<ev_child> - watch out for process status changes
1546		2358
1547	Child watchers trigger when your process receives a SIGCHLD in response to	2359	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	2360	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	2361	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	2362	has been forked (which implies it might have already exited), as long
1551	loop isn't entered (or is continued from a watcher).	2363	as the event loop isn't entered (or is continued from a watcher), i.e.,
		2364	forking and then immediately registering a watcher for the child is fine,
		2365	but forking and registering a watcher a few event loop iterations later or
		2366	in the next callback invocation is not.
1552		2367
1553	Only the default event loop is capable of handling signals, and therefore	2368	Only the default event loop is capable of handling signals, and therefore
1554	you can only register child watchers in the default event loop.	2369	you can only register child watchers in the default event loop.
1555		2370
		2371	Due to some design glitches inside libev, child watchers will always be
		2372	handled at maximum priority (their priority is set to C<EV_MAXPRI> by
		2373	libev)
		2374
1556	=head3 Process Interaction	2375	=head3 Process Interaction
1557		2376
1558	Libev grabs C<SIGCHLD> as soon as the default event loop is	2377	Libev grabs C<SIGCHLD> as soon as the default event loop is
1559	initialised. This is necessary to guarantee proper behaviour even if	2378	initialised. This is necessary to guarantee proper behaviour even if the
1560	the first child watcher is started after the child exits. The occurrence	2379	first child watcher is started after the child exits. The occurrence
1561	of C<SIGCHLD> is recorded asynchronously, but child reaping is done	2380	of C<SIGCHLD> is recorded asynchronously, but child reaping is done
1562	synchronously as part of the event loop processing. Libev always reaps all	2381	synchronously as part of the event loop processing. Libev always reaps all
1563	children, even ones not watched.	2382	children, even ones not watched.
1564		2383
1565	=head3 Overriding the Built-In Processing	2384	=head3 Overriding the Built-In Processing
…		…
1575	=head3 Stopping the Child Watcher	2394	=head3 Stopping the Child Watcher
1576		2395
1577	Currently, the child watcher never gets stopped, even when the	2396	Currently, the child watcher never gets stopped, even when the
1578	child terminates, so normally one needs to stop the watcher in the	2397	child terminates, so normally one needs to stop the watcher in the
1579	callback. Future versions of libev might stop the watcher automatically	2398	callback. Future versions of libev might stop the watcher automatically
1580	when a child exit is detected.	2399	when a child exit is detected (calling C<ev_child_stop> twice is not a
		2400	problem).
1581		2401
1582	=head3 Watcher-Specific Functions and Data Members	2402	=head3 Watcher-Specific Functions and Data Members
1583		2403
1584	=over 4	2404	=over 4
1585		2405
…		…
1617	its completion.	2437	its completion.
1618		2438
1619	ev_child cw;	2439	ev_child cw;
1620		2440
1621	static void	2441	static void
1622	child_cb (EV_P_ struct ev_child *w, int revents)	2442	child_cb (EV_P_ ev_child *w, int revents)
1623	{	2443	{
1624	ev_child_stop (EV_A_ w);	2444	ev_child_stop (EV_A_ w);
1625	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);	2445	printf ("process %d exited with status %x\n", w->rpid, w->rstatus);
1626	}	2446	}
1627		2447
…		…
1642		2462
1643		2463
1644	=head2 C<ev_stat> - did the file attributes just change?	2464	=head2 C<ev_stat> - did the file attributes just change?
1645		2465
1646	This watches a file system path for attribute changes. That is, it calls	2466	This watches a file system path for attribute changes. That is, it calls
1647	C<stat> regularly (or when the OS says it changed) and sees if it changed	2467	C<stat> on that path in regular intervals (or when the OS says it changed)
1648	compared to the last time, invoking the callback if it did.	2468	and sees if it changed compared to the last time, invoking the callback if
		2469	it did.
1649		2470
1650	The path does not need to exist: changing from "path exists" to "path does	2471	The path does not need to exist: changing from "path exists" to "path does
1651	not exist" is a status change like any other. The condition "path does	2472	not exist" is a status change like any other. The condition "path does not
1652	not exist" is signified by the C<st_nlink> field being zero (which is	2473	exist" (or more correctly "path cannot be stat'ed") is signified by the
1653	otherwise always forced to be at least one) and all the other fields of	2474	C<st_nlink> field being zero (which is otherwise always forced to be at
1654	the stat buffer having unspecified contents.	2475	least one) and all the other fields of the stat buffer having unspecified
		2476	contents.
1655		2477
1656	The path I<should> be absolute and I<must not> end in a slash. If it is	2478	The path I<must not> end in a slash or contain special components such as
		2479	C<.> or C<..>. The path I<should> be absolute: If it is relative and
1657	relative and your working directory changes, the behaviour is undefined.	2480	your working directory changes, then the behaviour is undefined.
1658		2481
1659	Since there is no standard to do this, the portable implementation simply	2482	Since there is no portable change notification interface available, the
1660	calls C<stat (2)> regularly on the path to see if it changed somehow. You	2483	portable implementation simply calls C<stat(2)> regularly on the path
1661	can specify a recommended polling interval for this case. If you specify	2484	to see if it changed somehow. You can specify a recommended polling
1662	a polling interval of C<0> (highly recommended!) then a I<suitable,	2485	interval for this case. If you specify a polling interval of C<0> (highly
1663	unspecified default> value will be used (which you can expect to be around	2486	recommended!) then a I<suitable, unspecified default> value will be used
1664	five seconds, although this might change dynamically). Libev will also	2487	(which you can expect to be around five seconds, although this might
1665	impose a minimum interval which is currently around C<0.1>, but thats	2488	change dynamically). Libev will also impose a minimum interval which is
1666	usually overkill.	2489	currently around C<0.1>, but that's usually overkill.
1667		2490
1668	This watcher type is not meant for massive numbers of stat watchers,	2491	This watcher type is not meant for massive numbers of stat watchers,
1669	as even with OS-supported change notifications, this can be	2492	as even with OS-supported change notifications, this can be
1670	resource-intensive.	2493	resource-intensive.
1671		2494
1672	At the time of this writing, only the Linux inotify interface is	2495	At the time of this writing, the only OS-specific interface implemented
1673	implemented (implementing kqueue support is left as an exercise for the	2496	is the Linux inotify interface (implementing kqueue support is left as an
1674	reader, note, however, that the author sees no way of implementing ev_stat	2497	exercise for the reader. Note, however, that the author sees no way of
1675	semantics with kqueue). Inotify will be used to give hints only and should	2498	implementing C<ev_stat> semantics with kqueue, except as a hint).
1676	not change the semantics of C<ev_stat> watchers, which means that libev
1677	sometimes needs to fall back to regular polling again even with inotify,
1678	but changes are usually detected immediately, and if the file exists there
1679	will be no polling.
1680		2499
1681	=head3 ABI Issues (Largefile Support)	2500	=head3 ABI Issues (Largefile Support)
1682		2501
1683	Libev by default (unless the user overrides this) uses the default	2502	Libev by default (unless the user overrides this) uses the default
1684	compilation environment, which means that on systems with large file	2503	compilation environment, which means that on systems with large file
1685	support disabled by default, you get the 32 bit version of the stat	2504	support disabled by default, you get the 32 bit version of the stat
1686	structure. When using the library from programs that change the ABI to	2505	structure. When using the library from programs that change the ABI to
1687	use 64 bit file offsets the programs will fail. In that case you have to	2506	use 64 bit file offsets the programs will fail. In that case you have to
1688	compile libev with the same flags to get binary compatibility. This is	2507	compile libev with the same flags to get binary compatibility. This is
1689	obviously the case with any flags that change the ABI, but the problem is	2508	obviously the case with any flags that change the ABI, but the problem is
1690	most noticeably disabled with ev_stat and large file support.	2509	most noticeably displayed with ev_stat and large file support.
1691		2510
1692	The solution for this is to lobby your distribution maker to make large	2511	The solution for this is to lobby your distribution maker to make large
1693	file interfaces available by default (as e.g. FreeBSD does) and not	2512	file interfaces available by default (as e.g. FreeBSD does) and not
1694	optional. Libev cannot simply switch on large file support because it has	2513	optional. Libev cannot simply switch on large file support because it has
1695	to exchange stat structures with application programs compiled using the	2514	to exchange stat structures with application programs compiled using the
1696	default compilation environment.	2515	default compilation environment.
1697		2516
1698	=head3 Inotify	2517	=head3 Inotify and Kqueue
1699		2518
1700	When C<inotify (7)> support has been compiled into libev (generally only	2519	When C<inotify (7)> support has been compiled into libev and present at
1701	available on Linux) and present at runtime, it will be used to speed up	2520	runtime, it will be used to speed up change detection where possible. The
1702	change detection where possible. The inotify descriptor will be created lazily	2521	inotify descriptor will be created lazily when the first C<ev_stat>
1703	when the first C<ev_stat> watcher is being started.	2522	watcher is being started.
1704		2523
1705	Inotify presence does not change the semantics of C<ev_stat> watchers	2524	Inotify presence does not change the semantics of C<ev_stat> watchers
1706	except that changes might be detected earlier, and in some cases, to avoid	2525	except that changes might be detected earlier, and in some cases, to avoid
1707	making regular C<stat> calls. Even in the presence of inotify support	2526	making regular C<stat> calls. Even in the presence of inotify support
1708	there are many cases where libev has to resort to regular C<stat> polling.	2527	there are many cases where libev has to resort to regular C<stat> polling,
		2528	but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too
		2529	many bugs), the path exists (i.e. stat succeeds), and the path resides on
		2530	a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and
		2531	xfs are fully working) libev usually gets away without polling.
1709		2532
1710	(There is no support for kqueue, as apparently it cannot be used to	2533	There is no support for kqueue, as apparently it cannot be used to
1711	implement this functionality, due to the requirement of having a file	2534	implement this functionality, due to the requirement of having a file
1712	descriptor open on the object at all times).	2535	descriptor open on the object at all times, and detecting renames, unlinks
		2536	etc. is difficult.
		2537
		2538	=head3 C<stat ()> is a synchronous operation
		2539
		2540	Libev doesn't normally do any kind of I/O itself, and so is not blocking
		2541	the process. The exception are C<ev_stat> watchers - those call C<stat
		2542	()>, which is a synchronous operation.
		2543
		2544	For local paths, this usually doesn't matter: unless the system is very
		2545	busy or the intervals between stat's are large, a stat call will be fast,
		2546	as the path data is usually in memory already (except when starting the
		2547	watcher).
		2548
		2549	For networked file systems, calling C<stat ()> can block an indefinite
		2550	time due to network issues, and even under good conditions, a stat call
		2551	often takes multiple milliseconds.
		2552
		2553	Therefore, it is best to avoid using C<ev_stat> watchers on networked
		2554	paths, although this is fully supported by libev.
1713		2555
1714	=head3 The special problem of stat time resolution	2556	=head3 The special problem of stat time resolution
1715		2557
1716	The C<stat ()> system call only supports full-second resolution portably, and	2558	The C<stat ()> system call only supports full-second resolution portably,
1717	even on systems where the resolution is higher, many file systems still	2559	and even on systems where the resolution is higher, most file systems
1718	only support whole seconds.	2560	still only support whole seconds.
1719		2561
1720	That means that, if the time is the only thing that changes, you can	2562	That means that, if the time is the only thing that changes, you can
1721	easily miss updates: on the first update, C<ev_stat> detects a change and	2563	easily miss updates: on the first update, C<ev_stat> detects a change and
1722	calls your callback, which does something. When there is another update	2564	calls your callback, which does something. When there is another update
1723	within the same second, C<ev_stat> will be unable to detect it as the stat	2565	within the same second, C<ev_stat> will be unable to detect unless the
1724	data does not change.	2566	stat data does change in other ways (e.g. file size).
1725		2567
1726	The solution to this is to delay acting on a change for slightly more	2568	The solution to this is to delay acting on a change for slightly more
1727	than a second (or till slightly after the next full second boundary), using	2569	than a second (or till slightly after the next full second boundary), using
1728	a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);	2570	a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);
1729	ev_timer_again (loop, w)>).	2571	ev_timer_again (loop, w)>).
…		…
1749	C<path>. The C<interval> is a hint on how quickly a change is expected to	2591	C<path>. The C<interval> is a hint on how quickly a change is expected to
1750	be detected and should normally be specified as C<0> to let libev choose	2592	be detected and should normally be specified as C<0> to let libev choose
1751	a suitable value. The memory pointed to by C<path> must point to the same	2593	a suitable value. The memory pointed to by C<path> must point to the same
1752	path for as long as the watcher is active.	2594	path for as long as the watcher is active.
1753		2595
1754	The callback will receive C<EV_STAT> when a change was detected, relative	2596	The callback will receive an C<EV_STAT> event when a change was detected,
1755	to the attributes at the time the watcher was started (or the last change	2597	relative to the attributes at the time the watcher was started (or the
1756	was detected).	2598	last change was detected).
1757		2599
1758	=item ev_stat_stat (loop, ev_stat *)	2600	=item ev_stat_stat (loop, ev_stat *)
1759		2601
1760	Updates the stat buffer immediately with new values. If you change the	2602	Updates the stat buffer immediately with new values. If you change the
1761	watched path in your callback, you could call this function to avoid	2603	watched path in your callback, you could call this function to avoid
…		…
1844		2686
1845		2687
1846	=head2 C<ev_idle> - when you've got nothing better to do...	2688	=head2 C<ev_idle> - when you've got nothing better to do...
1847		2689
1848	Idle watchers trigger events when no other events of the same or higher	2690	Idle watchers trigger events when no other events of the same or higher
1849	priority are pending (prepare, check and other idle watchers do not	2691	priority are pending (prepare, check and other idle watchers do not count
1850	count).	2692	as receiving "events").
1851		2693
1852	That is, as long as your process is busy handling sockets or timeouts	2694	That is, as long as your process is busy handling sockets or timeouts
1853	(or even signals, imagine) of the same or higher priority it will not be	2695	(or even signals, imagine) of the same or higher priority it will not be
1854	triggered. But when your process is idle (or only lower-priority watchers	2696	triggered. But when your process is idle (or only lower-priority watchers
1855	are pending), the idle watchers are being called once per event loop	2697	are pending), the idle watchers are being called once per event loop
…		…
1866		2708
1867	=head3 Watcher-Specific Functions and Data Members	2709	=head3 Watcher-Specific Functions and Data Members
1868		2710
1869	=over 4	2711	=over 4
1870		2712
1871	=item ev_idle_init (ev_signal *, callback)	2713	=item ev_idle_init (ev_idle *, callback)
1872		2714
1873	Initialises and configures the idle watcher - it has no parameters of any	2715	Initialises and configures the idle watcher - it has no parameters of any
1874	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	2716	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
1875	believe me.	2717	believe me.
1876		2718
…		…
1880		2722
1881	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the	2723	Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the
1882	callback, free it. Also, use no error checking, as usual.	2724	callback, free it. Also, use no error checking, as usual.
1883		2725
1884	static void	2726	static void
1885	idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)	2727	idle_cb (struct ev_loop *loop, ev_idle *w, int revents)
1886	{	2728	{
1887	free (w);	2729	free (w);
1888	// now do something you wanted to do when the program has	2730	// now do something you wanted to do when the program has
1889	// no longer anything immediate to do.	2731	// no longer anything immediate to do.
1890	}	2732	}
1891		2733
1892	struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));	2734	ev_idle *idle_watcher = malloc (sizeof (ev_idle));
1893	ev_idle_init (idle_watcher, idle_cb);	2735	ev_idle_init (idle_watcher, idle_cb);
1894	ev_idle_start (loop, idle_cb);	2736	ev_idle_start (loop, idle_watcher);
1895		2737
1896		2738
1897	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!	2739	=head2 C<ev_prepare> and C<ev_check> - customise your event loop!
1898		2740
1899	Prepare and check watchers are usually (but not always) used in tandem:	2741	Prepare and check watchers are usually (but not always) used in pairs:
1900	prepare watchers get invoked before the process blocks and check watchers	2742	prepare watchers get invoked before the process blocks and check watchers
1901	afterwards.	2743	afterwards.
1902		2744
1903	You I<must not> call C<ev_loop> or similar functions that enter	2745	You I<must not> call C<ev_run> or similar functions that enter
1904	the current event loop from either C<ev_prepare> or C<ev_check>	2746	the current event loop from either C<ev_prepare> or C<ev_check>
1905	watchers. Other loops than the current one are fine, however. The	2747	watchers. Other loops than the current one are fine, however. The
1906	rationale behind this is that you do not need to check for recursion in	2748	rationale behind this is that you do not need to check for recursion in
1907	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,	2749	those watchers, i.e. the sequence will always be C<ev_prepare>, blocking,
1908	C<ev_check> so if you have one watcher of each kind they will always be	2750	C<ev_check> so if you have one watcher of each kind they will always be
1909	called in pairs bracketing the blocking call.	2751	called in pairs bracketing the blocking call.
1910		2752
1911	Their main purpose is to integrate other event mechanisms into libev and	2753	Their main purpose is to integrate other event mechanisms into libev and
1912	their use is somewhat advanced. This could be used, for example, to track	2754	their use is somewhat advanced. They could be used, for example, to track
1913	variable changes, implement your own watchers, integrate net-snmp or a	2755	variable changes, implement your own watchers, integrate net-snmp or a
1914	coroutine library and lots more. They are also occasionally useful if	2756	coroutine library and lots more. They are also occasionally useful if
1915	you cache some data and want to flush it before blocking (for example,	2757	you cache some data and want to flush it before blocking (for example,
1916	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>	2758	in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>
1917	watcher).	2759	watcher).
1918		2760
1919	This is done by examining in each prepare call which file descriptors need	2761	This is done by examining in each prepare call which file descriptors
1920	to be watched by the other library, registering C<ev_io> watchers for	2762	need to be watched by the other library, registering C<ev_io> watchers
1921	them and starting an C<ev_timer> watcher for any timeouts (many libraries	2763	for them and starting an C<ev_timer> watcher for any timeouts (many
1922	provide just this functionality). Then, in the check watcher you check for	2764	libraries provide exactly this functionality). Then, in the check watcher,
1923	any events that occurred (by checking the pending status of all watchers	2765	you check for any events that occurred (by checking the pending status
1924	and stopping them) and call back into the library. The I/O and timer	2766	of all watchers and stopping them) and call back into the library. The
1925	callbacks will never actually be called (but must be valid nevertheless,	2767	I/O and timer callbacks will never actually be called (but must be valid
1926	because you never know, you know?).	2768	nevertheless, because you never know, you know?).
1927		2769
1928	As another example, the Perl Coro module uses these hooks to integrate	2770	As another example, the Perl Coro module uses these hooks to integrate
1929	coroutines into libev programs, by yielding to other active coroutines	2771	coroutines into libev programs, by yielding to other active coroutines
1930	during each prepare and only letting the process block if no coroutines	2772	during each prepare and only letting the process block if no coroutines
1931	are ready to run (it's actually more complicated: it only runs coroutines	2773	are ready to run (it's actually more complicated: it only runs coroutines
…		…
1934	loop from blocking if lower-priority coroutines are active, thus mapping	2776	loop from blocking if lower-priority coroutines are active, thus mapping
1935	low-priority coroutines to idle/background tasks).	2777	low-priority coroutines to idle/background tasks).
1936		2778
1937	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)	2779	It is recommended to give C<ev_check> watchers highest (C<EV_MAXPRI>)
1938	priority, to ensure that they are being run before any other watchers	2780	priority, to ensure that they are being run before any other watchers
		2781	after the poll (this doesn't matter for C<ev_prepare> watchers).
		2782
1939	after the poll. Also, C<ev_check> watchers (and C<ev_prepare> watchers,	2783	Also, C<ev_check> watchers (and C<ev_prepare> watchers, too) should not
1940	too) should not activate ("feed") events into libev. While libev fully	2784	activate ("feed") events into libev. While libev fully supports this, they
1941	supports this, they might get executed before other C<ev_check> watchers	2785	might get executed before other C<ev_check> watchers did their job. As
1942	did their job. As C<ev_check> watchers are often used to embed other	2786	C<ev_check> watchers are often used to embed other (non-libev) event
1943	(non-libev) event loops those other event loops might be in an unusable	2787	loops those other event loops might be in an unusable state until their
1944	state until their C<ev_check> watcher ran (always remind yourself to	2788	C<ev_check> watcher ran (always remind yourself to coexist peacefully with
1945	coexist peacefully with others).	2789	others).
1946		2790
1947	=head3 Watcher-Specific Functions and Data Members	2791	=head3 Watcher-Specific Functions and Data Members
1948		2792
1949	=over 4	2793	=over 4
1950		2794
…		…
1952		2796
1953	=item ev_check_init (ev_check *, callback)	2797	=item ev_check_init (ev_check *, callback)
1954		2798
1955	Initialises and configures the prepare or check watcher - they have no	2799	Initialises and configures the prepare or check watcher - they have no
1956	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>	2800	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>
1957	macros, but using them is utterly, utterly and completely pointless.	2801	macros, but using them is utterly, utterly, utterly and completely
		2802	pointless.
1958		2803
1959	=back	2804	=back
1960		2805
1961	=head3 Examples	2806	=head3 Examples
1962		2807
…		…
1975		2820
1976	static ev_io iow [nfd];	2821	static ev_io iow [nfd];
1977	static ev_timer tw;	2822	static ev_timer tw;
1978		2823
1979	static void	2824	static void
1980	io_cb (ev_loop *loop, ev_io *w, int revents)	2825	io_cb (struct ev_loop *loop, ev_io *w, int revents)
1981	{	2826	{
1982	}	2827	}
1983		2828
1984	// create io watchers for each fd and a timer before blocking	2829	// create io watchers for each fd and a timer before blocking
1985	static void	2830	static void
1986	adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)	2831	adns_prepare_cb (struct ev_loop *loop, ev_prepare *w, int revents)
1987	{	2832	{
1988	int timeout = 3600000;	2833	int timeout = 3600000;
1989	struct pollfd fds [nfd];	2834	struct pollfd fds [nfd];
1990	// actual code will need to loop here and realloc etc.	2835	// actual code will need to loop here and realloc etc.
1991	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));	2836	adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1992		2837
1993	/* the callback is illegal, but won't be called as we stop during check */	2838	/* the callback is illegal, but won't be called as we stop during check */
1994	ev_timer_init (&tw, 0, timeout * 1e-3);	2839	ev_timer_init (&tw, 0, timeout * 1e-3, 0.);
1995	ev_timer_start (loop, &tw);	2840	ev_timer_start (loop, &tw);
1996		2841
1997	// create one ev_io per pollfd	2842	// create one ev_io per pollfd
1998	for (int i = 0; i < nfd; ++i)	2843	for (int i = 0; i < nfd; ++i)
1999	{	2844	{
…		…
2006	}	2851	}
2007	}	2852	}
2008		2853
2009	// stop all watchers after blocking	2854	// stop all watchers after blocking
2010	static void	2855	static void
2011	adns_check_cb (ev_loop *loop, ev_check *w, int revents)	2856	adns_check_cb (struct ev_loop *loop, ev_check *w, int revents)
2012	{	2857	{
2013	ev_timer_stop (loop, &tw);	2858	ev_timer_stop (loop, &tw);
2014		2859
2015	for (int i = 0; i < nfd; ++i)	2860	for (int i = 0; i < nfd; ++i)
2016	{	2861	{
…		…
2055	}	2900	}
2056		2901
2057	// do not ever call adns_afterpoll	2902	// do not ever call adns_afterpoll
2058		2903
2059	Method 4: Do not use a prepare or check watcher because the module you	2904	Method 4: Do not use a prepare or check watcher because the module you
2060	want to embed is too inflexible to support it. Instead, you can override	2905	want to embed is not flexible enough to support it. Instead, you can
2061	their poll function. The drawback with this solution is that the main	2906	override their poll function. The drawback with this solution is that the
2062	loop is now no longer controllable by EV. The C<Glib::EV> module does	2907	main loop is now no longer controllable by EV. The C<Glib::EV> module uses
2063	this.	2908	this approach, effectively embedding EV as a client into the horrible
		2909	libglib event loop.
2064		2910
2065	static gint	2911	static gint
2066	event_poll_func (GPollFD *fds, guint nfds, gint timeout)	2912	event_poll_func (GPollFD *fds, guint nfds, gint timeout)
2067	{	2913	{
2068	int got_events = 0;	2914	int got_events = 0;
…		…
2072		2918
2073	if (timeout >= 0)	2919	if (timeout >= 0)
2074	// create/start timer	2920	// create/start timer
2075		2921
2076	// poll	2922	// poll
2077	ev_loop (EV_A_ 0);	2923	ev_run (EV_A_ 0);
2078		2924
2079	// stop timer again	2925	// stop timer again
2080	if (timeout >= 0)	2926	if (timeout >= 0)
2081	ev_timer_stop (EV_A_ &to);	2927	ev_timer_stop (EV_A_ &to);
2082		2928
…		…
2099	prioritise I/O.	2945	prioritise I/O.
2100		2946
2101	As an example for a bug workaround, the kqueue backend might only support	2947	As an example for a bug workaround, the kqueue backend might only support
2102	sockets on some platform, so it is unusable as generic backend, but you	2948	sockets on some platform, so it is unusable as generic backend, but you
2103	still want to make use of it because you have many sockets and it scales	2949	still want to make use of it because you have many sockets and it scales
2104	so nicely. In this case, you would create a kqueue-based loop and embed it	2950	so nicely. In this case, you would create a kqueue-based loop and embed
2105	into your default loop (which might use e.g. poll). Overall operation will	2951	it into your default loop (which might use e.g. poll). Overall operation
2106	be a bit slower because first libev has to poll and then call kevent, but	2952	will be a bit slower because first libev has to call C<poll> and then
2107	at least you can use both at what they are best.	2953	C<kevent>, but at least you can use both mechanisms for what they are
		2954	best: C<kqueue> for scalable sockets and C<poll> if you want it to work :)
2108		2955
2109	As for prioritising I/O: rarely you have the case where some fds have	2956	As for prioritising I/O: under rare circumstances you have the case where
2110	to be watched and handled very quickly (with low latency), and even	2957	some fds have to be watched and handled very quickly (with low latency),
2111	priorities and idle watchers might have too much overhead. In this case	2958	and even priorities and idle watchers might have too much overhead. In
2112	you would put all the high priority stuff in one loop and all the rest in	2959	this case you would put all the high priority stuff in one loop and all
2113	a second one, and embed the second one in the first.	2960	the rest in a second one, and embed the second one in the first.
2114		2961
2115	As long as the watcher is active, the callback will be invoked every time	2962	As long as the watcher is active, the callback will be invoked every
2116	there might be events pending in the embedded loop. The callback must then	2963	time there might be events pending in the embedded loop. The callback
2117	call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke	2964	must then call C<ev_embed_sweep (mainloop, watcher)> to make a single
2118	their callbacks (you could also start an idle watcher to give the embedded	2965	sweep and invoke their callbacks (the callback doesn't need to invoke the
2119	loop strictly lower priority for example). You can also set the callback	2966	C<ev_embed_sweep> function directly, it could also start an idle watcher
2120	to C<0>, in which case the embed watcher will automatically execute the	2967	to give the embedded loop strictly lower priority for example).
2121	embedded loop sweep.
2122		2968
2123	As long as the watcher is started it will automatically handle events. The	2969	You can also set the callback to C<0>, in which case the embed watcher
2124	callback will be invoked whenever some events have been handled. You can	2970	will automatically execute the embedded loop sweep whenever necessary.
2125	set the callback to C<0> to avoid having to specify one if you are not
2126	interested in that.
2127		2971
2128	Also, there have not currently been made special provisions for forking:	2972	Fork detection will be handled transparently while the C<ev_embed> watcher
2129	when you fork, you not only have to call C<ev_loop_fork> on both loops,	2973	is active, i.e., the embedded loop will automatically be forked when the
2130	but you will also have to stop and restart any C<ev_embed> watchers	2974	embedding loop forks. In other cases, the user is responsible for calling
2131	yourself.	2975	C<ev_loop_fork> on the embedded loop.
2132		2976
2133	Unfortunately, not all backends are embeddable, only the ones returned by	2977	Unfortunately, not all backends are embeddable: only the ones returned by
2134	C<ev_embeddable_backends> are, which, unfortunately, does not include any	2978	C<ev_embeddable_backends> are, which, unfortunately, does not include any
2135	portable one.	2979	portable one.
2136		2980
2137	So when you want to use this feature you will always have to be prepared	2981	So when you want to use this feature you will always have to be prepared
2138	that you cannot get an embeddable loop. The recommended way to get around	2982	that you cannot get an embeddable loop. The recommended way to get around
2139	this is to have a separate variables for your embeddable loop, try to	2983	this is to have a separate variables for your embeddable loop, try to
2140	create it, and if that fails, use the normal loop for everything.	2984	create it, and if that fails, use the normal loop for everything.
		2985
		2986	=head3 C<ev_embed> and fork
		2987
		2988	While the C<ev_embed> watcher is running, forks in the embedding loop will
		2989	automatically be applied to the embedded loop as well, so no special
		2990	fork handling is required in that case. When the watcher is not running,
		2991	however, it is still the task of the libev user to call C<ev_loop_fork ()>
		2992	as applicable.
2141		2993
2142	=head3 Watcher-Specific Functions and Data Members	2994	=head3 Watcher-Specific Functions and Data Members
2143		2995
2144	=over 4	2996	=over 4
2145		2997
…		…
2154	if you do not want that, you need to temporarily stop the embed watcher).	3006	if you do not want that, you need to temporarily stop the embed watcher).
2155		3007
2156	=item ev_embed_sweep (loop, ev_embed *)	3008	=item ev_embed_sweep (loop, ev_embed *)
2157		3009
2158	Make a single, non-blocking sweep over the embedded loop. This works	3010	Make a single, non-blocking sweep over the embedded loop. This works
2159	similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most	3011	similarly to C<ev_run (embedded_loop, EVRUN_NOWAIT)>, but in the most
2160	appropriate way for embedded loops.	3012	appropriate way for embedded loops.
2161		3013
2162	=item struct ev_loop *other [read-only]	3014	=item struct ev_loop *other [read-only]
2163		3015
2164	The embedded event loop.	3016	The embedded event loop.
…		…
2173	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be	3025	C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be
2174	used).	3026	used).
2175		3027
2176	struct ev_loop *loop_hi = ev_default_init (0);	3028	struct ev_loop *loop_hi = ev_default_init (0);
2177	struct ev_loop *loop_lo = 0;	3029	struct ev_loop *loop_lo = 0;
2178	struct ev_embed embed;	3030	ev_embed embed;
2179		3031
2180	// see if there is a chance of getting one that works	3032	// see if there is a chance of getting one that works
2181	// (remember that a flags value of 0 means autodetection)	3033	// (remember that a flags value of 0 means autodetection)
2182	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()	3034	loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
2183	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())	3035	? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
…		…
2197	kqueue implementation). Store the kqueue/socket-only event loop in	3049	kqueue implementation). Store the kqueue/socket-only event loop in
2198	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).	3050	C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
2199		3051
2200	struct ev_loop *loop = ev_default_init (0);	3052	struct ev_loop *loop = ev_default_init (0);
2201	struct ev_loop *loop_socket = 0;	3053	struct ev_loop *loop_socket = 0;
2202	struct ev_embed embed;	3054	ev_embed embed;
2203		3055
2204	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)	3056	if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
2205	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))	3057	if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
2206	{	3058	{
2207	ev_embed_init (&embed, 0, loop_socket);	3059	ev_embed_init (&embed, 0, loop_socket);
…		…
2222	event loop blocks next and before C<ev_check> watchers are being called,	3074	event loop blocks next and before C<ev_check> watchers are being called,
2223	and only in the child after the fork. If whoever good citizen calling	3075	and only in the child after the fork. If whoever good citizen calling
2224	C<ev_default_fork> cheats and calls it in the wrong process, the fork	3076	C<ev_default_fork> cheats and calls it in the wrong process, the fork
2225	handlers will be invoked, too, of course.	3077	handlers will be invoked, too, of course.
2226		3078
		3079	=head3 The special problem of life after fork - how is it possible?
		3080
		3081	Most uses of C<fork()> consist of forking, then some simple calls to set
		3082	up/change the process environment, followed by a call to C<exec()>. This
		3083	sequence should be handled by libev without any problems.
		3084
		3085	This changes when the application actually wants to do event handling
		3086	in the child, or both parent in child, in effect "continuing" after the
		3087	fork.
		3088
		3089	The default mode of operation (for libev, with application help to detect
		3090	forks) is to duplicate all the state in the child, as would be expected
		3091	when I<either> the parent I<or> the child process continues.
		3092
		3093	When both processes want to continue using libev, then this is usually the
		3094	wrong result. In that case, usually one process (typically the parent) is
		3095	supposed to continue with all watchers in place as before, while the other
		3096	process typically wants to start fresh, i.e. without any active watchers.
		3097
		3098	The cleanest and most efficient way to achieve that with libev is to
		3099	simply create a new event loop, which of course will be "empty", and
		3100	use that for new watchers. This has the advantage of not touching more
		3101	memory than necessary, and thus avoiding the copy-on-write, and the
		3102	disadvantage of having to use multiple event loops (which do not support
		3103	signal watchers).
		3104
		3105	When this is not possible, or you want to use the default loop for
		3106	other reasons, then in the process that wants to start "fresh", call
		3107	C<ev_loop_destroy (EV_DEFAULT)> followed by C<ev_default_loop (...)>.
		3108	Destroying the default loop will "orphan" (not stop) all registered
		3109	watchers, so you have to be careful not to execute code that modifies
		3110	those watchers. Note also that in that case, you have to re-register any
		3111	signal watchers.
		3112
2227	=head3 Watcher-Specific Functions and Data Members	3113	=head3 Watcher-Specific Functions and Data Members
2228		3114
2229	=over 4	3115	=over 4
2230		3116
2231	=item ev_fork_init (ev_signal *, callback)	3117	=item ev_fork_init (ev_fork *, callback)
2232		3118
2233	Initialises and configures the fork watcher - it has no parameters of any	3119	Initialises and configures the fork watcher - it has no parameters of any
2234	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,	3120	kind. There is a C<ev_fork_set> macro, but using it is utterly pointless,
2235	believe me.	3121	really.
2236		3122
2237	=back	3123	=back
2238		3124
2239		3125
		3126	=head2 C<ev_cleanup> - even the best things end
		3127
		3128	Cleanup watchers are called just before the event loop is being destroyed
		3129	by a call to C<ev_loop_destroy>.
		3130
		3131	While there is no guarantee that the event loop gets destroyed, cleanup
		3132	watchers provide a convenient method to install cleanup hooks for your
		3133	program, worker threads and so on - you just to make sure to destroy the
		3134	loop when you want them to be invoked.
		3135
		3136	Cleanup watchers are invoked in the same way as any other watcher. Unlike
		3137	all other watchers, they do not keep a reference to the event loop (which
		3138	makes a lot of sense if you think about it). Like all other watchers, you
		3139	can call libev functions in the callback, except C<ev_cleanup_start>.
		3140
		3141	=head3 Watcher-Specific Functions and Data Members
		3142
		3143	=over 4
		3144
		3145	=item ev_cleanup_init (ev_cleanup *, callback)
		3146
		3147	Initialises and configures the cleanup watcher - it has no parameters of
		3148	any kind. There is a C<ev_cleanup_set> macro, but using it is utterly
		3149	pointless, I assure you.
		3150
		3151	=back
		3152
		3153	Example: Register an atexit handler to destroy the default loop, so any
		3154	cleanup functions are called.
		3155
		3156	static void
		3157	program_exits (void)
		3158	{
		3159	ev_loop_destroy (EV_DEFAULT_UC);
		3160	}
		3161
		3162	...
		3163	atexit (program_exits);
		3164
		3165
2240	=head2 C<ev_async> - how to wake up another event loop	3166	=head2 C<ev_async> - how to wake up an event loop
2241		3167
2242	In general, you cannot use an C<ev_loop> from multiple threads or other	3168	In general, you cannot use an C<ev_run> from multiple threads or other
2243	asynchronous sources such as signal handlers (as opposed to multiple event	3169	asynchronous sources such as signal handlers (as opposed to multiple event
2244	loops - those are of course safe to use in different threads).	3170	loops - those are of course safe to use in different threads).
2245		3171
2246	Sometimes, however, you need to wake up another event loop you do not	3172	Sometimes, however, you need to wake up an event loop you do not control,
2247	control, for example because it belongs to another thread. This is what	3173	for example because it belongs to another thread. This is what C<ev_async>
2248	C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you	3174	watchers do: as long as the C<ev_async> watcher is active, you can signal
2249	can signal it by calling C<ev_async_send>, which is thread- and signal	3175	it by calling C<ev_async_send>, which is thread- and signal safe.
2250	safe.
2251		3176
2252	This functionality is very similar to C<ev_signal> watchers, as signals,	3177	This functionality is very similar to C<ev_signal> watchers, as signals,
2253	too, are asynchronous in nature, and signals, too, will be compressed	3178	too, are asynchronous in nature, and signals, too, will be compressed
2254	(i.e. the number of callback invocations may be less than the number of	3179	(i.e. the number of callback invocations may be less than the number of
2255	C<ev_async_sent> calls).	3180	C<ev_async_sent> calls).
…		…
2260	=head3 Queueing	3185	=head3 Queueing
2261		3186
2262	C<ev_async> does not support queueing of data in any way. The reason	3187	C<ev_async> does not support queueing of data in any way. The reason
2263	is that the author does not know of a simple (or any) algorithm for a	3188	is that the author does not know of a simple (or any) algorithm for a
2264	multiple-writer-single-reader queue that works in all cases and doesn't	3189	multiple-writer-single-reader queue that works in all cases and doesn't
2265	need elaborate support such as pthreads.	3190	need elaborate support such as pthreads or unportable memory access
		3191	semantics.
2266		3192
2267	That means that if you want to queue data, you have to provide your own	3193	That means that if you want to queue data, you have to provide your own
2268	queue. But at least I can tell you would implement locking around your	3194	queue. But at least I can tell you how to implement locking around your
2269	queue:	3195	queue:
2270		3196
2271	=over 4	3197	=over 4
2272		3198
2273	=item queueing from a signal handler context	3199	=item queueing from a signal handler context
2274		3200
2275	To implement race-free queueing, you simply add to the queue in the signal	3201	To implement race-free queueing, you simply add to the queue in the signal
2276	handler but you block the signal handler in the watcher callback. Here is an example that does that for	3202	handler but you block the signal handler in the watcher callback. Here is
2277	some fictitious SIGUSR1 handler:	3203	an example that does that for some fictitious SIGUSR1 handler:
2278		3204
2279	static ev_async mysig;	3205	static ev_async mysig;
2280		3206
2281	static void	3207	static void
2282	sigusr1_handler (void)	3208	sigusr1_handler (void)
…		…
2348	=over 4	3274	=over 4
2349		3275
2350	=item ev_async_init (ev_async *, callback)	3276	=item ev_async_init (ev_async *, callback)
2351		3277
2352	Initialises and configures the async watcher - it has no parameters of any	3278	Initialises and configures the async watcher - it has no parameters of any
2353	kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless,	3279	kind. There is a C<ev_async_set> macro, but using it is utterly pointless,
2354	believe me.	3280	trust me.
2355		3281
2356	=item ev_async_send (loop, ev_async *)	3282	=item ev_async_send (loop, ev_async *)
2357		3283
2358	Sends/signals/activates the given C<ev_async> watcher, that is, feeds	3284	Sends/signals/activates the given C<ev_async> watcher, that is, feeds
2359	an C<EV_ASYNC> event on the watcher into the event loop. Unlike	3285	an C<EV_ASYNC> event on the watcher into the event loop. Unlike
2360	C<ev_feed_event>, this call is safe to do in other threads, signal or	3286	C<ev_feed_event>, this call is safe to do from other threads, signal or
2361	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding	3287	similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding
2362	section below on what exactly this means).	3288	section below on what exactly this means).
2363		3289
		3290	Note that, as with other watchers in libev, multiple events might get
		3291	compressed into a single callback invocation (another way to look at this
		3292	is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>,
		3293	reset when the event loop detects that).
		3294
2364	This call incurs the overhead of a system call only once per loop iteration,	3295	This call incurs the overhead of a system call only once per event loop
2365	so while the overhead might be noticeable, it doesn't apply to repeated	3296	iteration, so while the overhead might be noticeable, it doesn't apply to
2366	calls to C<ev_async_send>.	3297	repeated calls to C<ev_async_send> for the same event loop.
2367		3298
2368	=item bool = ev_async_pending (ev_async *)	3299	=item bool = ev_async_pending (ev_async *)
2369		3300
2370	Returns a non-zero value when C<ev_async_send> has been called on the	3301	Returns a non-zero value when C<ev_async_send> has been called on the
2371	watcher but the event has not yet been processed (or even noted) by the	3302	watcher but the event has not yet been processed (or even noted) by the
…		…
2374	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When	3305	C<ev_async_send> sets a flag in the watcher and wakes up the loop. When
2375	the loop iterates next and checks for the watcher to have become active,	3306	the loop iterates next and checks for the watcher to have become active,
2376	it will reset the flag again. C<ev_async_pending> can be used to very	3307	it will reset the flag again. C<ev_async_pending> can be used to very
2377	quickly check whether invoking the loop might be a good idea.	3308	quickly check whether invoking the loop might be a good idea.
2378		3309
2379	Not that this does I<not> check whether the watcher itself is pending, only	3310	Not that this does I<not> check whether the watcher itself is pending,
2380	whether it has been requested to make this watcher pending.	3311	only whether it has been requested to make this watcher pending: there
		3312	is a time window between the event loop checking and resetting the async
		3313	notification, and the callback being invoked.
2381		3314
2382	=back	3315	=back
2383		3316
2384		3317
2385	=head1 OTHER FUNCTIONS	3318	=head1 OTHER FUNCTIONS
…		…
2389	=over 4	3322	=over 4
2390		3323
2391	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)	3324	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)
2392		3325
2393	This function combines a simple timer and an I/O watcher, calls your	3326	This function combines a simple timer and an I/O watcher, calls your
2394	callback on whichever event happens first and automatically stop both	3327	callback on whichever event happens first and automatically stops both
2395	watchers. This is useful if you want to wait for a single event on an fd	3328	watchers. This is useful if you want to wait for a single event on an fd
2396	or timeout without having to allocate/configure/start/stop/free one or	3329	or timeout without having to allocate/configure/start/stop/free one or
2397	more watchers yourself.	3330	more watchers yourself.
2398		3331
2399	If C<fd> is less than 0, then no I/O watcher will be started and events	3332	If C<fd> is less than 0, then no I/O watcher will be started and the
2400	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and	3333	C<events> argument is being ignored. Otherwise, an C<ev_io> watcher for
2401	C<events> set will be created and started.	3334	the given C<fd> and C<events> set will be created and started.
2402		3335
2403	If C<timeout> is less than 0, then no timeout watcher will be	3336	If C<timeout> is less than 0, then no timeout watcher will be
2404	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	3337	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
2405	repeat = 0) will be started. While C<0> is a valid timeout, it is of	3338	repeat = 0) will be started. C<0> is a valid timeout.
2406	dubious value.
2407		3339
2408	The callback has the type C<void (*cb)(int revents, void *arg)> and gets	3340	The callback has the type C<void (*cb)(int revents, void *arg)> and is
2409	passed an C<revents> set like normal event callbacks (a combination of	3341	passed an C<revents> set like normal event callbacks (a combination of
2410	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	3342	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMER>) and the C<arg>
2411	value passed to C<ev_once>:	3343	value passed to C<ev_once>. Note that it is possible to receive I<both>
		3344	a timeout and an io event at the same time - you probably should give io
		3345	events precedence.
		3346
		3347	Example: wait up to ten seconds for data to appear on STDIN_FILENO.
2412		3348
2413	static void stdin_ready (int revents, void *arg)	3349	static void stdin_ready (int revents, void *arg)
2414	{	3350	{
		3351	if (revents & EV_READ)
		3352	/* stdin might have data for us, joy! */;
2415	if (revents & EV_TIMEOUT)	3353	else if (revents & EV_TIMER)
2416	/* doh, nothing entered */;	3354	/* doh, nothing entered */;
2417	else if (revents & EV_READ)
2418	/* stdin might have data for us, joy! */;
2419	}	3355	}
2420		3356
2421	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);	3357	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
2422		3358
2423	=item ev_feed_event (ev_loop *, watcher *, int revents)
2424
2425	Feeds the given event set into the event loop, as if the specified event
2426	had happened for the specified watcher (which must be a pointer to an
2427	initialised but not necessarily started event watcher).
2428
2429	=item ev_feed_fd_event (ev_loop *, int fd, int revents)	3359	=item ev_feed_fd_event (loop, int fd, int revents)
2430		3360
2431	Feed an event on the given fd, as if a file descriptor backend detected	3361	Feed an event on the given fd, as if a file descriptor backend detected
2432	the given events it.	3362	the given events it.
2433		3363
2434	=item ev_feed_signal_event (ev_loop *loop, int signum)	3364	=item ev_feed_signal_event (loop, int signum)
2435		3365
2436	Feed an event as if the given signal occurred (C<loop> must be the default	3366	Feed an event as if the given signal occurred (C<loop> must be the default
2437	loop!).	3367	loop!).
2438		3368
2439	=back	3369	=back
…		…
2458	=item * Priorities are not currently supported. Initialising priorities	3388	=item * Priorities are not currently supported. Initialising priorities
2459	will fail and all watchers will have the same priority, even though there	3389	will fail and all watchers will have the same priority, even though there
2460	is an ev_pri field.	3390	is an ev_pri field.
2461		3391
2462	=item * In libevent, the last base created gets the signals, in libev, the	3392	=item * In libevent, the last base created gets the signals, in libev, the
2463	first base created (== the default loop) gets the signals.	3393	base that registered the signal gets the signals.
2464		3394
2465	=item * Other members are not supported.	3395	=item * Other members are not supported.
2466		3396
2467	=item * The libev emulation is I<not> ABI compatible to libevent, you need	3397	=item * The libev emulation is I<not> ABI compatible to libevent, you need
2468	to use the libev header file and library.	3398	to use the libev header file and library.
…		…
2519		3449
2520	=over 4	3450	=over 4
2521		3451
2522	=item ev::TYPE::TYPE ()	3452	=item ev::TYPE::TYPE ()
2523		3453
2524	=item ev::TYPE::TYPE (struct ev_loop *)	3454	=item ev::TYPE::TYPE (loop)
2525		3455
2526	=item ev::TYPE::~TYPE	3456	=item ev::TYPE::~TYPE
2527		3457
2528	The constructor (optionally) takes an event loop to associate the watcher	3458	The constructor (optionally) takes an event loop to associate the watcher
2529	with. If it is omitted, it will use C<EV_DEFAULT>.	3459	with. If it is omitted, it will use C<EV_DEFAULT>.
…		…
2561		3491
2562	myclass obj;	3492	myclass obj;
2563	ev::io iow;	3493	ev::io iow;
2564	iow.set <myclass, &myclass::io_cb> (&obj);	3494	iow.set <myclass, &myclass::io_cb> (&obj);
2565		3495
		3496	=item w->set (object *)
		3497
		3498	This is a variation of a method callback - leaving out the method to call
		3499	will default the method to C<operator ()>, which makes it possible to use
		3500	functor objects without having to manually specify the C<operator ()> all
		3501	the time. Incidentally, you can then also leave out the template argument
		3502	list.
		3503
		3504	The C<operator ()> method prototype must be C<void operator ()(watcher &w,
		3505	int revents)>.
		3506
		3507	See the method-C<set> above for more details.
		3508
		3509	Example: use a functor object as callback.
		3510
		3511	struct myfunctor
		3512	{
		3513	void operator() (ev::io &w, int revents)
		3514	{
		3515	...
		3516	}
		3517	}
		3518
		3519	myfunctor f;
		3520
		3521	ev::io w;
		3522	w.set (&f);
		3523
2566	=item w->set<function> (void *data = 0)	3524	=item w->set<function> (void *data = 0)
2567		3525
2568	Also sets a callback, but uses a static method or plain function as	3526	Also sets a callback, but uses a static method or plain function as
2569	callback. The optional C<data> argument will be stored in the watcher's	3527	callback. The optional C<data> argument will be stored in the watcher's
2570	C<data> member and is free for you to use.	3528	C<data> member and is free for you to use.
2571		3529
2572	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.	3530	The prototype of the C<function> must be C<void (*)(ev::TYPE &w, int)>.
2573		3531
2574	See the method-C<set> above for more details.	3532	See the method-C<set> above for more details.
2575		3533
2576	Example:	3534	Example: Use a plain function as callback.
2577		3535
2578	static void io_cb (ev::io &w, int revents) { }	3536	static void io_cb (ev::io &w, int revents) { }
2579	iow.set <io_cb> ();	3537	iow.set <io_cb> ();
2580		3538
2581	=item w->set (struct ev_loop *)	3539	=item w->set (loop)
2582		3540
2583	Associates a different C<struct ev_loop> with this watcher. You can only	3541	Associates a different C<struct ev_loop> with this watcher. You can only
2584	do this when the watcher is inactive (and not pending either).	3542	do this when the watcher is inactive (and not pending either).
2585		3543
2586	=item w->set ([arguments])	3544	=item w->set ([arguments])
2587		3545
2588	Basically the same as C<ev_TYPE_set>, with the same arguments. Must be	3546	Basically the same as C<ev_TYPE_set>, with the same arguments. Either this
2589	called at least once. Unlike the C counterpart, an active watcher gets	3547	method or a suitable start method must be called at least once. Unlike the
2590	automatically stopped and restarted when reconfiguring it with this	3548	C counterpart, an active watcher gets automatically stopped and restarted
2591	method.	3549	when reconfiguring it with this method.
2592		3550
2593	=item w->start ()	3551	=item w->start ()
2594		3552
2595	Starts the watcher. Note that there is no C<loop> argument, as the	3553	Starts the watcher. Note that there is no C<loop> argument, as the
2596	constructor already stores the event loop.	3554	constructor already stores the event loop.
2597		3555
		3556	=item w->start ([arguments])
		3557
		3558	Instead of calling C<set> and C<start> methods separately, it is often
		3559	convenient to wrap them in one call. Uses the same type of arguments as
		3560	the configure C<set> method of the watcher.
		3561
2598	=item w->stop ()	3562	=item w->stop ()
2599		3563
2600	Stops the watcher if it is active. Again, no C<loop> argument.	3564	Stops the watcher if it is active. Again, no C<loop> argument.
2601		3565
2602	=item w->again () (C<ev::timer>, C<ev::periodic> only)	3566	=item w->again () (C<ev::timer>, C<ev::periodic> only)
…		…
2614		3578
2615	=back	3579	=back
2616		3580
2617	=back	3581	=back
2618		3582
2619	Example: Define a class with an IO and idle watcher, start one of them in	3583	Example: Define a class with two I/O and idle watchers, start the I/O
2620	the constructor.	3584	watchers in the constructor.
2621		3585
2622	class myclass	3586	class myclass
2623	{	3587	{
2624	ev::io io; void io_cb (ev::io &w, int revents);	3588	ev::io io ; void io_cb (ev::io &w, int revents);
		3589	ev::io2 io2 ; void io2_cb (ev::io &w, int revents);
2625	ev:idle idle void idle_cb (ev::idle &w, int revents);	3590	ev::idle idle; void idle_cb (ev::idle &w, int revents);
2626		3591
2627	myclass (int fd)	3592	myclass (int fd)
2628	{	3593	{
2629	io .set <myclass, &myclass::io_cb > (this);	3594	io .set <myclass, &myclass::io_cb > (this);
		3595	io2 .set <myclass, &myclass::io2_cb > (this);
2630	idle.set <myclass, &myclass::idle_cb> (this);	3596	idle.set <myclass, &myclass::idle_cb> (this);
2631		3597
2632	io.start (fd, ev::READ);	3598	io.set (fd, ev::WRITE); // configure the watcher
		3599	io.start (); // start it whenever convenient
		3600
		3601	io2.start (fd, ev::READ); // set + start in one call
2633	}	3602	}
2634	};	3603	};
2635		3604
2636		3605
2637	=head1 OTHER LANGUAGE BINDINGS	3606	=head1 OTHER LANGUAGE BINDINGS
…		…
2646	=item Perl	3615	=item Perl
2647		3616
2648	The EV module implements the full libev API and is actually used to test	3617	The EV module implements the full libev API and is actually used to test
2649	libev. EV is developed together with libev. Apart from the EV core module,	3618	libev. EV is developed together with libev. Apart from the EV core module,
2650	there are additional modules that implement libev-compatible interfaces	3619	there are additional modules that implement libev-compatible interfaces
2651	to C<libadns> (C<EV::ADNS>), C<Net::SNMP> (C<Net::SNMP::EV>) and the	3620	to C<libadns> (C<EV::ADNS>, but C<AnyEvent::DNS> is preferred nowadays),
2652	C<libglib> event core (C<Glib::EV> and C<EV::Glib>).	3621	C<Net::SNMP> (C<Net::SNMP::EV>) and the C<libglib> event core (C<Glib::EV>
		3622	and C<EV::Glib>).
2653		3623
2654	It can be found and installed via CPAN, its homepage is at	3624	It can be found and installed via CPAN, its homepage is at
2655	L<http://software.schmorp.de/pkg/EV>.	3625	L<http://software.schmorp.de/pkg/EV>.
2656		3626
2657	=item Python	3627	=item Python
2658		3628
2659	Python bindings can be found at L<http://code.google.com/p/pyev/>. It	3629	Python bindings can be found at L<http://code.google.com/p/pyev/>. It
2660	seems to be quite complete and well-documented. Note, however, that the	3630	seems to be quite complete and well-documented.
2661	patch they require for libev is outright dangerous as it breaks the ABI
2662	for everybody else, and therefore, should never be applied in an installed
2663	libev (if python requires an incompatible ABI then it needs to embed
2664	libev).
2665		3631
2666	=item Ruby	3632	=item Ruby
2667		3633
2668	Tony Arcieri has written a ruby extension that offers access to a subset	3634	Tony Arcieri has written a ruby extension that offers access to a subset
2669	of the libev API and adds file handle abstractions, asynchronous DNS and	3635	of the libev API and adds file handle abstractions, asynchronous DNS and
2670	more on top of it. It can be found via gem servers. Its homepage is at	3636	more on top of it. It can be found via gem servers. Its homepage is at
2671	L<http://rev.rubyforge.org/>.	3637	L<http://rev.rubyforge.org/>.
2672		3638
		3639	Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190>
		3640	makes rev work even on mingw.
		3641
		3642	=item Haskell
		3643
		3644	A haskell binding to libev is available at
		3645	L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>.
		3646
2673	=item D	3647	=item D
2674		3648
2675	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to	3649	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
2676	be found at L<http://proj.llucax.com.ar/wiki/evd>.	3650	be found at L<http://proj.llucax.com.ar/wiki/evd>.
		3651
		3652	=item Ocaml
		3653
		3654	Erkki Seppala has written Ocaml bindings for libev, to be found at
		3655	L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>.
		3656
		3657	=item Lua
		3658
		3659	Brian Maher has written a partial interface to libev for lua (at the
		3660	time of this writing, only C<ev_io> and C<ev_timer>), to be found at
		3661	L<http://github.com/brimworks/lua-ev>.
2677		3662
2678	=back	3663	=back
2679		3664
2680		3665
2681	=head1 MACRO MAGIC	3666	=head1 MACRO MAGIC
…		…
2695	loop argument"). The C<EV_A> form is used when this is the sole argument,	3680	loop argument"). The C<EV_A> form is used when this is the sole argument,
2696	C<EV_A_> is used when other arguments are following. Example:	3681	C<EV_A_> is used when other arguments are following. Example:
2697		3682
2698	ev_unref (EV_A);	3683	ev_unref (EV_A);
2699	ev_timer_add (EV_A_ watcher);	3684	ev_timer_add (EV_A_ watcher);
2700	ev_loop (EV_A_ 0);	3685	ev_run (EV_A_ 0);
2701		3686
2702	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,	3687	It assumes the variable C<loop> of type C<struct ev_loop *> is in scope,
2703	which is often provided by the following macro.	3688	which is often provided by the following macro.
2704		3689
2705	=item C<EV_P>, C<EV_P_>	3690	=item C<EV_P>, C<EV_P_>
…		…
2745	}	3730	}
2746		3731
2747	ev_check check;	3732	ev_check check;
2748	ev_check_init (&check, check_cb);	3733	ev_check_init (&check, check_cb);
2749	ev_check_start (EV_DEFAULT_ &check);	3734	ev_check_start (EV_DEFAULT_ &check);
2750	ev_loop (EV_DEFAULT_ 0);	3735	ev_run (EV_DEFAULT_ 0);
2751		3736
2752	=head1 EMBEDDING	3737	=head1 EMBEDDING
2753		3738
2754	Libev can (and often is) directly embedded into host	3739	Libev can (and often is) directly embedded into host
2755	applications. Examples of applications that embed it include the Deliantra	3740	applications. Examples of applications that embed it include the Deliantra
…		…
2782		3767
2783	#define EV_STANDALONE 1	3768	#define EV_STANDALONE 1
2784	#include "ev.h"	3769	#include "ev.h"
2785		3770
2786	Both header files and implementation files can be compiled with a C++	3771	Both header files and implementation files can be compiled with a C++
2787	compiler (at least, thats a stated goal, and breakage will be treated	3772	compiler (at least, that's a stated goal, and breakage will be treated
2788	as a bug).	3773	as a bug).
2789		3774
2790	You need the following files in your source tree, or in a directory	3775	You need the following files in your source tree, or in a directory
2791	in your include path (e.g. in libev/ when using -Ilibev):	3776	in your include path (e.g. in libev/ when using -Ilibev):
2792		3777
…		…
2835	libev.m4	3820	libev.m4
2836		3821
2837	=head2 PREPROCESSOR SYMBOLS/MACROS	3822	=head2 PREPROCESSOR SYMBOLS/MACROS
2838		3823
2839	Libev can be configured via a variety of preprocessor symbols you have to	3824	Libev can be configured via a variety of preprocessor symbols you have to
2840	define before including any of its files. The default in the absence of	3825	define before including (or compiling) any of its files. The default in
2841	autoconf is noted for every option.	3826	the absence of autoconf is documented for every option.
		3827
		3828	Symbols marked with "(h)" do not change the ABI, and can have different
		3829	values when compiling libev vs. including F<ev.h>, so it is permissible
		3830	to redefine them before including F<ev.h> without breaking compatibility
		3831	to a compiled library. All other symbols change the ABI, which means all
		3832	users of libev and the libev code itself must be compiled with compatible
		3833	settings.
2842		3834
2843	=over 4	3835	=over 4
2844		3836
		3837	=item EV_COMPAT3 (h)
		3838
		3839	Backwards compatibility is a major concern for libev. This is why this
		3840	release of libev comes with wrappers for the functions and symbols that
		3841	have been renamed between libev version 3 and 4.
		3842
		3843	You can disable these wrappers (to test compatibility with future
		3844	versions) by defining C<EV_COMPAT3> to C<0> when compiling your
		3845	sources. This has the additional advantage that you can drop the C<struct>
		3846	from C<struct ev_loop> declarations, as libev will provide an C<ev_loop>
		3847	typedef in that case.
		3848
		3849	In some future version, the default for C<EV_COMPAT3> will become C<0>,
		3850	and in some even more future version the compatibility code will be
		3851	removed completely.
		3852
2845	=item EV_STANDALONE	3853	=item EV_STANDALONE (h)
2846		3854
2847	Must always be C<1> if you do not use autoconf configuration, which	3855	Must always be C<1> if you do not use autoconf configuration, which
2848	keeps libev from including F<config.h>, and it also defines dummy	3856	keeps libev from including F<config.h>, and it also defines dummy
2849	implementations for some libevent functions (such as logging, which is not	3857	implementations for some libevent functions (such as logging, which is not
2850	supported). It will also not define any of the structs usually found in	3858	supported). It will also not define any of the structs usually found in
2851	F<event.h> that are not directly supported by the libev core alone.	3859	F<event.h> that are not directly supported by the libev core alone.
2852		3860
		3861	In standalone mode, libev will still try to automatically deduce the
		3862	configuration, but has to be more conservative.
		3863
2853	=item EV_USE_MONOTONIC	3864	=item EV_USE_MONOTONIC
2854		3865
2855	If defined to be C<1>, libev will try to detect the availability of the	3866	If defined to be C<1>, libev will try to detect the availability of the
2856	monotonic clock option at both compile time and runtime. Otherwise no use	3867	monotonic clock option at both compile time and runtime. Otherwise no
2857	of the monotonic clock option will be attempted. If you enable this, you	3868	use of the monotonic clock option will be attempted. If you enable this,
2858	usually have to link against librt or something similar. Enabling it when	3869	you usually have to link against librt or something similar. Enabling it
2859	the functionality isn't available is safe, though, although you have	3870	when the functionality isn't available is safe, though, although you have
2860	to make sure you link against any libraries where the C<clock_gettime>	3871	to make sure you link against any libraries where the C<clock_gettime>
2861	function is hiding in (often F<-lrt>).	3872	function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>.
2862		3873
2863	=item EV_USE_REALTIME	3874	=item EV_USE_REALTIME
2864		3875
2865	If defined to be C<1>, libev will try to detect the availability of the	3876	If defined to be C<1>, libev will try to detect the availability of the
2866	real-time clock option at compile time (and assume its availability at	3877	real-time clock option at compile time (and assume its availability
2867	runtime if successful). Otherwise no use of the real-time clock option will	3878	at runtime if successful). Otherwise no use of the real-time clock
2868	be attempted. This effectively replaces C<gettimeofday> by C<clock_get	3879	option will be attempted. This effectively replaces C<gettimeofday>
2869	(CLOCK_REALTIME, ...)> and will not normally affect correctness. See the	3880	by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect
2870	note about libraries in the description of C<EV_USE_MONOTONIC>, though.	3881	correctness. See the note about libraries in the description of
		3882	C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of
		3883	C<EV_USE_CLOCK_SYSCALL>.
		3884
		3885	=item EV_USE_CLOCK_SYSCALL
		3886
		3887	If defined to be C<1>, libev will try to use a direct syscall instead
		3888	of calling the system-provided C<clock_gettime> function. This option
		3889	exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt>
		3890	unconditionally pulls in C<libpthread>, slowing down single-threaded
		3891	programs needlessly. Using a direct syscall is slightly slower (in
		3892	theory), because no optimised vdso implementation can be used, but avoids
		3893	the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or
		3894	higher, as it simplifies linking (no need for C<-lrt>).
2871		3895
2872	=item EV_USE_NANOSLEEP	3896	=item EV_USE_NANOSLEEP
2873		3897
2874	If defined to be C<1>, libev will assume that C<nanosleep ()> is available	3898	If defined to be C<1>, libev will assume that C<nanosleep ()> is available
2875	and will use it for delays. Otherwise it will use C<select ()>.	3899	and will use it for delays. Otherwise it will use C<select ()>.
…		…
2891		3915
2892	=item EV_SELECT_USE_FD_SET	3916	=item EV_SELECT_USE_FD_SET
2893		3917
2894	If defined to C<1>, then the select backend will use the system C<fd_set>	3918	If defined to C<1>, then the select backend will use the system C<fd_set>
2895	structure. This is useful if libev doesn't compile due to a missing	3919	structure. This is useful if libev doesn't compile due to a missing
2896	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on	3920	C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout
2897	exotic systems. This usually limits the range of file descriptors to some	3921	on exotic systems. This usually limits the range of file descriptors to
2898	low limit such as 1024 or might have other limitations (winsocket only	3922	some low limit such as 1024 or might have other limitations (winsocket
2899	allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might	3923	only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation,
2900	influence the size of the C<fd_set> used.	3924	configures the maximum size of the C<fd_set>.
2901		3925
2902	=item EV_SELECT_IS_WINSOCKET	3926	=item EV_SELECT_IS_WINSOCKET
2903		3927
2904	When defined to C<1>, the select backend will assume that	3928	When defined to C<1>, the select backend will assume that
2905	select/socket/connect etc. don't understand file descriptors but	3929	select/socket/connect etc. don't understand file descriptors but
…		…
2907	be used is the winsock select). This means that it will call	3931	be used is the winsock select). This means that it will call
2908	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,	3932	C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
2909	it is assumed that all these functions actually work on fds, even	3933	it is assumed that all these functions actually work on fds, even
2910	on win32. Should not be defined on non-win32 platforms.	3934	on win32. Should not be defined on non-win32 platforms.
2911		3935
2912	=item EV_FD_TO_WIN32_HANDLE	3936	=item EV_FD_TO_WIN32_HANDLE(fd)
2913		3937
2914	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map	3938	If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map
2915	file descriptors to socket handles. When not defining this symbol (the	3939	file descriptors to socket handles. When not defining this symbol (the
2916	default), then libev will call C<_get_osfhandle>, which is usually	3940	default), then libev will call C<_get_osfhandle>, which is usually
2917	correct. In some cases, programs use their own file descriptor management,	3941	correct. In some cases, programs use their own file descriptor management,
2918	in which case they can provide this function to map fds to socket handles.	3942	in which case they can provide this function to map fds to socket handles.
		3943
		3944	=item EV_WIN32_HANDLE_TO_FD(handle)
		3945
		3946	If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors
		3947	using the standard C<_open_osfhandle> function. For programs implementing
		3948	their own fd to handle mapping, overwriting this function makes it easier
		3949	to do so. This can be done by defining this macro to an appropriate value.
		3950
		3951	=item EV_WIN32_CLOSE_FD(fd)
		3952
		3953	If programs implement their own fd to handle mapping on win32, then this
		3954	macro can be used to override the C<close> function, useful to unregister
		3955	file descriptors again. Note that the replacement function has to close
		3956	the underlying OS handle.
2919		3957
2920	=item EV_USE_POLL	3958	=item EV_USE_POLL
2921		3959
2922	If defined to be C<1>, libev will compile in support for the C<poll>(2)	3960	If defined to be C<1>, libev will compile in support for the C<poll>(2)
2923	backend. Otherwise it will be enabled on non-win32 platforms. It	3961	backend. Otherwise it will be enabled on non-win32 platforms. It
…		…
2970	as well as for signal and thread safety in C<ev_async> watchers.	4008	as well as for signal and thread safety in C<ev_async> watchers.
2971		4009
2972	In the absence of this define, libev will use C<sig_atomic_t volatile>	4010	In the absence of this define, libev will use C<sig_atomic_t volatile>
2973	(from F<signal.h>), which is usually good enough on most platforms.	4011	(from F<signal.h>), which is usually good enough on most platforms.
2974		4012
2975	=item EV_H	4013	=item EV_H (h)
2976		4014
2977	The name of the F<ev.h> header file used to include it. The default if	4015	The name of the F<ev.h> header file used to include it. The default if
2978	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be	4016	undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
2979	used to virtually rename the F<ev.h> header file in case of conflicts.	4017	used to virtually rename the F<ev.h> header file in case of conflicts.
2980		4018
2981	=item EV_CONFIG_H	4019	=item EV_CONFIG_H (h)
2982		4020
2983	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override	4021	If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
2984	F<ev.c>'s idea of where to find the F<config.h> file, similarly to	4022	F<ev.c>'s idea of where to find the F<config.h> file, similarly to
2985	C<EV_H>, above.	4023	C<EV_H>, above.
2986		4024
2987	=item EV_EVENT_H	4025	=item EV_EVENT_H (h)
2988		4026
2989	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea	4027	Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
2990	of how the F<event.h> header can be found, the default is C<"event.h">.	4028	of how the F<event.h> header can be found, the default is C<"event.h">.
2991		4029
2992	=item EV_PROTOTYPES	4030	=item EV_PROTOTYPES (h)
2993		4031
2994	If defined to be C<0>, then F<ev.h> will not define any function	4032	If defined to be C<0>, then F<ev.h> will not define any function
2995	prototypes, but still define all the structs and other symbols. This is	4033	prototypes, but still define all the structs and other symbols. This is
2996	occasionally useful if you want to provide your own wrapper functions	4034	occasionally useful if you want to provide your own wrapper functions
2997	around libev functions.	4035	around libev functions.
…		…
3016	When doing priority-based operations, libev usually has to linearly search	4054	When doing priority-based operations, libev usually has to linearly search
3017	all the priorities, so having many of them (hundreds) uses a lot of space	4055	all the priorities, so having many of them (hundreds) uses a lot of space
3018	and time, so using the defaults of five priorities (-2 .. +2) is usually	4056	and time, so using the defaults of five priorities (-2 .. +2) is usually
3019	fine.	4057	fine.
3020		4058
3021	If your embedding application does not need any priorities, defining these both to	4059	If your embedding application does not need any priorities, defining these
3022	C<0> will save some memory and CPU.	4060	both to C<0> will save some memory and CPU.
3023		4061
3024	=item EV_PERIODIC_ENABLE	4062	=item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE,
		4063	EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE,
		4064	EV_ASYNC_ENABLE, EV_CHILD_ENABLE.
3025		4065
3026	If undefined or defined to be C<1>, then periodic timers are supported. If	4066	If undefined or defined to be C<1> (and the platform supports it), then
3027	defined to be C<0>, then they are not. Disabling them saves a few kB of	4067	the respective watcher type is supported. If defined to be C<0>, then it
3028	code.	4068	is not. Disabling watcher types mainly saves code size.
3029		4069
3030	=item EV_IDLE_ENABLE	4070	=item EV_FEATURES
3031
3032	If undefined or defined to be C<1>, then idle watchers are supported. If
3033	defined to be C<0>, then they are not. Disabling them saves a few kB of
3034	code.
3035
3036	=item EV_EMBED_ENABLE
3037
3038	If undefined or defined to be C<1>, then embed watchers are supported. If
3039	defined to be C<0>, then they are not.
3040
3041	=item EV_STAT_ENABLE
3042
3043	If undefined or defined to be C<1>, then stat watchers are supported. If
3044	defined to be C<0>, then they are not.
3045
3046	=item EV_FORK_ENABLE
3047
3048	If undefined or defined to be C<1>, then fork watchers are supported. If
3049	defined to be C<0>, then they are not.
3050
3051	=item EV_ASYNC_ENABLE
3052
3053	If undefined or defined to be C<1>, then async watchers are supported. If
3054	defined to be C<0>, then they are not.
3055
3056	=item EV_MINIMAL
3057		4071
3058	If you need to shave off some kilobytes of code at the expense of some	4072	If you need to shave off some kilobytes of code at the expense of some
3059	speed, define this symbol to C<1>. Currently this is used to override some	4073	speed (but with the full API), you can define this symbol to request
3060	inlining decisions, saves roughly 30% code size on amd64. It also selects a	4074	certain subsets of functionality. The default is to enable all features
3061	much smaller 2-heap for timer management over the default 4-heap.	4075	that can be enabled on the platform.
		4076
		4077	A typical way to use this symbol is to define it to C<0> (or to a bitset
		4078	with some broad features you want) and then selectively re-enable
		4079	additional parts you want, for example if you want everything minimal,
		4080	but multiple event loop support, async and child watchers and the poll
		4081	backend, use this:
		4082
		4083	#define EV_FEATURES 0
		4084	#define EV_MULTIPLICITY 1
		4085	#define EV_USE_POLL 1
		4086	#define EV_CHILD_ENABLE 1
		4087	#define EV_ASYNC_ENABLE 1
		4088
		4089	The actual value is a bitset, it can be a combination of the following
		4090	values:
		4091
		4092	=over 4
		4093
		4094	=item C<1> - faster/larger code
		4095
		4096	Use larger code to speed up some operations.
		4097
		4098	Currently this is used to override some inlining decisions (enlarging the
		4099	code size by roughly 30% on amd64).
		4100
		4101	When optimising for size, use of compiler flags such as C<-Os> with
		4102	gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of
		4103	assertions.
		4104
		4105	=item C<2> - faster/larger data structures
		4106
		4107	Replaces the small 2-heap for timer management by a faster 4-heap, larger
		4108	hash table sizes and so on. This will usually further increase code size
		4109	and can additionally have an effect on the size of data structures at
		4110	runtime.
		4111
		4112	=item C<4> - full API configuration
		4113
		4114	This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and
		4115	enables multiplicity (C<EV_MULTIPLICITY>=1).
		4116
		4117	=item C<8> - full API
		4118
		4119	This enables a lot of the "lesser used" API functions. See C<ev.h> for
		4120	details on which parts of the API are still available without this
		4121	feature, and do not complain if this subset changes over time.
		4122
		4123	=item C<16> - enable all optional watcher types
		4124
		4125	Enables all optional watcher types. If you want to selectively enable
		4126	only some watcher types other than I/O and timers (e.g. prepare,
		4127	embed, async, child...) you can enable them manually by defining
		4128	C<EV_watchertype_ENABLE> to C<1> instead.
		4129
		4130	=item C<32> - enable all backends
		4131
		4132	This enables all backends - without this feature, you need to enable at
		4133	least one backend manually (C<EV_USE_SELECT> is a good choice).
		4134
		4135	=item C<64> - enable OS-specific "helper" APIs
		4136
		4137	Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by
		4138	default.
		4139
		4140	=back
		4141
		4142	Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0>
		4143	reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb
		4144	code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O
		4145	watchers, timers and monotonic clock support.
		4146
		4147	With an intelligent-enough linker (gcc+binutils are intelligent enough
		4148	when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by
		4149	your program might be left out as well - a binary starting a timer and an
		4150	I/O watcher then might come out at only 5Kb.
		4151
		4152	=item EV_AVOID_STDIO
		4153
		4154	If this is set to C<1> at compiletime, then libev will avoid using stdio
		4155	functions (printf, scanf, perror etc.). This will increase the code size
		4156	somewhat, but if your program doesn't otherwise depend on stdio and your
		4157	libc allows it, this avoids linking in the stdio library which is quite
		4158	big.
		4159
		4160	Note that error messages might become less precise when this option is
		4161	enabled.
		4162
		4163	=item EV_NSIG
		4164
		4165	The highest supported signal number, +1 (or, the number of
		4166	signals): Normally, libev tries to deduce the maximum number of signals
		4167	automatically, but sometimes this fails, in which case it can be
		4168	specified. Also, using a lower number than detected (C<32> should be
		4169	good for about any system in existence) can save some memory, as libev
		4170	statically allocates some 12-24 bytes per signal number.
3062		4171
3063	=item EV_PID_HASHSIZE	4172	=item EV_PID_HASHSIZE
3064		4173
3065	C<ev_child> watchers use a small hash table to distribute workload by	4174	C<ev_child> watchers use a small hash table to distribute workload by
3066	pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more	4175	pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled),
3067	than enough. If you need to manage thousands of children you might want to	4176	usually more than enough. If you need to manage thousands of children you
3068	increase this value (I<must> be a power of two).	4177	might want to increase this value (I<must> be a power of two).
3069		4178
3070	=item EV_INOTIFY_HASHSIZE	4179	=item EV_INOTIFY_HASHSIZE
3071		4180
3072	C<ev_stat> watchers use a small hash table to distribute workload by	4181	C<ev_stat> watchers use a small hash table to distribute workload by
3073	inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>),	4182	inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES>
3074	usually more than enough. If you need to manage thousands of C<ev_stat>	4183	disabled), usually more than enough. If you need to manage thousands of
3075	watchers you might want to increase this value (I<must> be a power of	4184	C<ev_stat> watchers you might want to increase this value (I<must> be a
3076	two).	4185	power of two).
3077		4186
3078	=item EV_USE_4HEAP	4187	=item EV_USE_4HEAP
3079		4188
3080	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4189	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3081	timer and periodics heap, libev uses a 4-heap when this symbol is defined	4190	timer and periodics heaps, libev uses a 4-heap when this symbol is defined
3082	to C<1>. The 4-heap uses more complicated (longer) code but has	4191	to C<1>. The 4-heap uses more complicated (longer) code but has noticeably
3083	noticeably faster performance with many (thousands) of watchers.	4192	faster performance with many (thousands) of watchers.
3084		4193
3085	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4194	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3086	(disabled).	4195	will be C<0>.
3087		4196
3088	=item EV_HEAP_CACHE_AT	4197	=item EV_HEAP_CACHE_AT
3089		4198
3090	Heaps are not very cache-efficient. To improve the cache-efficiency of the	4199	Heaps are not very cache-efficient. To improve the cache-efficiency of the
3091	timer and periodics heap, libev can cache the timestamp (I<at>) within	4200	timer and periodics heaps, libev can cache the timestamp (I<at>) within
3092	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),	4201	the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>),
3093	which uses 8-12 bytes more per watcher and a few hundred bytes more code,	4202	which uses 8-12 bytes more per watcher and a few hundred bytes more code,
3094	but avoids random read accesses on heap changes. This improves performance	4203	but avoids random read accesses on heap changes. This improves performance
3095	noticeably with with many (hundreds) of watchers.	4204	noticeably with many (hundreds) of watchers.
3096		4205
3097	The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0>	4206	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3098	(disabled).	4207	will be C<0>.
3099		4208
3100	=item EV_VERIFY	4209	=item EV_VERIFY
3101		4210
3102	Controls how much internal verification (see C<ev_loop_verify ()>) will	4211	Controls how much internal verification (see C<ev_verify ()>) will
3103	be done: If set to C<0>, no internal verification code will be compiled	4212	be done: If set to C<0>, no internal verification code will be compiled
3104	in. If set to C<1>, then verification code will be compiled in, but not	4213	in. If set to C<1>, then verification code will be compiled in, but not
3105	called. If set to C<2>, then the internal verification code will be	4214	called. If set to C<2>, then the internal verification code will be
3106	called once per loop, which can slow down libev. If set to C<3>, then the	4215	called once per loop, which can slow down libev. If set to C<3>, then the
3107	verification code will be called very frequently, which will slow down	4216	verification code will be called very frequently, which will slow down
3108	libev considerably.	4217	libev considerably.
3109		4218
3110	The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be	4219	The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it
3111	C<0.>	4220	will be C<0>.
3112		4221
3113	=item EV_COMMON	4222	=item EV_COMMON
3114		4223
3115	By default, all watchers have a C<void *data> member. By redefining	4224	By default, all watchers have a C<void *data> member. By redefining
3116	this macro to a something else you can include more and other types of	4225	this macro to something else you can include more and other types of
3117	members. You have to define it each time you include one of the files,	4226	members. You have to define it each time you include one of the files,
3118	though, and it must be identical each time.	4227	though, and it must be identical each time.
3119		4228
3120	For example, the perl EV module uses something like this:	4229	For example, the perl EV module uses something like this:
3121		4230
…		…
3133	and the way callbacks are invoked and set. Must expand to a struct member	4242	and the way callbacks are invoked and set. Must expand to a struct member
3134	definition and a statement, respectively. See the F<ev.h> header file for	4243	definition and a statement, respectively. See the F<ev.h> header file for
3135	their default definitions. One possible use for overriding these is to	4244	their default definitions. One possible use for overriding these is to
3136	avoid the C<struct ev_loop *> as first argument in all cases, or to use	4245	avoid the C<struct ev_loop *> as first argument in all cases, or to use
3137	method calls instead of plain function calls in C++.	4246	method calls instead of plain function calls in C++.
		4247
		4248	=back
3138		4249
3139	=head2 EXPORTED API SYMBOLS	4250	=head2 EXPORTED API SYMBOLS
3140		4251
3141	If you need to re-export the API (e.g. via a DLL) and you need a list of	4252	If you need to re-export the API (e.g. via a DLL) and you need a list of
3142	exported symbols, you can use the provided F<Symbol.*> files which list	4253	exported symbols, you can use the provided F<Symbol.*> files which list
…		…
3172	file.	4283	file.
3173		4284
3174	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file	4285	The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
3175	that everybody includes and which overrides some configure choices:	4286	that everybody includes and which overrides some configure choices:
3176		4287
3177	#define EV_MINIMAL 1	4288	#define EV_FEATURES 8
3178	#define EV_USE_POLL 0	4289	#define EV_USE_SELECT 1
3179	#define EV_MULTIPLICITY 0
3180	#define EV_PERIODIC_ENABLE 0	4290	#define EV_PREPARE_ENABLE 1
		4291	#define EV_IDLE_ENABLE 1
3181	#define EV_STAT_ENABLE 0	4292	#define EV_SIGNAL_ENABLE 1
3182	#define EV_FORK_ENABLE 0	4293	#define EV_CHILD_ENABLE 1
		4294	#define EV_USE_STDEXCEPT 0
3183	#define EV_CONFIG_H <config.h>	4295	#define EV_CONFIG_H <config.h>
3184	#define EV_MINPRI 0
3185	#define EV_MAXPRI 0
3186		4296
3187	#include "ev++.h"	4297	#include "ev++.h"
3188		4298
3189	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:	4299	And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:
3190		4300
3191	#include "ev_cpp.h"	4301	#include "ev_cpp.h"
3192	#include "ev.c"	4302	#include "ev.c"
3193		4303
		4304	=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES
3194		4305
3195	=head1 THREADS AND COROUTINES	4306	=head2 THREADS AND COROUTINES
3196		4307
3197	=head2 THREADS	4308	=head3 THREADS
3198		4309
3199	Libev itself is completely thread-safe, but it uses no locking. This	4310	All libev functions are reentrant and thread-safe unless explicitly
		4311	documented otherwise, but libev implements no locking itself. This means
3200	means that you can use as many loops as you want in parallel, as long as	4312	that you can use as many loops as you want in parallel, as long as there
3201	only one thread ever calls into one libev function with the same loop	4313	are no concurrent calls into any libev function with the same loop
3202	parameter.	4314	parameter (C<ev_default_*> calls have an implicit default loop parameter,
		4315	of course): libev guarantees that different event loops share no data
		4316	structures that need any locking.
3203		4317
3204	Or put differently: calls with different loop parameters can be done in	4318	Or to put it differently: calls with different loop parameters can be done
3205	parallel from multiple threads, calls with the same loop parameter must be	4319	concurrently from multiple threads, calls with the same loop parameter
3206	done serially (but can be done from different threads, as long as only one	4320	must be done serially (but can be done from different threads, as long as
3207	thread ever is inside a call at any point in time, e.g. by using a mutex	4321	only one thread ever is inside a call at any point in time, e.g. by using
3208	per loop).	4322	a mutex per loop).
		4323
		4324	Specifically to support threads (and signal handlers), libev implements
		4325	so-called C<ev_async> watchers, which allow some limited form of
		4326	concurrency on the same event loop, namely waking it up "from the
		4327	outside".
3209		4328
3210	If you want to know which design (one loop, locking, or multiple loops	4329	If you want to know which design (one loop, locking, or multiple loops
3211	without or something else still) is best for your problem, then I cannot	4330	without or something else still) is best for your problem, then I cannot
3212	help you. I can give some generic advice however:	4331	help you, but here is some generic advice:
3213		4332
3214	=over 4	4333	=over 4
3215		4334
3216	=item * most applications have a main thread: use the default libev loop	4335	=item * most applications have a main thread: use the default libev loop
3217	in that thread, or create a separate thread running only the default loop.	4336	in that thread, or create a separate thread running only the default loop.
…		…
3229		4348
3230	Choosing a model is hard - look around, learn, know that usually you can do	4349	Choosing a model is hard - look around, learn, know that usually you can do
3231	better than you currently do :-)	4350	better than you currently do :-)
3232		4351
3233	=item * often you need to talk to some other thread which blocks in the	4352	=item * often you need to talk to some other thread which blocks in the
		4353	event loop.
		4354
3234	event loop - C<ev_async> watchers can be used to wake them up from other	4355	C<ev_async> watchers can be used to wake them up from other threads safely
3235	threads safely (or from signal contexts...).	4356	(or from signal contexts...).
		4357
		4358	An example use would be to communicate signals or other events that only
		4359	work in the default loop by registering the signal watcher with the
		4360	default loop and triggering an C<ev_async> watcher from the default loop
		4361	watcher callback into the event loop interested in the signal.
3236		4362
3237	=back	4363	=back
3238		4364
		4365	=head4 THREAD LOCKING EXAMPLE
		4366
		4367	Here is a fictitious example of how to run an event loop in a different
		4368	thread than where callbacks are being invoked and watchers are
		4369	created/added/removed.
		4370
		4371	For a real-world example, see the C<EV::Loop::Async> perl module,
		4372	which uses exactly this technique (which is suited for many high-level
		4373	languages).
		4374
		4375	The example uses a pthread mutex to protect the loop data, a condition
		4376	variable to wait for callback invocations, an async watcher to notify the
		4377	event loop thread and an unspecified mechanism to wake up the main thread.
		4378
		4379	First, you need to associate some data with the event loop:
		4380
		4381	typedef struct {
		4382	mutex_t lock; /* global loop lock */
		4383	ev_async async_w;
		4384	thread_t tid;
		4385	cond_t invoke_cv;
		4386	} userdata;
		4387
		4388	void prepare_loop (EV_P)
		4389	{
		4390	// for simplicity, we use a static userdata struct.
		4391	static userdata u;
		4392
		4393	ev_async_init (&u->async_w, async_cb);
		4394	ev_async_start (EV_A_ &u->async_w);
		4395
		4396	pthread_mutex_init (&u->lock, 0);
		4397	pthread_cond_init (&u->invoke_cv, 0);
		4398
		4399	// now associate this with the loop
		4400	ev_set_userdata (EV_A_ u);
		4401	ev_set_invoke_pending_cb (EV_A_ l_invoke);
		4402	ev_set_loop_release_cb (EV_A_ l_release, l_acquire);
		4403
		4404	// then create the thread running ev_loop
		4405	pthread_create (&u->tid, 0, l_run, EV_A);
		4406	}
		4407
		4408	The callback for the C<ev_async> watcher does nothing: the watcher is used
		4409	solely to wake up the event loop so it takes notice of any new watchers
		4410	that might have been added:
		4411
		4412	static void
		4413	async_cb (EV_P_ ev_async *w, int revents)
		4414	{
		4415	// just used for the side effects
		4416	}
		4417
		4418	The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex
		4419	protecting the loop data, respectively.
		4420
		4421	static void
		4422	l_release (EV_P)
		4423	{
		4424	userdata *u = ev_userdata (EV_A);
		4425	pthread_mutex_unlock (&u->lock);
		4426	}
		4427
		4428	static void
		4429	l_acquire (EV_P)
		4430	{
		4431	userdata *u = ev_userdata (EV_A);
		4432	pthread_mutex_lock (&u->lock);
		4433	}
		4434
		4435	The event loop thread first acquires the mutex, and then jumps straight
		4436	into C<ev_run>:
		4437
		4438	void *
		4439	l_run (void *thr_arg)
		4440	{
		4441	struct ev_loop *loop = (struct ev_loop *)thr_arg;
		4442
		4443	l_acquire (EV_A);
		4444	pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0);
		4445	ev_run (EV_A_ 0);
		4446	l_release (EV_A);
		4447
		4448	return 0;
		4449	}
		4450
		4451	Instead of invoking all pending watchers, the C<l_invoke> callback will
		4452	signal the main thread via some unspecified mechanism (signals? pipe
		4453	writes? C<Async::Interrupt>?) and then waits until all pending watchers
		4454	have been called (in a while loop because a) spurious wakeups are possible
		4455	and b) skipping inter-thread-communication when there are no pending
		4456	watchers is very beneficial):
		4457
		4458	static void
		4459	l_invoke (EV_P)
		4460	{
		4461	userdata *u = ev_userdata (EV_A);
		4462
		4463	while (ev_pending_count (EV_A))
		4464	{
		4465	wake_up_other_thread_in_some_magic_or_not_so_magic_way ();
		4466	pthread_cond_wait (&u->invoke_cv, &u->lock);
		4467	}
		4468	}
		4469
		4470	Now, whenever the main thread gets told to invoke pending watchers, it
		4471	will grab the lock, call C<ev_invoke_pending> and then signal the loop
		4472	thread to continue:
		4473
		4474	static void
		4475	real_invoke_pending (EV_P)
		4476	{
		4477	userdata *u = ev_userdata (EV_A);
		4478
		4479	pthread_mutex_lock (&u->lock);
		4480	ev_invoke_pending (EV_A);
		4481	pthread_cond_signal (&u->invoke_cv);
		4482	pthread_mutex_unlock (&u->lock);
		4483	}
		4484
		4485	Whenever you want to start/stop a watcher or do other modifications to an
		4486	event loop, you will now have to lock:
		4487
		4488	ev_timer timeout_watcher;
		4489	userdata *u = ev_userdata (EV_A);
		4490
		4491	ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
		4492
		4493	pthread_mutex_lock (&u->lock);
		4494	ev_timer_start (EV_A_ &timeout_watcher);
		4495	ev_async_send (EV_A_ &u->async_w);
		4496	pthread_mutex_unlock (&u->lock);
		4497
		4498	Note that sending the C<ev_async> watcher is required because otherwise
		4499	an event loop currently blocking in the kernel will have no knowledge
		4500	about the newly added timer. By waking up the loop it will pick up any new
		4501	watchers in the next event loop iteration.
		4502
3239	=head2 COROUTINES	4503	=head3 COROUTINES
3240		4504
3241	Libev is much more accommodating to coroutines ("cooperative threads"):	4505	Libev is very accommodating to coroutines ("cooperative threads"):
3242	libev fully supports nesting calls to it's functions from different	4506	libev fully supports nesting calls to its functions from different
3243	coroutines (e.g. you can call C<ev_loop> on the same loop from two	4507	coroutines (e.g. you can call C<ev_run> on the same loop from two
3244	different coroutines and switch freely between both coroutines running the	4508	different coroutines, and switch freely between both coroutines running
3245	loop, as long as you don't confuse yourself). The only exception is that	4509	the loop, as long as you don't confuse yourself). The only exception is
3246	you must not do this from C<ev_periodic> reschedule callbacks.	4510	that you must not do this from C<ev_periodic> reschedule callbacks.
3247		4511
3248	Care has been invested into making sure that libev does not keep local	4512	Care has been taken to ensure that libev does not keep local state inside
3249	state inside C<ev_loop>, and other calls do not usually allow coroutine	4513	C<ev_run>, and other calls do not usually allow for coroutine switches as
3250	switches.	4514	they do not call any callbacks.
3251		4515
		4516	=head2 COMPILER WARNINGS
3252		4517
3253	=head1 COMPLEXITIES	4518	Depending on your compiler and compiler settings, you might get no or a
		4519	lot of warnings when compiling libev code. Some people are apparently
		4520	scared by this.
3254		4521
3255	In this section the complexities of (many of) the algorithms used inside	4522	However, these are unavoidable for many reasons. For one, each compiler
3256	libev will be explained. For complexity discussions about backends see the	4523	has different warnings, and each user has different tastes regarding
3257	documentation for C<ev_default_init>.	4524	warning options. "Warn-free" code therefore cannot be a goal except when
		4525	targeting a specific compiler and compiler-version.
3258		4526
3259	All of the following are about amortised time: If an array needs to be	4527	Another reason is that some compiler warnings require elaborate
3260	extended, libev needs to realloc and move the whole array, but this	4528	workarounds, or other changes to the code that make it less clear and less
3261	happens asymptotically never with higher number of elements, so O(1) might	4529	maintainable.
3262	mean it might do a lengthy realloc operation in rare cases, but on average
3263	it is much faster and asymptotically approaches constant time.
3264		4530
3265	=over 4	4531	And of course, some compiler warnings are just plain stupid, or simply
		4532	wrong (because they don't actually warn about the condition their message
		4533	seems to warn about). For example, certain older gcc versions had some
		4534	warnings that resulted in an extreme number of false positives. These have
		4535	been fixed, but some people still insist on making code warn-free with
		4536	such buggy versions.
3266		4537
3267	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)	4538	While libev is written to generate as few warnings as possible,
		4539	"warn-free" code is not a goal, and it is recommended not to build libev
		4540	with any compiler warnings enabled unless you are prepared to cope with
		4541	them (e.g. by ignoring them). Remember that warnings are just that:
		4542	warnings, not errors, or proof of bugs.
3268		4543
3269	This means that, when you have a watcher that triggers in one hour and
3270	there are 100 watchers that would trigger before that then inserting will
3271	have to skip roughly seven (C<ld 100>) of these watchers.
3272		4544
3273	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)	4545	=head2 VALGRIND
3274		4546
3275	That means that changing a timer costs less than removing/adding them	4547	Valgrind has a special section here because it is a popular tool that is
3276	as only the relative motion in the event queue has to be paid for.	4548	highly useful. Unfortunately, valgrind reports are very hard to interpret.
3277		4549
3278	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)	4550	If you think you found a bug (memory leak, uninitialised data access etc.)
		4551	in libev, then check twice: If valgrind reports something like:
3279		4552
3280	These just add the watcher into an array or at the head of a list.	4553	==2274== definitely lost: 0 bytes in 0 blocks.
		4554	==2274== possibly lost: 0 bytes in 0 blocks.
		4555	==2274== still reachable: 256 bytes in 1 blocks.
3281		4556
3282	=item Stopping check/prepare/idle/fork/async watchers: O(1)	4557	Then there is no memory leak, just as memory accounted to global variables
		4558	is not a memleak - the memory is still being referenced, and didn't leak.
3283		4559
3284	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))	4560	Similarly, under some circumstances, valgrind might report kernel bugs
		4561	as if it were a bug in libev (e.g. in realloc or in the poll backend,
		4562	although an acceptable workaround has been found here), or it might be
		4563	confused.
3285		4564
3286	These watchers are stored in lists then need to be walked to find the	4565	Keep in mind that valgrind is a very good tool, but only a tool. Don't
3287	correct watcher to remove. The lists are usually short (you don't usually	4566	make it into some kind of religion.
3288	have many watchers waiting for the same fd or signal).
3289		4567
3290	=item Finding the next timer in each loop iteration: O(1)	4568	If you are unsure about something, feel free to contact the mailing list
		4569	with the full valgrind report and an explanation on why you think this
		4570	is a bug in libev (best check the archives, too :). However, don't be
		4571	annoyed when you get a brisk "this is no bug" answer and take the chance
		4572	of learning how to interpret valgrind properly.
3291		4573
3292	By virtue of using a binary or 4-heap, the next timer is always found at a	4574	If you need, for some reason, empty reports from valgrind for your project
3293	fixed position in the storage array.	4575	I suggest using suppression lists.
3294		4576
3295	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
3296		4577
3297	A change means an I/O watcher gets started or stopped, which requires	4578	=head1 PORTABILITY NOTES
3298	libev to recalculate its status (and possibly tell the kernel, depending
3299	on backend and whether C<ev_io_set> was used).
3300		4579
3301	=item Activating one watcher (putting it into the pending state): O(1)	4580	=head2 GNU/LINUX 32 BIT LIMITATIONS
3302		4581
3303	=item Priority handling: O(number_of_priorities)	4582	GNU/Linux is the only common platform that supports 64 bit file/large file
		4583	interfaces but I<disables> them by default.
3304		4584
3305	Priorities are implemented by allocating some space for each	4585	That means that libev compiled in the default environment doesn't support
3306	priority. When doing priority-based operations, libev usually has to	4586	files larger than 2GiB or so, which mainly affects C<ev_stat> watchers.
3307	linearly search all the priorities, but starting/stopping and activating
3308	watchers becomes O(1) w.r.t. priority handling.
3309		4587
3310	=item Sending an ev_async: O(1)	4588	Unfortunately, many programs try to work around this GNU/Linux issue
		4589	by enabling the large file API, which makes them incompatible with the
		4590	standard libev compiled for their system.
3311		4591
3312	=item Processing ev_async_send: O(number_of_async_watchers)	4592	Likewise, libev cannot enable the large file API itself as this would
		4593	suddenly make it incompatible to the default compile time environment,
		4594	i.e. all programs not using special compile switches.
3313		4595
3314	=item Processing signals: O(max_signal_number)	4596	=head2 OS/X AND DARWIN BUGS
3315		4597
3316	Sending involves a system call I<iff> there were no other C<ev_async_send>	4598	The whole thing is a bug if you ask me - basically any system interface
3317	calls in the current loop iteration. Checking for async and signal events	4599	you touch is broken, whether it is locales, poll, kqueue or even the
3318	involves iterating over all running async watchers or all signal numbers.	4600	OpenGL drivers.
3319		4601
3320	=back	4602	=head3 C<kqueue> is buggy
3321		4603
		4604	The kqueue syscall is broken in all known versions - most versions support
		4605	only sockets, many support pipes.
3322		4606
		4607	Libev tries to work around this by not using C<kqueue> by default on this
		4608	rotten platform, but of course you can still ask for it when creating a
		4609	loop - embedding a socket-only kqueue loop into a select-based one is
		4610	probably going to work well.
		4611
		4612	=head3 C<poll> is buggy
		4613
		4614	Instead of fixing C<kqueue>, Apple replaced their (working) C<poll>
		4615	implementation by something calling C<kqueue> internally around the 10.5.6
		4616	release, so now C<kqueue> I<and> C<poll> are broken.
		4617
		4618	Libev tries to work around this by not using C<poll> by default on
		4619	this rotten platform, but of course you can still ask for it when creating
		4620	a loop.
		4621
		4622	=head3 C<select> is buggy
		4623
		4624	All that's left is C<select>, and of course Apple found a way to fuck this
		4625	one up as well: On OS/X, C<select> actively limits the number of file
		4626	descriptors you can pass in to 1024 - your program suddenly crashes when
		4627	you use more.
		4628
		4629	There is an undocumented "workaround" for this - defining
		4630	C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should>
		4631	work on OS/X.
		4632
		4633	=head2 SOLARIS PROBLEMS AND WORKAROUNDS
		4634
		4635	=head3 C<errno> reentrancy
		4636
		4637	The default compile environment on Solaris is unfortunately so
		4638	thread-unsafe that you can't even use components/libraries compiled
		4639	without C<-D_REENTRANT> in a threaded program, which, of course, isn't
		4640	defined by default. A valid, if stupid, implementation choice.
		4641
		4642	If you want to use libev in threaded environments you have to make sure
		4643	it's compiled with C<_REENTRANT> defined.
		4644
		4645	=head3 Event port backend
		4646
		4647	The scalable event interface for Solaris is called "event
		4648	ports". Unfortunately, this mechanism is very buggy in all major
		4649	releases. If you run into high CPU usage, your program freezes or you get
		4650	a large number of spurious wakeups, make sure you have all the relevant
		4651	and latest kernel patches applied. No, I don't know which ones, but there
		4652	are multiple ones to apply, and afterwards, event ports actually work
		4653	great.
		4654
		4655	If you can't get it to work, you can try running the program by setting
		4656	the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and
		4657	C<select> backends.
		4658
		4659	=head2 AIX POLL BUG
		4660
		4661	AIX unfortunately has a broken C<poll.h> header. Libev works around
		4662	this by trying to avoid the poll backend altogether (i.e. it's not even
		4663	compiled in), which normally isn't a big problem as C<select> works fine
		4664	with large bitsets on AIX, and AIX is dead anyway.
		4665
3323	=head1 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS	4666	=head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS
		4667
		4668	=head3 General issues
3324		4669
3325	Win32 doesn't support any of the standards (e.g. POSIX) that libev	4670	Win32 doesn't support any of the standards (e.g. POSIX) that libev
3326	requires, and its I/O model is fundamentally incompatible with the POSIX	4671	requires, and its I/O model is fundamentally incompatible with the POSIX
3327	model. Libev still offers limited functionality on this platform in	4672	model. Libev still offers limited functionality on this platform in
3328	the form of the C<EVBACKEND_SELECT> backend, and only supports socket	4673	the form of the C<EVBACKEND_SELECT> backend, and only supports socket
3329	descriptors. This only applies when using Win32 natively, not when using	4674	descriptors. This only applies when using Win32 natively, not when using
3330	e.g. cygwin.	4675	e.g. cygwin. Actually, it only applies to the microsofts own compilers,
		4676	as every compielr comes with a slightly differently broken/incompatible
		4677	environment.
3331		4678
3332	Lifting these limitations would basically require the full	4679	Lifting these limitations would basically require the full
3333	re-implementation of the I/O system. If you are into these kinds of	4680	re-implementation of the I/O system. If you are into this kind of thing,
3334	things, then note that glib does exactly that for you in a very portable	4681	then note that glib does exactly that for you in a very portable way (note
3335	way (note also that glib is the slowest event library known to man).	4682	also that glib is the slowest event library known to man).
3336		4683
3337	There is no supported compilation method available on windows except	4684	There is no supported compilation method available on windows except
3338	embedding it into other applications.	4685	embedding it into other applications.
		4686
		4687	Sensible signal handling is officially unsupported by Microsoft - libev
		4688	tries its best, but under most conditions, signals will simply not work.
3339		4689
3340	Not a libev limitation but worth mentioning: windows apparently doesn't	4690	Not a libev limitation but worth mentioning: windows apparently doesn't
3341	accept large writes: instead of resulting in a partial write, windows will	4691	accept large writes: instead of resulting in a partial write, windows will
3342	either accept everything or return C<ENOBUFS> if the buffer is too large,	4692	either accept everything or return C<ENOBUFS> if the buffer is too large,
3343	so make sure you only write small amounts into your sockets (less than a	4693	so make sure you only write small amounts into your sockets (less than a
3344	megabyte seems safe, but thsi apparently depends on the amount of memory	4694	megabyte seems safe, but this apparently depends on the amount of memory
3345	available).	4695	available).
3346		4696
3347	Due to the many, low, and arbitrary limits on the win32 platform and	4697	Due to the many, low, and arbitrary limits on the win32 platform and
3348	the abysmal performance of winsockets, using a large number of sockets	4698	the abysmal performance of winsockets, using a large number of sockets
3349	is not recommended (and not reasonable). If your program needs to use	4699	is not recommended (and not reasonable). If your program needs to use
3350	more than a hundred or so sockets, then likely it needs to use a totally	4700	more than a hundred or so sockets, then likely it needs to use a totally
3351	different implementation for windows, as libev offers the POSIX readiness	4701	different implementation for windows, as libev offers the POSIX readiness
3352	notification model, which cannot be implemented efficiently on windows	4702	notification model, which cannot be implemented efficiently on windows
3353	(Microsoft monopoly games).	4703	(due to Microsoft monopoly games).
3354		4704
3355	A typical way to use libev under windows is to embed it (see the embedding	4705	A typical way to use libev under windows is to embed it (see the embedding
3356	section for details) and use the following F<evwrap.h> header file instead	4706	section for details) and use the following F<evwrap.h> header file instead
3357	of F<ev.h>:	4707	of F<ev.h>:
3358		4708
…		…
3360	#define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */	4710	#define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */
3361		4711
3362	#include "ev.h"	4712	#include "ev.h"
3363		4713
3364	And compile the following F<evwrap.c> file into your project (make sure	4714	And compile the following F<evwrap.c> file into your project (make sure
3365	you do I<not> compile the F<ev.c> or any other embedded soruce files!):	4715	you do I<not> compile the F<ev.c> or any other embedded source files!):
3366		4716
3367	#include "evwrap.h"	4717	#include "evwrap.h"
3368	#include "ev.c"	4718	#include "ev.c"
3369		4719
3370	=over 4
3371
3372	=item The winsocket select function	4720	=head3 The winsocket C<select> function
3373		4721
3374	The winsocket C<select> function doesn't follow POSIX in that it	4722	The winsocket C<select> function doesn't follow POSIX in that it
3375	requires socket I<handles> and not socket I<file descriptors> (it is	4723	requires socket I<handles> and not socket I<file descriptors> (it is
3376	also extremely buggy). This makes select very inefficient, and also	4724	also extremely buggy). This makes select very inefficient, and also
3377	requires a mapping from file descriptors to socket handles (the Microsoft	4725	requires a mapping from file descriptors to socket handles (the Microsoft
…		…
3386	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */	4734	#define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
3387		4735
3388	Note that winsockets handling of fd sets is O(n), so you can easily get a	4736	Note that winsockets handling of fd sets is O(n), so you can easily get a
3389	complexity in the O(n²) range when using win32.	4737	complexity in the O(n²) range when using win32.
3390		4738
3391	=item Limited number of file descriptors	4739	=head3 Limited number of file descriptors
3392		4740
3393	Windows has numerous arbitrary (and low) limits on things.	4741	Windows has numerous arbitrary (and low) limits on things.
3394		4742
3395	Early versions of winsocket's select only supported waiting for a maximum	4743	Early versions of winsocket's select only supported waiting for a maximum
3396	of C<64> handles (probably owning to the fact that all windows kernels	4744	of C<64> handles (probably owning to the fact that all windows kernels
3397	can only wait for C<64> things at the same time internally; Microsoft	4745	can only wait for C<64> things at the same time internally; Microsoft
3398	recommends spawning a chain of threads and wait for 63 handles and the	4746	recommends spawning a chain of threads and wait for 63 handles and the
3399	previous thread in each. Great).	4747	previous thread in each. Sounds great!).
3400		4748
3401	Newer versions support more handles, but you need to define C<FD_SETSIZE>	4749	Newer versions support more handles, but you need to define C<FD_SETSIZE>
3402	to some high number (e.g. C<2048>) before compiling the winsocket select	4750	to some high number (e.g. C<2048>) before compiling the winsocket select
3403	call (which might be in libev or elsewhere, for example, perl does its own	4751	call (which might be in libev or elsewhere, for example, perl and many
3404	select emulation on windows).	4752	other interpreters do their own select emulation on windows).
3405		4753
3406	Another limit is the number of file descriptors in the Microsoft runtime	4754	Another limit is the number of file descriptors in the Microsoft runtime
3407	libraries, which by default is C<64> (there must be a hidden I<64> fetish	4755	libraries, which by default is C<64> (there must be a hidden I<64>
3408	or something like this inside Microsoft). You can increase this by calling	4756	fetish or something like this inside Microsoft). You can increase this
3409	C<_setmaxstdio>, which can increase this limit to C<2048> (another	4757	by calling C<_setmaxstdio>, which can increase this limit to C<2048>
3410	arbitrary limit), but is broken in many versions of the Microsoft runtime	4758	(another arbitrary limit), but is broken in many versions of the Microsoft
3411	libraries.
3412
3413	This might get you to about C<512> or C<2048> sockets (depending on	4759	runtime libraries. This might get you to about C<512> or C<2048> sockets
3414	windows version and/or the phase of the moon). To get more, you need to	4760	(depending on windows version and/or the phase of the moon). To get more,
3415	wrap all I/O functions and provide your own fd management, but the cost of	4761	you need to wrap all I/O functions and provide your own fd management, but
3416	calling select (O(n²)) will likely make this unworkable.	4762	the cost of calling select (O(n²)) will likely make this unworkable.
3417		4763
3418	=back
3419
3420
3421	=head1 PORTABILITY REQUIREMENTS	4764	=head2 PORTABILITY REQUIREMENTS
3422		4765
3423	In addition to a working ISO-C implementation, libev relies on a few	4766	In addition to a working ISO-C implementation and of course the
3424	additional extensions:	4767	backend-specific APIs, libev relies on a few additional extensions:
3425		4768
3426	=over 4	4769	=over 4
3427		4770
3428	=item C<void (*)(ev_watcher_type *, int revents)> must have compatible	4771	=item C<void (*)(ev_watcher_type *, int revents)> must have compatible
3429	calling conventions regardless of C<ev_watcher_type *>.	4772	calling conventions regardless of C<ev_watcher_type *>.
…		…
3432	structure (guaranteed by POSIX but not by ISO C for example), but it also	4775	structure (guaranteed by POSIX but not by ISO C for example), but it also
3433	assumes that the same (machine) code can be used to call any watcher	4776	assumes that the same (machine) code can be used to call any watcher
3434	callback: The watcher callbacks have different type signatures, but libev	4777	callback: The watcher callbacks have different type signatures, but libev
3435	calls them using an C<ev_watcher *> internally.	4778	calls them using an C<ev_watcher *> internally.
3436		4779
		4780	=item pointer accesses must be thread-atomic
		4781
		4782	Accessing a pointer value must be atomic, it must both be readable and
		4783	writable in one piece - this is the case on all current architectures.
		4784
3437	=item C<sig_atomic_t volatile> must be thread-atomic as well	4785	=item C<sig_atomic_t volatile> must be thread-atomic as well
3438		4786
3439	The type C<sig_atomic_t volatile> (or whatever is defined as	4787	The type C<sig_atomic_t volatile> (or whatever is defined as
3440	C<EV_ATOMIC_T>) must be atomic w.r.t. accesses from different	4788	C<EV_ATOMIC_T>) must be atomic with respect to accesses from different
3441	threads. This is not part of the specification for C<sig_atomic_t>, but is	4789	threads. This is not part of the specification for C<sig_atomic_t>, but is
3442	believed to be sufficiently portable.	4790	believed to be sufficiently portable.
3443		4791
3444	=item C<sigprocmask> must work in a threaded environment	4792	=item C<sigprocmask> must work in a threaded environment
3445		4793
…		…
3454	except the initial one, and run the default loop in the initial thread as	4802	except the initial one, and run the default loop in the initial thread as
3455	well.	4803	well.
3456		4804
3457	=item C<long> must be large enough for common memory allocation sizes	4805	=item C<long> must be large enough for common memory allocation sizes
3458		4806
3459	To improve portability and simplify using libev, libev uses C<long>	4807	To improve portability and simplify its API, libev uses C<long> internally
3460	internally instead of C<size_t> when allocating its data structures. On	4808	instead of C<size_t> when allocating its data structures. On non-POSIX
3461	non-POSIX systems (Microsoft...) this might be unexpectedly low, but	4809	systems (Microsoft...) this might be unexpectedly low, but is still at
3462	is still at least 31 bits everywhere, which is enough for hundreds of	4810	least 31 bits everywhere, which is enough for hundreds of millions of
3463	millions of watchers.	4811	watchers.
3464		4812
3465	=item C<double> must hold a time value in seconds with enough accuracy	4813	=item C<double> must hold a time value in seconds with enough accuracy
3466		4814
3467	The type C<double> is used to represent timestamps. It is required to	4815	The type C<double> is used to represent timestamps. It is required to
3468	have at least 51 bits of mantissa (and 9 bits of exponent), which is good	4816	have at least 51 bits of mantissa (and 9 bits of exponent), which is
3469	enough for at least into the year 4000. This requirement is fulfilled by	4817	good enough for at least into the year 4000 with millisecond accuracy
		4818	(the design goal for libev). This requirement is overfulfilled by
3470	implementations implementing IEEE 754 (basically all existing ones).	4819	implementations using IEEE 754, which is basically all existing ones. With
		4820	IEEE 754 doubles, you get microsecond accuracy until at least 2200.
3471		4821
3472	=back	4822	=back
3473		4823
3474	If you know of other additional requirements drop me a note.	4824	If you know of other additional requirements drop me a note.
3475		4825
3476		4826
3477	=head1 COMPILER WARNINGS	4827	=head1 ALGORITHMIC COMPLEXITIES
3478		4828
3479	Depending on your compiler and compiler settings, you might get no or a	4829	In this section the complexities of (many of) the algorithms used inside
3480	lot of warnings when compiling libev code. Some people are apparently	4830	libev will be documented. For complexity discussions about backends see
3481	scared by this.	4831	the documentation for C<ev_default_init>.
3482		4832
3483	However, these are unavoidable for many reasons. For one, each compiler	4833	All of the following are about amortised time: If an array needs to be
3484	has different warnings, and each user has different tastes regarding	4834	extended, libev needs to realloc and move the whole array, but this
3485	warning options. "Warn-free" code therefore cannot be a goal except when	4835	happens asymptotically rarer with higher number of elements, so O(1) might
3486	targeting a specific compiler and compiler-version.	4836	mean that libev does a lengthy realloc operation in rare cases, but on
		4837	average it is much faster and asymptotically approaches constant time.
3487		4838
3488	Another reason is that some compiler warnings require elaborate	4839	=over 4
3489	workarounds, or other changes to the code that make it less clear and less
3490	maintainable.
3491		4840
3492	And of course, some compiler warnings are just plain stupid, or simply	4841	=item Starting and stopping timer/periodic watchers: O(log skipped_other_timers)
3493	wrong (because they don't actually warn about the condition their message
3494	seems to warn about).
3495		4842
3496	While libev is written to generate as few warnings as possible,	4843	This means that, when you have a watcher that triggers in one hour and
3497	"warn-free" code is not a goal, and it is recommended not to build libev	4844	there are 100 watchers that would trigger before that, then inserting will
3498	with any compiler warnings enabled unless you are prepared to cope with	4845	have to skip roughly seven (C<ld 100>) of these watchers.
3499	them (e.g. by ignoring them). Remember that warnings are just that:
3500	warnings, not errors, or proof of bugs.
3501		4846
		4847	=item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)
3502		4848
3503	=head1 VALGRIND	4849	That means that changing a timer costs less than removing/adding them,
		4850	as only the relative motion in the event queue has to be paid for.
3504		4851
3505	Valgrind has a special section here because it is a popular tool that is	4852	=item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
3506	highly useful, but valgrind reports are very hard to interpret.
3507		4853
3508	If you think you found a bug (memory leak, uninitialised data access etc.)	4854	These just add the watcher into an array or at the head of a list.
3509	in libev, then check twice: If valgrind reports something like:
3510		4855
3511	==2274== definitely lost: 0 bytes in 0 blocks.	4856	=item Stopping check/prepare/idle/fork/async watchers: O(1)
3512	==2274== possibly lost: 0 bytes in 0 blocks.
3513	==2274== still reachable: 256 bytes in 1 blocks.
3514		4857
3515	Then there is no memory leak. Similarly, under some circumstances,	4858	=item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))
3516	valgrind might report kernel bugs as if it were a bug in libev, or it
3517	might be confused (it is a very good tool, but only a tool).
3518		4859
3519	If you are unsure about something, feel free to contact the mailing list	4860	These watchers are stored in lists, so they need to be walked to find the
3520	with the full valgrind report and an explanation on why you think this is	4861	correct watcher to remove. The lists are usually short (you don't usually
3521	a bug in libev. However, don't be annoyed when you get a brisk "this is	4862	have many watchers waiting for the same fd or signal: one is typical, two
3522	no bug" answer and take the chance of learning how to interpret valgrind	4863	is rare).
3523	properly.
3524		4864
3525	If you need, for some reason, empty reports from valgrind for your project	4865	=item Finding the next timer in each loop iteration: O(1)
3526	I suggest using suppression lists.
3527		4866
		4867	By virtue of using a binary or 4-heap, the next timer is always found at a
		4868	fixed position in the storage array.
		4869
		4870	=item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)
		4871
		4872	A change means an I/O watcher gets started or stopped, which requires
		4873	libev to recalculate its status (and possibly tell the kernel, depending
		4874	on backend and whether C<ev_io_set> was used).
		4875
		4876	=item Activating one watcher (putting it into the pending state): O(1)
		4877
		4878	=item Priority handling: O(number_of_priorities)
		4879
		4880	Priorities are implemented by allocating some space for each
		4881	priority. When doing priority-based operations, libev usually has to
		4882	linearly search all the priorities, but starting/stopping and activating
		4883	watchers becomes O(1) with respect to priority handling.
		4884
		4885	=item Sending an ev_async: O(1)
		4886
		4887	=item Processing ev_async_send: O(number_of_async_watchers)
		4888
		4889	=item Processing signals: O(max_signal_number)
		4890
		4891	Sending involves a system call I<iff> there were no other C<ev_async_send>
		4892	calls in the current loop iteration. Checking for async and signal events
		4893	involves iterating over all running async watchers or all signal numbers.
		4894
		4895	=back
		4896
		4897
		4898	=head1 PORTING FROM LIBEV 3.X TO 4.X
		4899
		4900	The major version 4 introduced some incompatible changes to the API.
		4901
		4902	At the moment, the C<ev.h> header file provides compatibility definitions
		4903	for all changes, so most programs should still compile. The compatibility
		4904	layer might be removed in later versions of libev, so better update to the
		4905	new API early than late.
		4906
		4907	=over 4
		4908
		4909	=item C<EV_COMPAT3> backwards compatibility mechanism
		4910
		4911	The backward compatibility mechanism can be controlled by
		4912	C<EV_COMPAT3>. See L<PREPROCESSOR SYMBOLS/MACROS> in the L<EMBEDDING>
		4913	section.
		4914
		4915	=item C<ev_default_destroy> and C<ev_default_fork> have been removed
		4916
		4917	These calls can be replaced easily by their C<ev_loop_xxx> counterparts:
		4918
		4919	ev_loop_destroy (EV_DEFAULT_UC);
		4920	ev_loop_fork (EV_DEFAULT);
		4921
		4922	=item function/symbol renames
		4923
		4924	A number of functions and symbols have been renamed:
		4925
		4926	ev_loop => ev_run
		4927	EVLOOP_NONBLOCK => EVRUN_NOWAIT
		4928	EVLOOP_ONESHOT => EVRUN_ONCE
		4929
		4930	ev_unloop => ev_break
		4931	EVUNLOOP_CANCEL => EVBREAK_CANCEL
		4932	EVUNLOOP_ONE => EVBREAK_ONE
		4933	EVUNLOOP_ALL => EVBREAK_ALL
		4934
		4935	EV_TIMEOUT => EV_TIMER
		4936
		4937	ev_loop_count => ev_iteration
		4938	ev_loop_depth => ev_depth
		4939	ev_loop_verify => ev_verify
		4940
		4941	Most functions working on C<struct ev_loop> objects don't have an
		4942	C<ev_loop_> prefix, so it was removed; C<ev_loop>, C<ev_unloop> and
		4943	associated constants have been renamed to not collide with the C<struct
		4944	ev_loop> anymore and C<EV_TIMER> now follows the same naming scheme
		4945	as all other watcher types. Note that C<ev_loop_fork> is still called
		4946	C<ev_loop_fork> because it would otherwise clash with the C<ev_fork>
		4947	typedef.
		4948
		4949	=item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES>
		4950
		4951	The preprocessor symbol C<EV_MINIMAL> has been replaced by a different
		4952	mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile
		4953	and work, but the library code will of course be larger.
		4954
		4955	=back
		4956
		4957
		4958	=head1 GLOSSARY
		4959
		4960	=over 4
		4961
		4962	=item active
		4963
		4964	A watcher is active as long as it has been started and not yet stopped.
		4965	See L<WATCHER STATES> for details.
		4966
		4967	=item application
		4968
		4969	In this document, an application is whatever is using libev.
		4970
		4971	=item backend
		4972
		4973	The part of the code dealing with the operating system interfaces.
		4974
		4975	=item callback
		4976
		4977	The address of a function that is called when some event has been
		4978	detected. Callbacks are being passed the event loop, the watcher that
		4979	received the event, and the actual event bitset.
		4980
		4981	=item callback/watcher invocation
		4982
		4983	The act of calling the callback associated with a watcher.
		4984
		4985	=item event
		4986
		4987	A change of state of some external event, such as data now being available
		4988	for reading on a file descriptor, time having passed or simply not having
		4989	any other events happening anymore.
		4990
		4991	In libev, events are represented as single bits (such as C<EV_READ> or
		4992	C<EV_TIMER>).
		4993
		4994	=item event library
		4995
		4996	A software package implementing an event model and loop.
		4997
		4998	=item event loop
		4999
		5000	An entity that handles and processes external events and converts them
		5001	into callback invocations.
		5002
		5003	=item event model
		5004
		5005	The model used to describe how an event loop handles and processes
		5006	watchers and events.
		5007
		5008	=item pending
		5009
		5010	A watcher is pending as soon as the corresponding event has been
		5011	detected. See L<WATCHER STATES> for details.
		5012
		5013	=item real time
		5014
		5015	The physical time that is observed. It is apparently strictly monotonic :)
		5016
		5017	=item wall-clock time
		5018
		5019	The time and date as shown on clocks. Unlike real time, it can actually
		5020	be wrong and jump forwards and backwards, e.g. when the you adjust your
		5021	clock.
		5022
		5023	=item watcher
		5024
		5025	A data structure that describes interest in certain events. Watchers need
		5026	to be started (attached to an event loop) before they can receive events.
		5027
		5028	=back
3528		5029
3529	=head1 AUTHOR	5030	=head1 AUTHOR
3530		5031
3531	Marc Lehmann <libev@schmorp.de>.	5032	Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael
		5033	Magnusson and Emanuele Giaquinta.
3532		5034

Diff Legend

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