public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: swap still stuck
Date: Wed, 21 Feb 2001 00:14:06 +0100	[thread overview]
Message-ID: <20010221001406.A1035@werewolf.able.es> (raw)

Hi, everyone.

I seem to have again a problem that was talked about on the list, but I thought
it was yet corrected with some VM constants balancing.

I run 2.4.1-ac19-SMP. System works fine, but after a couple kernel untars
and an open netscape, starts to swap. Read buffers are still there. Do the
untars, launch netscape and instead of trashing buffers takes a bite on
swap.

Then you let netscape (what a mem hog example...) forgotten and start to do
some terminal work, config kernel, build, etc. Return to netscape and it is
much less responsible and disk starts to crawl to un-swap netscape. And
my 200 Mb of read buffers are still in main memory...

Is there any utility to say to kernel TROW AWAY YOUR READ BUFFERS ?. It looks
like it does not know how to do it.

I have finished some work session with just the last rxvt on screen, a mem like:

werewolf:~/soft/snd/alsa/alsa-utils# free
             total       used       free     shared    buffers     cached
Mem:        255524     244888      10636          0      94816      97052
-/+ buffers/cache:      53020     202504
Swap:       152576       9024     143552

but swap being 50Mb.

Why system does not try to drop read buffer pages before swapping ?


-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.1-ac19 #1 SMP Mon Feb 19 21:52:31 CET 2001 i686


             reply	other threads:[~2001-02-20 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 23:14 J . A . Magallon [this message]
2001-02-21 23:15 ` swap still stuck Rik van Riel

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=20010221001406.A1035@werewolf.able.es \
    --to=jamagallon@able.es \
    --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