From 71217f48ea498d7292ca3bf17b8bffe1ab97e642 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 28 Nov 2007 11:27:29 +0000 Subject: *** empty log message *** --- ev.html | 31 +++++++++++++++++++++++++------ ev.pod | 11 ++++++++--- 2 files changed, 33 insertions(+), 9 deletions(-) diff --git a/ev.html b/ev.html index a107da8..ec6eb1b 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -1249,7 +1249,7 @@ not exist" is signified by the st_nlink field being zero (whic otherwise always forced to be at least one) and all the other fields of the stat buffer having unspecified contents.

Since there is no standard to do this, the portable implementation simply -calls stat (2) regulalry on the path to see if it changed somehow. You +calls stat (2) regularly on the path to see if it changed somehow. You can specify a recommended polling interval for this case. If you specify a polling interval of 0 (highly recommended!) then a suitable, unspecified default value will be used (which you can expect to be around @@ -1259,8 +1259,13 @@ usually overkill.

This watcher type is not meant for massive numbers of stat watchers, as even with OS-supported change notifications, this can be resource-intensive.

At the time of this writing, no specific OS backends are implemented, but -if demand increases, at least a kqueue and inotify backend will be added.

At the time of this writing, only the Linux inotify interface is +implemented (implementing kqueue support is left as an exercise for the +reader). Inotify will be used to give hints only and should not change the +semantics of ev_stat watchers, which means that libev sometimes needs +to fall back to regular polling again even with inotify, but changes are +usually detected immediately, and if the file exists there will be no +polling.

ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)

ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)

reserved for future expansion, works like the USE symbols above.

EV_USE_INOTIFY

If defined to be 1, libev will compile in support for the Linux inotify +interface to speed up ev_stat watchers. Its actual availability will +be detected at runtime.

EV_H

The name of the ev.h header file used to include it. The default if @@ -2081,7 +2092,15 @@ some inlining decisions, saves roughly 30% codesize of amd64.

ev_child watchers use a small hash table to distribute workload by pid. The default size is 16 (or 1 with EV_MINIMAL), usually more than enough. If you need to manage thousands of children you might want to -increase this value.

+increase this value (must be a power of two).

EV_INOTIFY_HASHSIZE

ev_staz watchers use a small hash table to distribute workload by +inotify watch id. The default size is 16 (or 1 with EV_MINIMAL), +usually more than enough. If you need to manage thousands of ev_stat +watchers you might want to increase this value (must be a power of +two).

EV_COMMON

@@ -2148,7 +2167,7 @@ documentation for ev_default_init.

Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)

Starting io/check/prepare/idle/signal/child watchers: O(1)

Stopping check/prepare/idle watchers: O(1)

Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))

Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))

Finding the next timer per loop iteration: O(1)

Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)

Activating one watcher: O(1)

regulalry on the path to see if it changed somehow. You +calls C regularly on the path to see if it changed somehow. You can specify a recommended polling interval for this case. If you specify a polling interval of C<0> (highly recommended!) then a I value will be used (which you can expect to be around @@ -1236,8 +1236,13 @@ This watcher type is not meant for massive numbers of stat watchers, as even with OS-supported change notifications, this can be resource-intensive. -At the time of this writing, no specific OS backends are implemented, but -if demand increases, at least a kqueue and inotify backend will be added. +At the time of this writing, only the Linux inotify interface is +implemented (implementing kqueue support is left as an exercise for the +reader). Inotify will be used to give hints only and should not change the +semantics of C watchers, which means that libev sometimes needs +to fall back to regular polling again even with inotify, but changes are +usually detected immediately, and if the file exists there will be no +polling. =over 4 -- cgit v1.2.3