linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: 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 16:00:03 -0400	[thread overview]
Message-ID: <20070604200003.GD19224@thunk.org> (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:
> 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

Well, I think Linus was saying that we have to do both (where the
signal interrupts and where it doesn't), and I agree with that:

  There are enough reasons to discourage people from using uninterruptible
  sleep ("this f*cking application won't die when the network goes down")
  that I don't think this is an issue. We need to handle both cases, and
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  while we can expand on the two cases we have now, we can't remove them. 
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Fortunately, although the -ERESTARTSYS framework is a little awkward
(and people can shoot arrows at me for creating it 15 year ago :-), we
do have a way of supporting both styles without _too_ much pain.

							- Ted


      parent reply	other threads:[~2007-06-04 20:00 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
2007-06-04 20:00           ` Theodore Tso [this message]

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=20070604200003.GD19224@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@clusterfs.com \
    --cc=dhlii@comcast.net \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).