linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tvrtko A. Uršulin" <tvrtko@croadria.com>
To: linux-kernel@vger.kernel.org
Subject: Pagecache going out of control (2.4)
Date: Fri, 29 Aug 2003 14:59:10 +0200	[thread overview]
Message-ID: <200308291459.10983.tvrtko@croadria.com> (raw)


Hello everyone,

For some time now, the situation with 2.4 kernels is the following: Try to 
gzip -d very large file (few times larger than physical RAM) in the 
background and do some other work. You will find out that your system gets 
very slow. All RAM is used up for pagecache, and even more, your application 
data is getting swapped out to make more room for pagecache!

I think this is a bad behaviour, and would pretty much like to be able to 
control the maximum memory used for pagecache.

Recently, I found a patch by indou.takao@jp.fujitsu.com which implements a 
pgcache-max sysctl for 2.5.x. I tried to backport it to 2.4.21 but so far 
with no success (many differences in VM system).

I don't understand why not to give such a option to users, I know a lot of 
them irritated with current pagecache behaviour... options and 
configurability should be a good thing, no?

Best regards,
Tvrtko A. Ursulin


                 reply	other threads:[~2003-08-29 12:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200308291459.10983.tvrtko@croadria.com \
    --to=tvrtko@croadria.com \
    --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;
as well as URLs for NNTP newsgroup(s).