From: Mike Fedyk <mfedyk@matchmail.com>
To: Alex Buell <alex.buell@munted.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inode_cache / dentry_cache not being reclaimed aggressively enough on low-memory PCs
Date: Sat, 3 Jan 2004 23:23:12 -0800 [thread overview]
Message-ID: <20040104072312.GM1882@matchmail.com> (raw)
In-Reply-To: <20040103190543.3b2d917f.akpm@osdl.org>
On Sat, Jan 03, 2004 at 07:05:43PM -0800, Andrew Morton wrote:
> Alex Buell <alex.buell@munted.org.uk> wrote:
> >
> > On Sat, 3 Jan 2004, Andrew Morton wrote:
> >
> > > John Lash <jlash@speakeasy.net> wrote:
> > > >
> > > > As it stands, it will maintain as many unused entries as there are used entries.
> > > > If this low memory system las a large, stable, number of inuse dentry objects,
> > > > the unused entries will match it thereby holding double the memory and possibly
> > > > causing the problem you see.
> > >
> > > Yup. There is a fix in 2.6.1-rc1 for this.
> >
> > Which change would that be? It would be nice to back-port that to 2.4.x if
> > that's possible?
>
> It is not backportable.
>
> You could try increasing `count' in shrink_dcache_memory() and
> shrink_icache_memory(). Also you should be using 2.4.23 or later because
> it does have improvements in the memory reclaim area.
Also, if there are any improvements considered for the 2.4 VM, it should be
on top of the -aa series. That's where the latest updates are, and it
doesn't make sence to work from a base that already has seperate
improvements available.
next prev parent reply other threads:[~2004-01-04 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 11:35 inode_cache / dentry_cache not being reclaimed aggressively enough on low-memory PCs Alex Buell
2004-01-03 16:30 ` John Lash
2004-01-03 18:27 ` Alex Buell
2004-01-03 22:24 ` Mike Fedyk
2004-01-03 22:55 ` Andrew Morton
2004-01-04 0:15 ` Alex Buell
2004-01-04 3:05 ` Andrew Morton
2004-01-04 7:23 ` Mike Fedyk [this message]
2004-01-05 17:32 ` Marcelo Tosatti
2004-01-05 18:47 ` Mike Fedyk
2004-01-09 20:49 ` Rik van Riel
2004-01-04 5:31 ` John Lash
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=20040104072312.GM1882@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=alex.buell@munted.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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