From: Simon Kirby <sim@netnation.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_NONBLOCK on files
Date: Wed, 19 Sep 2001 00:24:39 -0700 [thread overview]
Message-ID: <20010919002439.A21138@netnation.com> (raw)
In-Reply-To: <20010918234648.A21010@netnation.com> <m1r8t3fyot.fsf@frodo.biederman.org>
In-Reply-To: <m1r8t3fyot.fsf@frodo.biederman.org>
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. :)
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
next prev parent reply other threads:[~2001-09-19 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:46 O_NONBLOCK on files Simon Kirby
2001-09-19 7:05 ` Eric W. Biederman
2001-09-19 7:24 ` Simon Kirby [this message]
2001-09-24 20:47 ` Matti Aarnio
2001-09-24 21:05 ` Simon Kirby
2001-09-24 21:30 ` Benjamin LaHaise
2001-09-19 8:52 ` Erik Andersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010919002439.A21138@netnation.com \
--to=sim@netnation.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox