From: Andrew Morton <akpm@osdl.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: 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 00:23:37 -0800 [thread overview]
Message-ID: <20060310002337.489265a3.akpm@osdl.org> (raw)
In-Reply-To: <1141977557.2876.20.camel@laptopd505.fenrus.org>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: 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 00:23:37 -0800 [thread overview]
Message-ID: <20060310002337.489265a3.akpm@osdl.org> (raw)
In-Reply-To: <1141977557.2876.20.camel@laptopd505.fenrus.org>
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.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-10 8:26 UTC|newest]
Thread overview: 18+ 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 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 [this message]
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: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
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=20060310002337.489265a3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Ext2-devel@lists.sourceforge.net \
--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 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.