| … | |
… | |
| 243 | |
243 | |
| 244 | If you need to know how, check the C<IO::AIO> perl module, which does |
244 | If you need to know how, check the C<IO::AIO> perl module, which does |
| 245 | exactly that. |
245 | exactly that. |
| 246 | |
246 | |
| 247 | |
247 | |
|
|
248 | =head1 COMPILETIME CONFIGURATION |
|
|
249 | |
|
|
250 | These symbols, if used, must be defined when compiling F<eio.c>. |
|
|
251 | |
|
|
252 | =over 4 |
|
|
253 | |
|
|
254 | =item EIO_STACKSIZE |
|
|
255 | |
|
|
256 | This symbol governs the stack size for each eio thread. Libeio itself |
|
|
257 | was written to use very little stackspace, but when using C<EIO_CUSTOM> |
|
|
258 | requests, you might want to increase this. |
|
|
259 | |
|
|
260 | If this symbol is undefined (the default) then libeio will use its default |
|
|
261 | stack size (C<sizeof (long) * 4096> currently). If it is defined, but |
|
|
262 | C<0>, then the default operating system stack size will be used. In all |
|
|
263 | other cases, the value must be an expression that evaluates to the desired |
|
|
264 | stack size. |
|
|
265 | |
|
|
266 | =back |
|
|
267 | |
|
|
268 | |
| 248 | =head1 PORTABILITY REQUIREMENTS |
269 | =head1 PORTABILITY REQUIREMENTS |
| 249 | |
270 | |
| 250 | In addition to a working ISO-C implementation, libeio relies on a few |
271 | In addition to a working ISO-C implementation, libeio relies on a few |
| 251 | additional extensions: |
272 | additional extensions: |
| 252 | |
273 | |
