| … | |
… | |
| 7 | scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} |
7 | scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} |
| 8 | } |
8 | } |
| 9 | |
9 | |
| 10 | my $DEFINE; |
10 | my $DEFINE; |
| 11 | |
11 | |
| 12 | unless (-e "libev/ev_linuxaio.c") { |
12 | unless (-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 |
| … | |
… | |
| 185 | print <<EOF; |
185 | print <<EOF; |
| 186 | |
186 | |
| 187 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
187 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
| 188 | |
188 | |
| 189 | |
189 | |
| 190 | Similarly to the epoll backend above, EV can take advantage of kqueue on |
190 | Linux 4.19 introduced another event polling interface, "io_uring". While |
| 191 | many BSD systems. Support for kqueue will be detected at runtime, with a |
191 | this API is far superior to epoll and almost rivals linuxaio, it also |
| 192 | safe fallback to other methods when it cannot be used. |
192 | suffers from the same issues as kqueue typically does: only a subset of |
|
|
193 | file types are supported (as of 5.2). It is also very buggy still, and |
|
|
194 | most importantly, very very slow for most workloads. Therefore, this |
|
|
195 | backend is not used by default, even when it is compiled in, and you have |
|
|
196 | to request it explicitly, e.g. with LIBEV_FLAGS=128. If unsure, accept the |
|
|
197 | default. |
| 193 | |
198 | |
|
|
199 | EOF |
|
|
200 | |
|
|
201 | my $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 | |
|
|
206 | if ($can_iouring) { |
|
|
207 | print <<EOF; |
|
|
208 | |
|
|
209 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
210 | |
|
|
211 | |
|
|
212 | The previously mentioned Linux io_uring is experimental and will not be |
|
|
213 | used unless requested explicitly. You can, howeer, choose to make ti a |
|
|
214 | recommended basckend, which means it will be chosen if available even when |
|
|
215 | not explicitly asked for, in preference to epoll on GNU/Linux. This option |
|
|
216 | is likely temporary. When unsure, accept the default. |
|
|
217 | |
|
|
218 | EOF |
|
|
219 | |
|
|
220 | my $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 | |
|
|
226 | print <<EOF; |
|
|
227 | |
|
|
228 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
229 | |
|
|
230 | |
|
|
231 | EV can take advantage of kqueue on many BSD systems. Support for kqueue |
|
|
232 | will be detected at runtime, with a safe fallback to other methods when it |
|
|
233 | cannot be used. |
|
|
234 | |
| 194 | Note that kqueue is broken on most operating systems, so by default it |
235 | Note that kqueue is subtly broken on most operating systems, so by default |
| 195 | won't be used on many platforms, but you can still create your own event |
236 | it won't be used on many platforms, but you can still create your own |
| 196 | loop with kqueue backend if you ask specifically for it. |
237 | event loop with kqueue backend if you ask specifically for it. |
| 197 | |
238 | |
| 198 | Here is what we know: |
239 | Here is what we know: |
| 199 | |
240 | |
| 200 | NetBSD: partially working in at least 3.1 and later. Yeah! :) |
241 | NetBSD: partially working in at least 3.1 and later. Yeah! :) |
| 201 | FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, |
242 | FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, |
