Date: Sun, 22 May 2016 15:30:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 209558] [request] Wakeup only one thread while kqueue events are available Message-ID: <bug-209558-16-o58qi9c9vS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209558-16@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209558 Jilles Tjoelker <jilles@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jilles@FreeBSD.org --- Comment #3 from Jilles Tjoelker <jilles@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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209558-16-o58qi9c9vS>