From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
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 16:50:03 +0000 [thread overview]
Message-ID: <20050315165003.GF21986@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1110903996.6290.73.camel@laptopd505.fenrus.org>
On Tue, Mar 15, 2005 at 05:26:36PM +0100, Arjan van de Ven wrote:
> 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)
Can we get rid of the "nobh" ext2 mount option too so other people don't
get mislead into thinking this is a good idea?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-03-15 16:50 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
2005-03-15 16:36 ` Badari Pulavarty
2005-03-15 16:50 ` Matthew Wilcox [this message]
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=20050315165003.GF21986@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=arjan@infradead.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®