From: "J . A . Magallon" <jamagallon@able.es>
To: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
Cc: "linux-kernel @ vger . kernel . org" <linux-kernel@vger.kernel.org>
Subject: Re: VM behaviour under 2.4.5-ac21
Date: Sat, 30 Jun 2001 01:20:17 +0200 [thread overview]
Message-ID: <20010630012017.A5048@werewolf.able.es> (raw)
In-Reply-To: <3B3C95AF.9D125337@TeraPort.de>
In-Reply-To: <3B3C95AF.9D125337@TeraPort.de>; from Martin.Knoblauch@TeraPort.de on Fri, Jun 29, 2001 at 16:50:23 +0200
On 20010629 Martin Knoblauch wrote:
>Hi,
>
> just something positive for the weekend. With 2.4.5-ac21, the behaviour
>on my laptop (128MB plus twice the sapw) seems a bit more sane. When I
>start new large applications now, the "used" portion of VM actually
>pushes against the cache instead of forcing stuff into swap. It is still
>using swap, but the effects on interactivity are much lighter.
>
I was just going to say the same. After ac20, I think, the kernel stopped
pre-allocating swap.
Before I had always some swap used even if I was only using half my core memory
(256Mb). And growing. I have not seen the box touch the swap since ac20.
It uses all the ram it can get for cache, but does not send anything to swap
to use its ram for cache.
Now running ac21 while building ac22, and state is:
werewolf:/usr/src# free
total used free shared buffers cached
Mem: 255588 241044 14544 2168 8836 153752
-/+ buffers/cache: 78456 177132
Swap: 152576 0 152576
werewolf:/usr/src# vmstat
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
1 0 0 0 6944 8836 153868 0 0 16 12 95 385 17 3 80
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.1 (Cooker) for i586
Linux werewolf 2.4.5-ac21 #1 SMP Fri Jun 29 16:02:22 CEST 2001 i686
next prev parent reply other threads:[~2001-06-29 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 14:50 VM behaviour under 2.4.5-ac21 Martin Knoblauch
2001-06-29 23:20 ` J . A . Magallon [this message]
2001-06-30 15:33 ` Marcelo Tosatti
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=20010630012017.A5048@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Martin.Knoblauch@TeraPort.de \
--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.