From: Arjan van de Ven <arjan@infradead.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Badari Pulavarty <pbadari@us.ibm.com>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Is nobh code still useful?
Date: Fri, 18 Sep 2009 16:25:54 +0200 [thread overview]
Message-ID: <20090918162554.13a72664@infradead.org> (raw)
In-Reply-To: <20090918141226.GB26991@mit.edu>
On Fri, 18 Sep 2009 10:12:26 -0400
Theodore Tso <tytso@mit.edu> wrote:
> On Thu, Sep 17, 2009 at 09:21:37PM -0700, Badari Pulavarty wrote:
> >
> > Originally it was supported on ext2. I added support nobh support
> > for ext3. At that time, the main
> > issue/complaint was that, these bufferheads consume memory from
> > ZONE_NORMAL causing
> > memory pressure on 32-bit (i386) configurations.
>
> Specifically, it matters on very large configuration systems (i.e.,
> 32GB-64GB using PAE-36) that today we'd probably just say, "use
> x86_64, you moron". It would probably matter if someone were to want
> to upgrade a non-64-bit capable machine to a newer kernel.
>
> Dropping nobh from ext3 at this point might prevent some of these
> older systems from upgrading, I'm not sure how much we would care; on
> the one hand, these machines tended to be pretty expensive, so people
> would probably want to use them for a while. On the other hand, it
> has been over five years now since x86_64 machines have been
> available, and many of these customers are highly unlikely to want to
> upgrade anyway.
isn't the converse to just make nobh the default but not an option a
better approach then?
I forgot why this was a good idea to be an option again ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-18 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 13:56 Is nobh code still useful? Jan Kara
2009-09-17 15:11 ` Boaz Harrosh
2009-09-17 15:25 ` Jan Kara
2009-09-18 4:21 ` Badari Pulavarty
2009-09-18 14:12 ` Theodore Tso
2009-09-18 14:25 ` Arjan van de Ven [this message]
2009-09-20 18:17 ` Jan Kara
2009-09-23 14:16 ` Christoph Hellwig
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=20090918162554.13a72664@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=tytso@mit.edu \
/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).