From: Daniel Phillips <phillips@bonn-fries.net>
To: Hugh Dickins <hugh@veritas.com>, Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-mm@kvack.org, Andrew Morton <akpm@zip.com.au>,
Mike Galbraith <mikeg@wen-online.de>,
Steven Cole <elenstev@mesatop.com>,
Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Subject: Re: 2.4.8-pre1 and dbench -20% throughput
Date: Sun, 29 Jul 2001 23:20:21 +0200 [thread overview]
Message-ID: <01072923202100.01194@starship> (raw)
In-Reply-To: <Pine.LNX.4.21.0107292131380.1085-100000@localhost.localdomain>
On Sunday 29 July 2001 22:44, Hugh Dickins wrote:
> On Sun, 29 Jul 2001, Rik van Riel wrote:
> > Actually, I liked the fact that we could change the policy
> > of up and down aging of pages in one place instead of having
> > to edit the source in multiple places...
>
> No question, that was a good principle; but in practice there were or
> are very few places where they were used, yet far too many variants
> provided, some with awkward side-effects on the lists.
>
> I've no objection to one age_page_up() and one age_page_down()
> (though I do find the term "age" unhelpful here), inline or macro,
> but even so a lot seems to depend on where and when we initialize it.
"Age" is hugely misleading, I think everybody agrees, but we are still
in a stable series, and a global name change would just make it harder
to apply patches.
That said, I think BSD uses "weight". It's not a lot better, but at
least you know that the more heaviliy weighted page is one with the
higher weight value, whereas we have "age up" meaning "make younger" :-/
And how can age go up and down anyway? I'd prefer to talk about
->temperature, more in line with what we see in the literature.
But then, it's so easy to talk about "aging", what would it be with
->temperature: Heating? Cooling? Stirring? ;-)
--
Daniel
--
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-07-29 21:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107272112.f6RLC3d28206@maila.telia.com>
[not found] ` <0107280034050V.00285@starship>
2001-07-27 23:43 ` Roger Larsson
2001-07-28 1:11 ` Daniel Phillips
2001-07-28 3:18 ` Daniel Phillips
2001-07-28 13:40 ` Marcelo Tosatti
2001-07-28 20:13 ` Daniel Phillips
2001-07-28 20:26 ` Linus Torvalds
2001-07-29 14:10 ` Daniel Phillips
2001-07-29 14:48 ` Rik van Riel
2001-07-29 15:34 ` Daniel Phillips
2001-07-29 15:31 ` Mike Galbraith
2001-07-29 16:05 ` Linus Torvalds
2001-07-29 20:19 ` Hugh Dickins
2001-07-29 20:25 ` Rik van Riel
2001-07-29 20:44 ` Hugh Dickins
2001-07-29 21:20 ` Daniel Phillips [this message]
2001-07-29 21:51 ` Hugh Dickins
2001-07-29 23:23 ` Rik van Riel
2001-07-31 7:30 ` Kai Henningsen
2001-07-31 14:13 ` Daniel Phillips
2001-07-31 17:37 ` Jonathan Morton
2001-07-29 1:41 ` Andrew Morton
2001-07-29 14:39 ` Daniel Phillips
2001-07-30 3:19 ` Theodore Tso
2001-07-30 15:17 ` Randy.Dunlap
2001-07-30 16:41 ` Theodore Tso
2001-07-30 17:52 ` Mike Galbraith
2001-07-30 19:39 ` Zlatko Calusic
2001-07-29 17:48 ` Steven Cole
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=01072923202100.01194@starship \
--to=phillips@bonn-fries.net \
--cc=akpm@zip.com.au \
--cc=elenstev@mesatop.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=riel@conectiva.com.br \
--cc=roger.larsson@skelleftea.mail.telia.com \
--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