From: Jonathan Morton <chromi@cyberspace.org>
To: Benjamin Redelings I <bredelin@ucla.edu>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: VM question: side effect of not scanning Active pages?
Date: Mon, 15 Oct 2001 13:38:22 +0100 [thread overview]
Message-ID: <a05100300b7f08800c756@[192.168.239.101]> (raw)
In-Reply-To: <3BCA2015.5080306@ucla.edu>
> In both Andrea and Rik's VM, I have tried modifying try_to_swap_out so
>that a page would be skipped if it is "active". For example, I have
>currently modified 2.4.13-pre2 by adding:
>
> if (PageActive(page))
> return 0;
>
>after testing the hardware referenced bit. This was motivated by
>sections of VM-improvement patches written by both Rik and Andrea.
> This SEEMS to increase performance, but it has another side
>effect. The
>RSS of unused daemons no longer EVER drops to 4k, which it does without
>this modification. The RSS does decrease (usually) to the value of
>shared memory, but the amount of shared memory only gets down to about
>200-300k instead of decreasing to 4k.
> Can anyone tell me why not scanning Active page for swapout would have
>this effect? Thanks!
The "active" pages in your inactive daemons are probably the glibc
pages, which are generally in use by other applications. It should
not have any real effect on the system - in fact, keeping glibc in
memory is probably a Good Thing, and may be partially responsible for
your improvement in performance.
AFAICT, 'pinning' active pages in memory is a good thing, provided
they are deactivated appropriately after a period of disuse. This
appears to be the case in current kernels and the new VM, so you're
good to go in my view.
--
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
website: http://www.chromatix.uklinux.net/vnc/
geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline: The key to knowledge is not to rely on people to teach you it.
--
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-mm.org/
prev parent reply other threads:[~2001-10-15 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 23:30 Benjamin Redelings I
2001-10-14 18:55 ` Joseph A Knapka
[not found] ` <3BCA6F25.2000807@ucla.edu>
2001-10-14 23:58 ` Joseph A Knapka
2001-10-15 12:38 ` Jonathan Morton [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='a05100300b7f08800c756@[192.168.239.101]' \
--to=chromi@cyberspace.org \
--cc=bredelin@ucla.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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