From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
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 16:30:08 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106071618580.1156-100000@freak.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.21.0106071345190.6604-100000@penguin.transmeta.com>
On Thu, 7 Jun 2001, Linus Torvalds wrote:
>
> Forgot one comment..
>
> > > 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.
>
> We should strive to keep the active/inactive lists in LRU order anyway, so
> the ordering does tell you something about how recent (and thus how
> important) the page is. Also, it's certainly MUCH preferable to let pages
> age down to zero, than to let pages retain a maximum age over a long time,
> like the old code used to do.
>
> If, after long periods of inactivity, we start needing fresh pages again,
> it's probably actually an _advantage_ to give the new pages a higher
> relative importance. Caches tend to lose their usefulness over time, and
> if the old cached pages are really relevant, then the new spurt of usage
> will obviously mark them young again.
>
> And if, after the idle time, the behaviour is different, the old pages
> have appropriately been aged down and won't stand in the way of a new
> cache footprint.
>
> Do you actually have regular usage that shows the age-down to be a bad
> thing?
Fill the active list of cache and wait for a while to get the inactive
list full.
When that happens and pressure begins, refill_inactive_scan() from
try_to_free_pages() will not be called because the inactive list is full
(the kernel "thinks" we dont have an inactive shortage). Well, not sure if
this is a bad thing in the end.
--
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/
next prev parent reply other threads:[~2001-06-07 19:30 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 [this message]
2001-06-07 21:08 ` Jonathan Morton
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=Pine.LNX.4.21.0106071618580.1156-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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