From: Nick Piggin <npiggin@suse.de>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
Badari Pulavarty <pbadari@gmail.com>
Subject: Re: [patch][rfc] fs: fix nobh error handling
Date: Thu, 9 Aug 2007 03:45:52 +0200 [thread overview]
Message-ID: <20070809014552.GC12539@wotan.suse.de> (raw)
In-Reply-To: <1186583982.20310.4.camel@localhost.localdomain>
On Wed, Aug 08, 2007 at 07:39:42AM -0700, Mingming Cao wrote:
> On Wed, 2007-08-08 at 08:07 -0500, Dave Kleikamp wrote:
> >
> > For jfs's sake, I don't really care if it ever uses nobh again. I
> > originally started using it because I figured the movement was away from
> > buffer heads and jfs seemed just as happy with the nobh functions (after
> > a few bugs were flushed out). I don't think jfs really benefitted
> > though.
> >
> > That said, I don't really know who cares about the nobh option in ext3.
> >
>
> Actually IBM/LTC use the nobh option in ext3 on our internal kernel
> development server, to control the consumption of large amount of low
> memory space.
Fair enough... but you mean to say that page reclaim does not control
the consumption of low memory well enough? Ie. what is the exact benefit
of using nobh?
(I'm not trying to argue to remove it... yet... just interested)
next prev parent reply other threads:[~2007-08-09 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 5:51 [patch][rfc] fs: fix nobh error handling Nick Piggin
2007-08-08 1:09 ` Andrew Morton
2007-08-08 2:18 ` Nick Piggin
2007-08-08 2:33 ` Andrew Morton
2007-08-08 3:12 ` Nick Piggin
2007-08-08 13:07 ` Dave Kleikamp
2007-08-08 14:39 ` Mingming Cao
2007-08-09 1:45 ` Nick Piggin [this message]
2007-08-20 4:33 ` Nick Piggin
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=20070809014552.GC12539@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=shaggy@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).