[ViewVC] Diff of: cvs/libeio/eio.pod

Comparing libeio/eio.pod (file contents):
Revision 1.3 by root, Wed Oct 22 18:15:36 2008 UTC vs.
Revision 1.5 by root, Sun Nov 29 15:53:48 2009 UTC

 It also offers wrappers around C<sendfile> (Solaris, Linux, HP-UX and
 FreeBSD, with emulation on other platforms) and C<readahead> (Linux, with
 emulation elsewhere>).
-The goal is to enbale you to write fully non-blocking programs. For
+The goal is to enable you to write fully non-blocking programs. For
 example, in a game server, you would not want to freeze for a few seconds
 just because the server is running a backup and you happen to call
 C<readdir>.
 =head2 TIME REPRESENTATION
 If you need to know how, check the C<IO::AIO> perl module, which does
 exactly that.
+=head1 COMPILETIME CONFIGURATION
+These symbols, if used, must be defined when compiling F<eio.c>.
+=over 4
+=item EIO_STACKSIZE
+This symbol governs the stack size for each eio thread. Libeio itself
+was written to use very little stackspace, but when using C<EIO_CUSTOM>
+requests, you might want to increase this.
+If this symbol is undefined (the default) then libeio will use its default
+stack size (C<sizeof (long) * 4096> currently).  If it is defined, but
+C<0>, then the default operating system stack size will be used. In all
+other cases, the value must be an expression that evaluates to the desired
+stack size.
+=back
 =head1 PORTABILITY REQUIREMENTS
 In addition to a working ISO-C implementation, libeio relies on a few
 additional extensions:

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