All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: smurf@smurf.noris.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists
Date: Sat, 13 Mar 2004 10:23:11 +1100	[thread overview]
Message-ID: <4052465F.4010201@cyberone.com.au> (raw)
In-Reply-To: <20040312111228.3425780b.akpm@osdl.org>



Andrew Morton wrote:

>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>>Just had a try of doing things like updatedb and dd if=/dev/zero of=./blah
>>It is pretty swappy I guess.
>>
>
>You'll need to bring the scanning priority back into the picture: don't
>move mapped pages down onto the inactive list at low scanning priorities. 
>And that eans retaining the remember-the-priority-from-last-time logic.
>
>Otherwise it's inevitable that even a `cat monster_file > /dev/null' will
>eventually swap out everything it can.
>
>

Hmm I dunno. At mapped_page_cost 8, I don't think it is swappy enough
that your desktop users will be running into problems. I need to write
4GB of file to push out 70MB of swap here (256MB RAM). And not much of
that swap has come back in, by the way...

>>By the way, I would be interested to know the rationale behind
>>mark_page_accessed as it is without this patch, also what is it doing in
>>rmap.c (I know hardly anything actually uses page_test_and_clear_young, but
>>still). It seems to me like it only serves to make VM behaviour harder to
>>understand, but I'm probably missing something. Andrew?
>>
>
>hm, that's left-over code which is pretty pointless now.
>
>
>	if (page_test_and_clear_young(page))
>		mark_page_accessed(page);
>
>	if (TestClearPageReferenced(page))
>		referenced++;
>
>The pages in here are never on the LRU, so all the mark_page_accessed()
>will do is to set PG_Referenced.  And we immediately clear it again.  So
>the mark_page_accessed() can be replaced with referenced++.
>
>
>

Yep, see the patch I'd attached before.


  reply	other threads:[~2004-03-12 23:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11  0:04 [PATCH] 2.6.4-rc2-mm1: vm-split-active-lists Nick Piggin
2004-03-11 17:25 ` Marc-Christian Petersen
2004-03-11 17:25   ` Marc-Christian Petersen
2004-03-12  9:09   ` Nick Piggin
2004-03-12  9:09     ` Nick Piggin
2004-03-12  9:27     ` Andrew Morton
2004-03-12  9:27       ` Andrew Morton
2004-03-12  9:37       ` Nick Piggin
2004-03-12  9:37         ` Nick Piggin
2004-03-12 11:08       ` Matthias Urlichs
2004-03-12 11:47         ` Jamie Lokier
2004-03-12 12:44         ` Nick Piggin
2004-03-12 14:15           ` Nick Piggin
2004-03-12 15:05             ` Nikita Danilov
2004-03-12 15:28               ` Nick Piggin
2004-03-12 16:31                 ` Nikita Danilov
2004-03-12 23:05                   ` Nick Piggin
2004-03-12 19:12             ` Andrew Morton
2004-03-12 23:23               ` Nick Piggin [this message]
2004-03-12 19:12           ` Bill Davidsen
2004-03-12 23:50             ` Nick Piggin
2004-03-12 21:46         ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-03-12 14:18 Mark_H_Johnson
2004-03-12 14:18 ` Mark_H_Johnson
2004-03-12 14:27 ` Nick Piggin
2004-03-12 14:27   ` Nick Piggin
2004-03-12 19:46   ` Jamie Lokier
2004-03-12 19:46     ` Jamie Lokier
2004-03-12 15:00 Mark_H_Johnson
2004-03-12 15:00 ` Mark_H_Johnson
2004-03-12 15:13 ` Nick Piggin
2004-03-12 15:13   ` Nick Piggin
2004-03-12 19:35   ` Jamie Lokier
2004-03-12 19:35     ` Jamie Lokier
2004-03-12 21:17     ` Mike Fedyk
2004-03-12 21:17       ` Mike Fedyk
2004-03-12 22:21       ` Jamie Lokier
2004-03-12 22:21         ` Jamie Lokier
2004-03-12 22:36         ` Mike Fedyk
2004-03-12 22:36           ` Mike Fedyk

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=4052465F.4010201@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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.