[Bug 209558] [request] Wakeup only one thread while kqueue events are available

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun May 22 15:30:49 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209558

Jilles Tjoelker <jilles at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jilles at FreeBSD.org

--- Comment #3 from Jilles Tjoelker <jilles at FreeBSD.org> ---
With the test program's current design, it should enable non-blocking mode on
the socket and ignore [EAGAIN] and [ECONNABORTED] errors from accept().

Apart from that, I appreciate the thundering herd issue with the program.
However, I'm a bit afraid of applications getting stuck for a while when the
awakened thread exits without waking another thread. Also, randomly
distributing socket events across threads seems inefficient; it should be more
efficient to tie each socket to one thread and have one kqueue per thread.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-threads mailing list