> Well, putting a cpu_Debugger() in uipc_socket.c in sowakeup()
> reveals that the call is generated from uipc_usrreq(), and it
> is an sorwakeup.. The call stack is from the read... I think
> this is wrong.

I beleive the only time we should fire a SIGIO on a read operation is
when it was not possible to write to the pipe previously because no
memory was available. If the read frees some memory then the pipe
becomes available for writing, and we can send a SIGIO.

-- 
Emmanuel Dreyfus
p99dreyf@criens.u-psud.fr