… | |
… | |
54 | |
54 | |
55 | |
55 | |
56 | POSIX optionally offers support for a (potentially) high-resolution |
56 | POSIX optionally offers support for a (potentially) high-resolution |
57 | realtime clock interface. In a good implementation, using it is faster |
57 | realtime clock interface. In a good implementation, using it is faster |
58 | than the normal method of using gettimeofday. Unfortunately, this option |
58 | than the normal method of using gettimeofday. Unfortunately, this option |
59 | is also bound to be broken on some systems, so you can disable use and |
59 | is also bound to be broken on some systems, and current EV versions do not |
60 | probing of this feature altogether here. Otherwise support for this clock |
60 | actually call C<gettimeofday> very often, so ti defaults to no. |
61 | type will be autodetected at compiletime. |
|
|
62 | |
61 | |
63 | EOF |
62 | EOF |
64 | |
63 | |
65 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "y") =~ /[yY]/)); |
64 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/)); |
66 | |
65 | |
67 | print <<EOF; |
66 | print <<EOF; |
68 | |
67 | |
69 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
68 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
70 | |
69 | |
… | |
… | |
143 | many BSD systems. Support for kqueue will be detected at runtime, with a |
142 | many BSD systems. Support for kqueue will be detected at runtime, with a |
144 | safe fallback to other methods when it cannot be used. |
143 | safe fallback to other methods when it cannot be used. |
145 | |
144 | |
146 | Note that kqueue is broken on most operating systems, so by default it |
145 | Note that kqueue is broken on most operating systems, so by default it |
147 | won't be used on many platforms, but you can still create your own event |
146 | won't be used on many platforms, but you can still create your own event |
148 | loop with kqueue backend. |
147 | loop with kqueue backend if you ask specifically for it. |
149 | |
148 | |
150 | Here is what we know: |
149 | Here is what we know: |
151 | |
150 | |
152 | NetBSD: partially working in at least 3.1. Yeah! :) |
151 | NetBSD: partially working in at least 3.1. Yeah! :) |
153 | FreeBSD: broken on at least 6.2-STABLE, |
152 | FreeBSD: broken on at least 6.2-STABLE, |
… | |
… | |
197 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
196 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
198 | |
197 | |
199 | |
198 | |
200 | A backend of a different kind is the Linux inotify(7) interface, which can |
199 | A backend of a different kind is the Linux inotify(7) interface, which can |
201 | be used to speed up (and reduce resource consumption) of stat watchers. If |
200 | be used to speed up (and reduce resource consumption) of stat watchers. If |
202 | you have it, it is usually a good idea to enable it. |
201 | you have the include file and libc support for it, it is usually a good |
|
|
202 | idea to enable it, as kernel availability is detected at runtime. |
203 | |
203 | |
204 | EOF |
204 | EOF |
205 | |
205 | |
206 | my $can_inotify = -e "/usr/include/sys/inotify.h"; |
206 | my $can_inotify = -e "/usr/include/sys/inotify.h"; |
207 | $can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY}; |
207 | $can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY}; |
… | |
… | |
221 | EOF |
221 | EOF |
222 | |
222 | |
223 | my $can_eventfd = -e "/usr/include/sys/eventfd.h"; |
223 | my $can_eventfd = -e "/usr/include/sys/eventfd.h"; |
224 | $can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD}; |
224 | $can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD}; |
225 | $DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/)); |
225 | $DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/)); |
|
|
226 | |
|
|
227 | print <<EOF; |
|
|
228 | |
|
|
229 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
230 | |
|
|
231 | |
|
|
232 | Another sometimes useful bit of functionality is the Linux signalfd, which |
|
|
233 | is useful for faster signal handling (don't care). Kernel support for |
|
|
234 | this will be probed at runtime, but your libc must contain the necessary |
|
|
235 | wrapper and include files. Glibc 2.9 and later should have this wrapper. |
|
|
236 | |
|
|
237 | EOF |
|
|
238 | |
|
|
239 | my $can_signalfd = -e "/usr/include/sys/signalfd.h"; |
|
|
240 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
|
|
241 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
226 | |
242 | |
227 | print <<EOF; |
243 | print <<EOF; |
228 | |
244 | |
229 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
245 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
230 | |
246 | |
… | |
… | |
248 | DEFINE => "$DEFINE", |
264 | DEFINE => "$DEFINE", |
249 | NAME => "EV", |
265 | NAME => "EV", |
250 | LIBS => [$LIBS], |
266 | LIBS => [$LIBS], |
251 | PREREQ_PM => { |
267 | PREREQ_PM => { |
252 | @anyevent, |
268 | @anyevent, |
|
|
269 | "common::sense" => 0, |
253 | }, |
270 | }, |
254 | VERSION_FROM => "EV.pm", |
271 | VERSION_FROM => "EV.pm", |
255 | PM => { |
272 | PM => { |
256 | 'EV.pm' => '$(INST_LIBDIR)/EV.pm', |
273 | 'EV.pm' => '$(INST_LIBDIR)/EV.pm', |
257 | 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', |
274 | 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', |