From: Benjamin LaHaise <bcrl@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
David Woodhouse <dwmw2@infradead.org>,
David Howells <dhowells@redhat.com>,
alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: manipulating sigmask from filesystems and drivers
Date: Fri, 2 Aug 2002 12:00:40 -0400 [thread overview]
Message-ID: <20020802120040.A25119@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208020833110.18265-100000@home.transmeta.com>; from torvalds@transmeta.com on Fri, Aug 02, 2002 at 08:39:34AM -0700
On Fri, Aug 02, 2002 at 08:39:34AM -0700, Linus Torvalds wrote:
> We already do this right, and there is no reason to _break_ the fact that
> we do it right. Can you come up with a _single_ reason for why we should
> break existing standardized binary interfaces?
Personally, I think that uninterruptible file io is good, but there needs
to be an upper limit to the maximum size of the io. As it stands today,
someone can do a single multigigabyte read or write that is completely
uninterruptible (even to kill -9), but could take a minute or more to
complete.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next prev parent reply other threads:[~2002-08-02 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 11:52 manipulating sigmask from filesystems and drivers David Howells
2002-07-31 11:58 ` Alan Cox
2002-08-01 19:09 ` Linus Torvalds
2002-08-01 20:10 ` David Woodhouse
2002-08-01 20:21 ` Linus Torvalds
2002-08-01 20:47 ` Roman Zippel
2002-08-01 20:51 ` Linus Torvalds
2002-08-01 21:15 ` Roman Zippel
2002-08-01 21:42 ` Linus Torvalds
2002-08-01 22:29 ` David Woodhouse
2002-08-01 22:40 ` Linus Torvalds
2002-08-01 22:50 ` David Woodhouse
2002-08-02 15:59 ` yodaiken
2002-08-01 22:35 ` Roman Zippel
2002-08-01 23:30 ` Linus Torvalds
2002-08-02 0:31 ` Olivier Galibert
2002-08-02 8:00 ` Kai Henningsen
2002-08-02 10:02 ` Roman Zippel
2002-08-02 12:38 ` Ryan Anderson
2002-08-02 15:39 ` Linus Torvalds
2002-08-02 16:00 ` Benjamin LaHaise [this message]
2002-08-02 16:27 ` Linus Torvalds
2002-08-02 17:13 ` Jamie Lokier
2002-08-02 17:29 ` Linus Torvalds
2002-08-02 17:57 ` Trond Myklebust
2002-08-02 18:10 ` Linus Torvalds
2002-08-02 17:33 ` Oliver Neukum
2002-08-03 18:27 ` David Woodhouse
2002-10-17 8:32 ` David Woodhouse
2002-08-02 19:27 ` Roman Zippel
2002-08-02 7:31 ` Giuliano Pochini
[not found] ` <mailman.1028232841.11555.linux-kernel2news@redhat.com>
2002-08-01 23:37 ` Pete Zaitcev
2002-08-01 23:46 ` David Woodhouse
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2D3E2B@nasdaq.ms.ensim.com>
2002-08-02 17:57 ` Paul Menage
2002-08-02 23:25 ` Ryan Anderson
2002-08-02 23:30 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 18:24 Jesse Pollard
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=20020802120040.A25119@redhat.com \
--to=bcrl@redhat.com \
--cc=alan@redhat.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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.