From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: ext3 inode cache eats system, news at 11
Date: Wed, 28 Apr 2004 05:41:10 -0500 [thread overview]
Message-ID: <20040428104110.GU2995@rx8.ibm.com> (raw)
In-Reply-To: <20040426210237.788045cf.akpm@osdl.org> (from akpm@osdl.org on Mon, Apr 26, 2004 at 23:02:37 -0500)
On 04/26/04 23:02:37, Andrew Morton wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >
> > Andrew Morton wrote:
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/broken-out/slab-order-0-for-vfs-caches.patch
> > >
> > > is not a completely happy solution, but it should fix things up.
> >
> > Another thing you could be doing is not zeroing swapper->nr
> > if the shrinker function doesn't do anything, in order to try
> > to maintain pressure on the dcache. This would be similar to
> > your deferred list idea.
>
> Am now doing this.
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6-rc2/2.6.6-rc2-mm2/broken-out/shrink_slab-handle-GFP_NOFS.patch
Hi Andrew,
I've been fighting a similar problem to this one on a SpecSFS setup
that Im running and it seems that this patch fixes it. While I was
trying several other patches at the time (all of them not dcache
related) and its hard right now to measure the exact improvement
percentage, I would guess that these patches provides at least a
11% improvement on my 64GB machine.
BTW: I was using JFS on my setup.
Thanks
-JRS
prev parent reply other threads:[~2004-04-28 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:18 ext3 inode cache eats system, news at 11 Jonathan Corbet
2004-04-26 17:58 ` Chris Wedgwood
2004-04-27 1:12 ` Andrew Morton
2004-04-27 3:26 ` Nick Piggin
2004-04-27 4:02 ` Andrew Morton
2004-04-27 4:17 ` Nick Piggin
2004-04-28 10:41 ` Jose R. Santos [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=20040428104110.GU2995@rx8.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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