[lkml]   [2001]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: O_NONBLOCK on files
On Wed, Sep 19, 2001 at 01:05:06AM -0600, Eric W. Biederman wrote:

> Besides the SUS or the POSIX specs...

Yeah, well, blah.

> What would cause the data to be read in if read just checks the caches?
> With sockets the other side is clearing pushing or pulling the data. With
> files there is no other side...

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.

Reading a file would need a receive queue to make this work, I guess. :)


[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ ][ ]
[ Opinions expressed are not necessarily those of my employers. ]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.081 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site