linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>,
	torvalds@transmeta.com, blah@kvack.org, H.H.vanRiel@fys.ruu.nl,
	nahshon@actcom.co.il, alan@lxorguk.ukuu.org.uk, paubert@iram.es,
	linux-kernel@vger.rutgers.edu, mingo@chiara.csoma.elte.hu,
	linux-mm@kvack.org
Subject: Re: Fairness in love and swapping
Date: Thu, 26 Feb 1998 22:33:28 GMT	[thread overview]
Message-ID: <199802262233.WAA03878@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <199802260805.JAA00715@cave.BitWizard.nl>

Hi,

On Thu, 26 Feb 1998 09:05:55 +0100 (MET), R.E.Wolff@BitWizard.nl
(Rogier Wolff) said:

> [ Processes P1 and P2 both need the same amount of CPU time, I've noted
> the "completion percentages" at the top. ]

> If you run it like this, you'll get:

>           0        50       100
>       P1  <---- in memory ----> 

>           0                   5         50      100
>       P2  < swapping like mad ><---- in memory ---> 

> but if the system would be "fair" we would get: 

>           0                  5                 10            15
>       P1  <------ swapping --- like --- mad ------------------- ....

>           0                  5                 10            15
>       P2  <------ swapping --- like --- mad ------------------- ....


> So.... In some cases, this behaviour is exactly what you want. 

It's maybe not "exactly what you want", but it can certainly be better
than being purely fair, for exactly this reason.  That's why it's hard
to see how we can improve much on the current scheme except to tweak
around the edges --- there are cases where being completely fair
actually reduces overall throughput substantially.

> What we really need is that some mechanism that actually determines
> in the first and last case that the system is thrashing like hell,
> and that "swapping" (as opposed to paging) is becoming a required
> strategy. 

True.  Any takers for this?  :)

--Stephen

  parent reply	other threads:[~1998-02-26 22:33 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
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 [this message]
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=199802262233.WAA03878@dax.dcs.ed.ac.uk \
    --to=sct@dcs.ed.ac.uk \
    --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-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=nahshon@actcom.co.il \
    --cc=paubert@iram.es \
    --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