tor/changes/UserspaceIOCPBuffers
Nick Mathewson 6e6a661296 New UserspaceIOCPBuffers option to set SO_{SND,RCV}BUF to zero
When running with IOCP, we are in theory able to use userspace-
allocated buffers to avoid filling up the stingy amount of kernel
space allocated for sockets buffers.

The bufferevent_async implementation in Libevent provides this
ability, in theory.  (There are likely to be remaining bugs).  This
patch adds a new option that, when using IOCP bufferevents, sets
each socket's send and receive buffers to 0, so that we should use
this ability.

When all the bugs are worked out here, if we are right about bug 98,
this might solve or mitigate bug 98.

This option is experimental and will likely require lots of testing
and debugging.
2011-11-18 17:43:03 -05:00

8 lines
410 B
Plaintext

o Minor features:
- Experimental support for running on Windows with IOCP and no
kernel-space socket buffers. This feature is controlled by a new
UserspaceIOCPBuffers feature (off by default), which has no
effect unless Tor has been built with support for bufferevents,
is running on Windows, and has enabled IOCP. This may, in the
long run, help solve or mitigate bug 98.