All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Lash <jlash@speakeasy.net>
To: Andrew Morton <akpm@osdl.org>
Cc: alex.buell@munted.org.uk, 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:31:17 -0600	[thread overview]
Message-ID: <20040103233117.6476a799.jlash@speakeasy.net> (raw)
In-Reply-To: <20040103145557.369a12c4.akpm@osdl.org>

ahh, good. I'll take a look. Thanks Andrew.

--john


On Sat, 3 Jan 2004 14:55:57 -0800
Andrew Morton <akpm@osdl.org> 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.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

      parent reply	other threads:[~2004-01-04  5:31 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
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 [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=20040103233117.6476a799.jlash@speakeasy.net \
    --to=jlash@speakeasy.net \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.