From: Rik van Riel <riel@nl.linux.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux MM <linux-mm@kvack.org>,
"Stephen Tweedie <sct@redhat.com> Linux Kernel"
<linux-kernel@vger.rutgers.edu>
Subject: Re: [PATCH] kswapd performance fix
Date: Fri, 25 Feb 2000 12:55:19 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10002251250450.24051-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <14518.22746.519992.127418@dukat.scot.redhat.com>
On Fri, 25 Feb 2000, Stephen C. Tweedie wrote:
> On Fri, 25 Feb 2000 00:30:59 +0100 (CET), Rik van Riel
> <riel@nl.linux.org> said:
>
> > The patch should apply to any 2.2 or 2.3 kernel, but for
> > 2.3 it'll have the interesting side effect of nullifying
> > the (minimal) page aging that's going on there.
>
> Have you actually tested the impact of this under a variety of
> load conditions? In the past we have seen such apparently trivial
> changes completely break the VM balance under certain loads.
The PG_referenced bit isn't used for anything except for
NRU/LRU page reclaiming in shrink_mmap().
However, shrink_mmap() will skip over any pages that are
still mapped by processes _and_ when we unmap the page
from the (next to) last user we set the PG_referenced bit.
The PG_referenced bit is also not used at all by shrink_mmap(),
unless (page->count == 1); shm_swap() doesn't use the referenced
bit at all.
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
--
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/
prev parent reply other threads:[~2000-02-25 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 23:30 Rik van Riel
2000-02-25 10:26 ` Stephen C. Tweedie
2000-02-25 11:55 ` Rik van Riel [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=Pine.LNX.4.10.10002251250450.24051-100000@mirkwood.dummy.home \
--to=riel@nl.linux.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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