|
Revision tags: release-2.2.1-alpha, release-2.1.12-stable, release-2.1.11-stable, release-2.1.10-stable, release-2.1.9-beta, release-2.0.23-beta, release-2.1.8-stable, release-2.1.7-rc, release-2.1.6-beta, release-2.0.22-stable, release-1.4.15-stable, release-2.1.5-beta, release-2.1.4-alpha, release-2.1.3-alpha, release-2.1.2-alpha, release-2.0.21-stable, release-2.0.20-stable, release-2.0.19-stable, release-2.1.1-alpha, release-2.0.18-stable, release-2.0.17-stable, release-2.0.16-stable, release-2.0.15-stable, release-2.0.14-stable, release-2.0.13-stable, release-2.0.12-stable, release-2.0.11-stable, release-2.0.10-stable, release-2.0.9-rc, release-2.0.8-rc |
|
| #
53a07fe2 |
| 17-Sep-2010 |
Nick Mathewson <[email protected]> |
Replace pipe-based notification with EVFILT_USER where possible
Sufficiently recent kqueue implementations have an EVFILT_USER filter
that we can use to wake up an event base from another thread. W
Replace pipe-based notification with EVFILT_USER where possible
Sufficiently recent kqueue implementations have an EVFILT_USER filter
that we can use to wake up an event base from another thread. When
it's supported, we now use this mechanism rather than our old
(pipe-based) mechanism. This should save some time and complications
on newer OSX and freebsds.
show more ...
|