From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 11/13] don't hold i_sem during O_DIRECT writes to blockdevs
Date: Sun, 28 Jul 2002 19:05:44 +0100 [thread overview]
Message-ID: <20020728190544.A14314@infradead.org> (raw)
In-Reply-To: <3D44302C.1082D6DC@zip.com.au>; from akpm@zip.com.au on Sun, Jul 28, 2002 at 10:55:56AM -0700
On Sun, Jul 28, 2002 at 10:55:56AM -0700, Andrew Morton wrote:
> > I think I prefer option 3, it's the cleanest way of doing it.
>
> It could be time to separate out a __generic_file_write() which
> doesn't take i_sem at all. The ext3 tree was doing that for a
> while, to permit multipage transactions in journalled data mode.
In fact we we already have that already in the XFS tree (Steve called it
do_generic_file_write although I'd really prefer __generic_file_write).
> > A little unrelated, but as you touch the code: what about removing the two
> > existing special cases for S_ISBLK() in generic_file_write()? they're
> > present only to provide the old (pre-LFS) blockdevice semantics on 2.4,
> > we shouldn't keept them around forever..
>
> hm. Are you sure about that? They look fairly useful to me?
The O_APPEND special casing is certainly very, very ugly - application
should use it on block devices at all - if they're screwed when doing it
anyway it's their problem.
And I think we can expect reasonable ulimits for root nowdays, although
I'm open for discussions on that one.
next prev parent reply other threads:[~2002-07-28 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 7:33 [patch 11/13] don't hold i_sem during O_DIRECT writes to blockdevs Andrew Morton
2002-07-28 11:06 ` Christoph Hellwig
2002-07-28 17:55 ` Andrew Morton
2002-07-28 18:05 ` Christoph Hellwig [this message]
2002-07-28 18:41 ` Christoph Hellwig
2002-07-29 0:04 ` Linus Torvalds
2002-07-29 0:39 ` Andrew Morton
2002-07-29 0:47 ` Linus Torvalds
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=20020728190544.A14314@infradead.org \
--to=hch@infradead.org \
--cc=akpm@zip.com.au \
--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 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.