From: "Dr. Werner Fink" <werner@suse.de>
To: H.H.vanRiel@fys.ruu.nl
Cc: sct@dcs.ed.ac.uk, torvalds@transmeta.com, nahshon@actcom.co.il,
alan@lxorguk.ukuu.org.uk, paubert@iram.es,
mingo@chiara.csoma.elte.hu, linux-mm@kvack.org
Subject: Re: Fairness in love and swapping
Date: Thu, 26 Feb 1998 19:57:54 +0100 [thread overview]
Message-ID: <199802261857.TAA13144@boole.fs100.suse.de> (raw)
In-Reply-To: <Pine.LNX.3.91.980226123303.26424F-100000@mirkwood.dummy.home> (message from Rik van Riel on Thu, 26 Feb 1998 12:34:40 +0100 (MET))
>
> > There is one point more which makes ageing a bit unfair. In
> > include/linux/pagemap.h PAGE_AGE_VALUE is defined to 16 which is used in
> > __add_page_to_hash_queue() to set the age of a hashed page ... IMHO only
> > touch_page() should be used. Nevertheless a static value of 16
> > breaks the dynamic manner of swap control via /proc/sys/vm/swapctl
>
> Without my mmap-age patch, page cache pages aren't aged
> at all... They're just freed whenever they weren't referenced
> since the last scan. The PAGE_AGE_VALUE is quite useless IMO
> (but I could be wrong, Stephen?).
The age of a page cache page isn't changed if a process took it (?). IMHO that
means that this age is the starting age of such a process page, isn't it?
Maybe it would be a win if the initial page age, the increase and decrease
amount for the page age depends on the priority or the amount of
the time slice of the owner process(es).
Werner
next prev parent reply other threads:[~1998-02-26 19:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-25 20:32 Fairness in love and swapping Stephen C. Tweedie
1998-02-25 21:02 ` Linus Torvalds
1998-02-25 21:44 ` Rik van Riel
1998-02-25 21:39 ` Dr. Werner Fink
1998-02-25 22:27 ` Rik van Riel
1998-02-26 11:03 ` Dr. Werner Fink
1998-02-26 11:34 ` Rik van Riel
1998-02-26 18:57 ` Dr. Werner Fink [this message]
1998-02-26 19:32 ` Rik van Riel
1998-02-26 22:44 ` Stephen C. Tweedie
1998-02-26 23:34 ` Rik van Riel
1998-02-27 19:41 ` Stephen C. Tweedie
1998-03-02 16:19 ` Rik van Riel
1998-03-02 22:35 ` Stephen C. Tweedie
1998-03-02 23:14 ` Rik van Riel
1998-03-03 22:59 ` Stephen C. Tweedie
1998-02-26 8:05 ` Rogier Wolff
1998-02-26 13:00 ` Dr. Werner Fink
1998-02-26 22:36 ` Stephen C. Tweedie
1998-02-26 23:20 ` Dr. Werner Fink
1998-02-26 14:30 ` Rik van Riel
1998-02-26 22:41 ` Stephen C. Tweedie
1998-02-26 23:21 ` Rik van Riel
1998-02-26 22:33 ` Stephen C. Tweedie
1998-02-26 22:49 ` Rik van Riel
1998-02-27 2:56 ` Michael O'Reilly
[not found] <199802270729.IAA00680@cave.BitWizard.nl>
1998-02-27 11:26 ` 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=199802261857.TAA13144@boole.fs100.suse.de \
--to=werner@suse.de \
--cc=H.H.vanRiel@fys.ruu.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=nahshon@actcom.co.il \
--cc=paubert@iram.es \
--cc=sct@dcs.ed.ac.uk \
--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