Re: O_NONBLOCK on files

[Simon Kirby <sim@netnation.com>]

On Mon, Sep 24, 2001 at 11:47:17PM +0300, Matti Aarnio wrote:

> On Wed, Sep 19, 2001 at 12:24:39AM -0700, Simon Kirby wrote:
> 
> > Hmm...Without even thinking about it, I assumed it would start a read and
> > select() or poll() or some later call would return readable when my
> > outstanding request was fulfilled.  But yes, I guess you're right, this is
> > different behavior because there is no other side.
> 
>    To push the idea into ultimate:  AIO
> 
>    You open file, start IO, and do other things while the machine
>    is doing IO.    Doing open() asynchronously would be ultimate,
>    but alas, not particularly trivial.
> 
>    There are problems also in the AIO status rendezvous mechanisms.
> 
>    Your best choice could be (with moderation) to do synchronous
>    operations at separate threads.

Yes, but this sucks.  My whole intent was an interface design that would
never need to context switch.  I'm not sure if this is even possible, but
if so it would be very nice from a userspace perspective.

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]