linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.5.44-mm6
Date: Mon, 28 Oct 2002 09:18:46 -0800	[thread overview]
Message-ID: <3DBD7176.BAC2BCD3@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210281051440.1697-100000@imladris.surriel.com>

Rik van Riel wrote:
> 
> On Sun, 27 Oct 2002, Andrew Morton wrote:
> 
> > . Spent some time tuning up 2.5's StupidSwapStorm throughput.  It's
> >   on par with 2.4 for single-threaded things, but not for multiple
> >   processes.
> >
> >   This is because 2.4's virtual scan allows individual processes to
> >   hammer all the others into swap and to make lots of progress then
> >   exit.  In the 2.5 VM all processes make equal progress and just
> >   thrash each other to bits.
> >
> >   This is an innate useful side-effect of the virtual scan, although
> >   it may have significant failure modes.  The 2.5 VM would need an
> >   explicit load control algorithm if we care about such workloads.
> 
> 1) 2.4 does have the failure modes you talk about ;)

Shock :)  How does one trigger them?


> 2) I have most of an explicit load control algorithm ready,
>    against an early 2.4 kernel, but porting it should be very
>    little work
> 
> Just let me know if you're interested in my load control mechanism
> and I'll send it to you.

It would be interesting if you could send out what you have.

It would also be interesting to know if we really care?  The
machine is already running 10x slower than it would be if it
had enough memory; perhaps it is just not a region of operation
for which we're interested in optimising.  (Just being argumentitive
here ;))

>  Note that I never got the load control _policy_ right yet ...

mm.  Tricky.  This is interesting:
http://www.unet.univie.ac.at/aix/aixbman/prftungd/vmmov.htm
--
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/

  reply	other threads:[~2002-10-28 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28  6:06 2.5.44-mm6 Andrew Morton
2002-10-28  2:24 ` 2.5.44-mm6 Rob Landley
2002-10-28  7:31   ` 2.5.44-mm6 Andrew Morton
2002-10-28  2:41     ` 2.5.44-mm6 Rob Landley
2002-10-28 12:53 ` 2.5.44-mm6 Rik van Riel
2002-10-28 17:18   ` Andrew Morton [this message]
2002-10-29 12:02     ` 2.5.44-mm6 Bill Davidsen
2002-10-29 17:28       ` 2.5.44-mm6 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=3DBD7176.BAC2BCD3@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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