On Apr 28,  2:18pm, thorpej@zembu.com (Jason R Thorpe) wrote:
-- Subject: Re: possible bug in NetBSD asynchronous I/O

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.

christos

| On Sat, Apr 28, 2001 at 10:34:40PM +0200, Ignatios Souvatzis wrote:
| 
|  > > I do not exepct to receive SIGIO because the reader at the other end of
|  > > a pipe has readen a byte. Do you expect such a behavior? Since NetBSD
|  > > seems to be the only OS doing this, I beleive there is a real problem
|  > > here.
|  > 
|  > Hm, when the reader reads one byte, I can write one byte, and if I'm async
|  > writing, I deserve to get notified by SIGIO, IMO.
| 
| The real question is: do other OSs send the SIGIO only if the buffer
| goes from "no room available" to "some room available", or does it
| send it when the buffer goes from "some room available" to "some more room
| available".
| 
| -- 
|         -- Jason R. Thorpe <thorpej@zembu.com>
-- End of excerpt from Jason R Thorpe