linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: Background scanning change on 2.4.6-pre1
Date: Thu, 7 Jun 2001 22:08:00 +0100	[thread overview]
Message-ID: <l03130320b7459cd17e98@[192.168.239.105]> (raw)
In-Reply-To: <Pine.LNX.4.21.0106071345190.6604-100000@penguin.transmeta.com>

>> > This is going to make all pages have age 0 on an idle system after some
>> > time (the old code from Rik which has been replaced by this code tried to
>> > avoid that)
>
>There's another reason why I think the patch may be ok even without any
>added logic: not only does it simplify the code and remove a illogical
>heuristic, but there is nothing that really says that "age 0" is
>necessarily very bad.

Here's my take on it.  The point of ageing is twofold - to age down pages
that aren't in use, and to age up pages that *are* in use.  So, pages that
are in use will remain with high ages even when background scanning is
being done, and pages that aren't in use will decay to zero age.

I can't see what's wrong with that.  When we need more memory, it's a Very
Good Thing to know that most of the pages in the system haven't been
accessed in yonks - we know exactly which ones we want to throw out first.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)

The key to knowledge is not to rely on people to teach you it.

GCS$/E/S 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+(*)


--
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/

  parent reply	other threads:[~2001-06-07 21:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 18:50 Marcelo Tosatti
2001-06-07 20:43 ` Linus Torvalds
2001-06-07 20:51   ` Linus Torvalds
2001-06-07 19:30     ` Marcelo Tosatti
2001-06-07 21:08     ` Jonathan Morton [this message]
2001-06-07 21:05   ` Andreas Dilger
2001-06-09  3:26   ` Rik van Riel
2001-06-07 21:09 ` Andreas Dilger
     [not found] <Pine.LNX.4.31.0106081313500.3244-100000@penguin.transmeta.com>
2001-06-08 19:20 ` Marcelo Tosatti
2001-06-08 21:27   ` David S. Miller
2001-06-08 19:59     ` Marcelo Tosatti
2001-06-08 21:47       ` David S. Miller
2001-06-08 21:51       ` Linus Torvalds
2001-06-08 20:44         ` Marcelo Tosatti
2001-06-08 22:33           ` Linus Torvalds
2001-06-08 21:10             ` Marcelo Tosatti
2001-06-09  0:12               ` Linus Torvalds
2001-06-09  3:48                 ` Rik van Riel
2001-06-09  4:05                   ` Linus Torvalds
2001-06-09  3:46           ` 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='l03130320b7459cd17e98@[192.168.239.105]' \
    --to=chromi@cyberspace.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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