linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. Werner Fink" <werner@suse.de>
To: sct@dcs.ed.ac.uk
Cc: R.E.Wolff@BitWizard.nl, torvalds@transmeta.com, blah@kvack.org,
	H.H.vanRiel@fys.ruu.nl, 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: Fri, 27 Feb 1998 00:20:09 +0100	[thread overview]
Message-ID: <199802262320.AAA21643@boole.fs100.suse.de> (raw)
In-Reply-To: <199802262236.WAA03891@dax.dcs.ed.ac.uk> (sct@dcs.ed.ac.uk)

> >> "swapping" (as opposed to paging) is becoming a required
> >> strategy
> 
> > In other words: the pages swapped in or cached into the swap cache
> > should get their initial age which its self is calculated out of the
> > current priority of the corresponding process?
> 
> No, the idea is that we stop paging one or more processes altogether
> and suspend them for a while, flushing their entire resident set out
> to disk for the duration.  It's something very valuable when you are
> running big concurrent batch jobs, and essentially moves the fairness
> problem out of the memory space and into the scheduler, where we _can_
> make a reasonable stab at being fair.

Ohmm ... yes, but it's a pity because the diagrams of Roger took an old idea
of mine back into my mind :)  The idea was simply to give a process an
advantage over the others within its time slice by simply makeing
touch_page(), age_page(), and a new inline intial_age() depending on the
amount of the process time slice.


            Werner

  reply	other threads:[~1998-02-26 23:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-25 20:32 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
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 [this message]
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=199802262320.AAA21643@boole.fs100.suse.de \
    --to=werner@suse.de \
    --cc=H.H.vanRiel@fys.ruu.nl \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=blah@kvack.org \
    --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