From: Arjan van de Ven <arjan@infradead.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext2-devel <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: [PATCH] 2.6.11-mm3 patch for ext3 writeback "nobh" option
Date: Tue, 15 Mar 2005 17:26:36 +0100 [thread overview]
Message-ID: <1110903996.6290.73.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1110902996.24286.328.camel@dyn318077bld.beaverton.ibm.com>
On Tue, 2005-03-15 at 08:09 -0800, Badari Pulavarty wrote:
> On Mon, 2005-03-14 at 18:09, Andrew Morton wrote:
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > >
> > > Here is the 2.6.11-mm3 version of patch for adding "nobh"
> > > support for ext3 writeback mode.
> >
> > Care to update Documentation/filesystems/ext3.txt?
>
> Yes. I will do that. I am planning to add "nobh" support to
> ext3 ordered mode also, since its the default one. We need
> to modify generic interfaces like mpage_writepage(s) to
> keep track of bio count and make journal code wait for them etc. -
> at that point the "generic" code will no longer be generic.
> I am thinking of a way to do it *less* intrusively.
>
> At that point, we can make "nobh" default option. (which
> needs less documentation).
I still don't get why you want a mount option. Sure during development
it can be nice.. but do you still want it in the production trees??
(I understand that for small blocksizes you need to fallback code, fine,
no problem, but why do you want to make it an *option* instead of
automatic)
next prev parent reply other threads:[~2005-03-15 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 19:18 Badari Pulavarty
2005-03-14 19:29 ` Arjan van de Ven
2005-03-14 19:54 ` Badari Pulavarty
2005-03-15 2:09 ` Andrew Morton
2005-03-15 16:09 ` [Ext2-devel] " Badari Pulavarty
2005-03-15 16:26 ` Arjan van de Ven [this message]
2005-03-15 16:36 ` Badari Pulavarty
2005-03-15 16:50 ` Matthew Wilcox
2005-03-15 19:45 ` Andrew Morton
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=1110903996.6290.73.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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®