Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 May 2016 18:45:25 +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-MJM87EcFAA@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209558-16@https.bugs.freebsd.org/bugzilla/>
References:  <bug-209558-16@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209558

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Works As Intended

--- Comment #4 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Jilles Tjoelker from comment #3)
Such program must not use single kqueue for several threads, if the desire =
is
to avoid the thundering herd issue.

More important is that socket events are level triggered, i.e. readiness of=
 the
listen socket must be reported until the incoming connection is consumed.  =
So
the program behaviour is as intended.  Change of wakeup(9) to wakeup_one(9)
hides userspace bug, you just do not get all _required_ notifications since
less threads are runnable.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209558-16-MJM87EcFAA>