ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/Makefile.PL
(Generate patch)

Comparing EV/Makefile.PL (file contents):
Revision 1.63 by root, Fri Jul 12 06:18:37 2019 UTC vs.
Revision 1.67 by root, Fri Dec 20 21:05:49 2019 UTC

… …
7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} 7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}
8} 8}
9 9
10my $DEFINE; 10my $DEFINE;
11 11
12unless (-e "libev/ev_linuxaio.c") { 12unless (-e "libev/ev_iouring.c") {
13 print <<EOF; 13 print <<EOF;
14 14
15*** 15***
16*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV, 16*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV,
17*** you also have to check-out the "libev" module from the same CVS 17*** you also have to check-out the "libev" module from the same CVS
… …
113 113
114 114
115The second very portable backend is poll(2). It does not exist on windows 115The second very portable backend is poll(2). It does not exist on windows
116and various versions of Mac OS X (and on the other versions it simply 116and various versions of Mac OS X (and on the other versions it simply
117doesn't work), but works basically everywhere else. It is recommended to use 117doesn't work), but works basically everywhere else. It is recommended to use
118the default here unless you run into compile problems in ev_poll.c. 118the default here unless you run into compilation problems in ev_poll.c.
119 119
120EOF 120EOF
121 121
122$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/)); 122$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/));
123 123
… …
185print <<EOF; 185print <<EOF;
186 186
187*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 187*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
188 188
189 189
190Similarly to the epoll backend above, EV can take advantage of kqueue on 190Linux 4.19 introduced another event polling interface, "io_uring". While
191many BSD systems. Support for kqueue will be detected at runtime, with a 191this API is far superior to epoll and almost rivals linuxaio, it also
192safe fallback to other methods when it cannot be used. 192suffers from the same issues as kqueue typically does: only a subset of
193file types are supported (as of 5.2). It is also very buggy still, and
194most importantly, very very slow for most workloads. Therefore, this
195backend is not used by default, even when it is compiled in, and you have
196to request it explicitly, e.g. with LIBEV_FLAGS=128. If unsure, accept the
197default.
193 198
199EOF
200
201my $can_iouring = have_inc "linux/fs.h";
202$can_iouring = $ENV{EV_IOURING} if exists $ENV{EV_IOURING};
203$can_iouring = 0 + (prompt ("Enable linux io_uring backend (y/n)?", $can_iouring ? "y" : "n") =~ /[yY]/);
204$DEFINE .= " -DEV_USE_IOURING=$can_iouring";
205
206if ($can_iouring) {
207print <<EOF;
208
209*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
210
211
212The previously mentioned Linux io_uring is experimental and will not be
213used unless requested explicitly. You can, howeer, choose to make ti a
214recommended basckend, which means it will be chosen if available even when
215not explicitly asked for, in preference to epoll on GNU/Linux. This option
216is likely temporary. When unsure, accept the default.
217
218EOF
219
220my $recommend_iouring = 0;
221$recommend_iouring = $ENV{EV_RECOMMEND_IOURING} if exists $ENV{EV_RECOMMEND_IOURING};
222$recommend_iouring = 0 + (prompt ("Treat io_uring as a recommended backend (y/n)?", $recommend_iouring ? "y" : "n") =~ /[yY]/);
223$DEFINE .= " -DEV_RECOMMEND_IOURING=$recommend_iouring";
224}
225
226print <<EOF;
227
228*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
229
230
231EV can take advantage of kqueue on many BSD systems. Support for kqueue
232will be detected at runtime, with a safe fallback to other methods when it
233cannot be used.
234
194Note that kqueue is broken on most operating systems, so by default it 235Note that kqueue is subtly broken on most operating systems, so by default
195won't be used on many platforms, but you can still create your own event 236it won't be used on many platforms, but you can still create your own
196loop with kqueue backend if you ask specifically for it. 237event loop with kqueue backend if you ask specifically for it.
197 238
198Here is what we know: 239Here is what we know:
199 240
200NetBSD: partially working in at least 3.1 and later. Yeah! :) 241NetBSD: partially working in at least 3.1 and later. Yeah! :)
201FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, 242FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
… …
292EOF 333EOF
293 334
294my $can_signalfd = have_inc "sys/signalfd.h"; 335my $can_signalfd = have_inc "sys/signalfd.h";
295$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; 336$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
296$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); 337$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));
338
339print <<EOF;
340
341*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
342
343
344Linux kernels can notify userspace about realtime clock timejumps
345using timerfd. Libev by default will try to take advantage of this if
346possible. You can completely disable the detection and use of timerfd for
347this purpose by answering 'n' here. Support for timerfd will otherwise be
348autodetected at both compile- and runtime.
349
350EOF
351
352unless (prompt ("Enable optional support for timerfd to detect timejumps (y/n)?", "y") =~ /[yY]/) {
353 $DEFINE .= " -DEV_USE_TIMERFD=0";
354}
297 355
298print <<EOF; 356print <<EOF;
299 357
300*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 358*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
301 359
… …
324 382
325Very rarely, people want to tweak EV even more, e.g. to exclude 383Very rarely, people want to tweak EV even more, e.g. to exclude
326or include certain watcher types or backends. This can be done by adding 384or include certain watcher types or backends. This can be done by adding
327extra -D options here, or via the EV_EXTRA_DEFS environment variable. 385extra -D options here, or via the EV_EXTRA_DEFS environment variable.
328 386
329For example, if you run into compile problems because of missing memory 387For example, if you run into compilation problems because of missing memory
330fences (or you just want extra performance), you can tell EV to not support 388fences (or you just want extra performance), you can tell EV to not support
331smp and threads via -DEV_NO_THREADS. 389smp and threads via -DEV_NO_THREADS.
332 390
333Normal persons just press enter. 391Most people would just press enter.
334 392
335EOF 393EOF
336 394
337$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}"; 395$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
338 396

Diff Legend

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