From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
pbadari@us.ibm.com, sct@redhat.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ext2-devel@lists.sourceforge.net
Subject: Re: [RFC PATCH] ext3 writepage() journal avoidance
Date: Fri, 10 Mar 2006 07:43:34 -0600 [thread overview]
Message-ID: <1141998214.10426.3.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <20060310002337.489265a3.akpm@osdl.org>
On Fri, 2006-03-10 at 00:23 -0800, Andrew Morton wrote:
> Arjan van de Ven <arjan@infradead.org> wrote:
> >
> >
> > > I'm not sure that PageMappedToDisk() gets set in all the right places
> > > though - it's mainly for the `nobh' handling and block_prepare_write()
> > > would need to be taught to set it. I guess that'd be a net win, even if
> > > only ext3 uses it..
> >
> > btw is nobh mature enough yet to become the default, or to just go away
> > entirely as option ?
>
> I don't know how much usage it's had, sorry. It's only allowed in
> data=writeback mode and not many people seem to use even that.
For what it's worth, jfs has been using the nobh_* paths almost since
they where introduced (exclusively, it's not an option), so at least the
vfs pieces have been exercised to some extent.
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2006-03-10 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 18:39 [RFC PATCH] ext3 writepage() journal avoidance Badari Pulavarty
2006-03-09 23:22 ` Andrew Morton
2006-03-10 0:45 ` Badari Pulavarty
2006-03-10 1:16 ` Andrew Morton
2006-03-10 7:59 ` Arjan van de Ven
2006-03-10 8:23 ` Andrew Morton
2006-03-10 8:43 ` Arjan van de Ven
2006-03-10 8:53 ` Andrew Morton
2006-03-10 14:58 ` Badari Pulavarty
2006-03-10 16:19 ` Dave Jones
2006-03-10 16:40 ` Badari Pulavarty
2006-03-10 16:51 ` Dave Jones
2006-03-10 17:00 ` Badari Pulavarty
2006-03-10 16:46 ` Badari Pulavarty
2006-03-10 13:43 ` Dave Kleikamp [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=1141998214.10426.3.camel@kleikamp.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.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;
as well as URLs for NNTP newsgroup(s).