From: Joel Becker <Joel.Becker@oracle.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Theodore Tso <tytso@mit.edu>, Matthew Wilcox <matthew@wil.cx>,
Bryan Henderson <hbryan@us.ibm.com>,
Andreas Dilger <adilger@clusterfs.com>,
"David H. Lynch Jr." <dhlii@comcast.net>,
linux-fsdevel@vger.kernel.org
Subject: Re: Read/write counts
Date: Mon, 4 Jun 2007 12:24:52 -0700 [thread overview]
Message-ID: <20070604192452.GD6528@ca-server1.us.oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706042053340.28373@scrub.home>
On Mon, Jun 04, 2007 at 08:57:16PM +0200, Roman Zippel wrote:
> On Mon, 4 Jun 2007, Theodore Tso wrote:
>
> > Hmm, I'm not sure I would go that far. Per the POSIX specification,
> > we support the optional BSD-style restartable system calls for signals
> > which will avoid short reads; but this is only true if SA_RESTART is
> > passed to sigaction(). Without SA_RESTART, we will indeed return
> > short reads, as required by POSIX.
> >
> > I don't think Linus has said that short reads are always evil; I
> > certainly can't remember him ever making that statement. Do you have
> > a pointer to a LKML message where he's said that?
>
> That's the last discussion about signals and I/O I can remember:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0208.0/0188.html
He said 'disk read', not 'read(2)'. I'd expect he means certain
things like stat(2) and readdir(2) when they have to go to disk.
read(2) explicitly lists EINTR as a valid result, and often folks use
signals to interrupt read(2). The world certainly writes programs
to expect short read(2).
Joel
--
"Gone to plant a weeping willow
On the bank's green edge it will roll, roll, roll.
Sing a lulaby beside the waters.
Lovers come and go, the river roll, roll, rolls."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2007-06-04 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 10:20 Read/write counts David H. Lynch Jr.
2007-06-04 16:33 ` Andreas Dilger
2007-06-04 16:56 ` Bryan Henderson
2007-06-04 17:02 ` Matthew Wilcox
2007-06-04 18:33 ` Theodore Tso
2007-06-04 18:57 ` Roman Zippel
2007-06-04 19:24 ` Joel Becker [this message]
2007-06-04 20:00 ` Theodore Tso
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=20070604192452.GD6528@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=adilger@clusterfs.com \
--cc=dhlii@comcast.net \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tytso@mit.edu \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.