linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-mm@kvack.org, Alexander Viro <viro@math.psu.edu>,
	Ingo Molnar <mingo@elte.hu>
Subject: inode/dentry pressure
Date: Wed, 16 May 2001 19:59:55 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0105161953170.5251-100000@duckman.distro.conectiva> (raw)

Hi,

since the inode and dentry cache memory usage and the way this
memory is reaped by kswapd are still very fragile and these
caches often eat as much as 50% of system memory on normal
desktop systems I think we need to come up with a real solution
to this problem.

A quick fix would be to always try and reap inode and dentry
cache memory whenever these two eat over 10% of memory and let
the normal VM path eat from them when they're consuming less,
but since this could break in other situations I'm asking here
if anybody else has a real solution...

If we cannot find an easy to implement Real Solution(tm) we
should probably go for the 10% limit in 2.4 and implement the
real solution in 2.5; if anybody has a 2.4-attainable idea
I'd like to hear about it ;)

regards,

Rik
--
Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml

Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com/


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2001-05-16 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 22:59 Rik van Riel [this message]
2001-05-16 23:34 ` Alexander Viro
2001-05-17  3:26   ` Ed Tomlinson
2001-05-16 23:36 ` Jeff Garzik

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=Pine.LNX.4.33.0105161953170.5251-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=bcrl@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=viro@math.psu.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