From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: jw schultz <jw@pegasys.ws>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: wait queue process state
Date: 29 May 2002 01:21:47 +0100 [thread overview]
Message-ID: <1022631707.4123.151.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020528190518.E21009@redhat.com>
On Wed, 2002-05-29 at 00:05, Benjamin LaHaise wrote:
> On Tue, May 28, 2002 at 04:01:43PM -0700, jw schultz wrote:
> > The read system call is interuptable, period. Disk access
> > is considered slow. If you code asuming it will not be
> > interupted or that an interupt will cause a return of -1
> > your code may break on Linux and will certainly not be
> > portable.
>
> Linux does not permit interrupting regular file reads on local disks;
> only NFS supports it. Maybe 2.5 is the time to change this.
What Unix and standards say and do make that one unfortunately a very
bad idea. Its true that to the letter of the specs you can do
interruptible disk I/O. Its also true to the real world that vast
amounts of software breaks in subtle, unreported, oh hell what ate my
file kind of ways
next prev parent reply other threads:[~2002-05-28 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 21:11 Joseph Cordina
2002-05-27 15:49 ` William Lee Irwin III
2002-05-28 7:57 ` Terje Eggestad
2002-05-28 23:01 ` jw schultz
2002-05-28 23:05 ` Benjamin LaHaise
2002-05-29 0:21 ` Alan Cox [this message]
2002-05-29 10:58 ` David Woodhouse
2002-05-29 12:43 ` Alan Cox
2002-05-29 11:55 ` Roman Zippel
2002-05-29 13:29 ` Alan Cox
2002-05-29 11:56 ` David Woodhouse
2002-05-31 19:05 ` Theodore Ts'o
2002-05-29 11:25 ` Trond Myklebust
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=1022631707.4123.151.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=jw@pegasys.ws \
--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
all inboxes | Powered by JetHome®