On 0728T1419, Luigi Rizzo wrote:
Hi,
for some work we are doing on bhyve, we need some lightweight mechanism that
a kernel thread can use to wake up another user thread possibly
waiting for some event.
https://reviews.freebsd.org/D2172
___
Hi,
for some work we are doing on bhyve, we need some lightweight mechanism that
a kernel thread can use to wake up another user thread possibly
waiting for some event.
If the recipient of the event were a kernel thread it would simply
do a tsleep(chan...) and the sender would do a wakeup() or
On 28 Jul 2015, at 18:23, Adrian Chadd adrian.ch...@gmail.com wrote:
(What would be nice is having kqueue know about conditionals, so we
can sleep on a cond as well as a kqueue fd+queue, but I can't have
everything I want..)
I recently came across a need to do something like this. Being
On 28 July 2015 at 10:31, David Chisnall thera...@freebsd.org wrote:
On 28 Jul 2015, at 18:23, Adrian Chadd adrian.ch...@gmail.com wrote:
(What would be nice is having kqueue know about conditionals, so we
can sleep on a cond as well as a kqueue fd+queue, but I can't have
everything I want..)
There's a kqueue notification mechanism just for this very thing.
(What would be nice is having kqueue know about conditionals, so we
can sleep on a cond as well as a kqueue fd+queue, but I can't have
everything I want..)
-adrian
On 28 July 2015 at 05:19, Luigi Rizzo ri...@iet.unipi.it
On 28 Jul 2015, at 18:33, Adrian Chadd adrian.ch...@gmail.com wrote:
Windows has had this for years. It makes async network programming
with thread worker queues significantly less abusive.
Can you do the same with Solaris completion ports? It might be a good source
of inspiration for a
On 28 July 2015 at 10:42, David Chisnall thera...@freebsd.org wrote:
On 28 Jul 2015, at 18:33, Adrian Chadd adrian.ch...@gmail.com wrote:
Windows has had this for years. It makes async network programming
with thread worker queues significantly less abusive.
Can you do the same with Solaris
