From: Andrew Morton <akpm@zip.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "M. Edward Borasky" <znmeb@aracnet.com>,
Art Hays <art@lsr.nei.nih.gov>,
linux-kernel@vger.kernel.org
Subject: Re: kswapd etc hogging machine
Date: Thu, 03 Jan 2002 10:59:23 -0800 [thread overview]
Message-ID: <3C34AA0B.3D4B2891@zip.com.au> (raw)
In-Reply-To: <3C33E8EA.FAF8E337@zip.com.au> from "Andrew Morton" at Jan 02, 2002 09:15:22 PM <E16M72b-0008B8-00@the-village.bc.nu>
Alan Cox wrote:
>
> > But Art's kernel (what kernel is in RH7.2 anyway? 2.4.9 with vendor
> > hacks^Wfixes, I think) is nowhere near that stage.
>
> 7.2 is 2.4.7-ac ish, 7.2 + errata is 2.4.9-ac ish
OK, thanks.
> > The good news is that 2.4.17 has pretty much slain this dragon. The
> > -aa patches are better still, and 2.4.18 will be even better than
> > that.
>
> Bollocks. I get regular mails from large numbers of people who are stuck
> at 2.4.12/13-ac and are hoping I'll do an update because their machines
> die in hours or run 25-50% slower with 2.4.1x.
I was referring to the swap and evict in the presence of heavy write
traffic.
> 2.4.1x VM code is performing better under light loads but its absolutely
> and completely hopeless under a real paging load. 2.4.17-aa is somewhat
> better interestingly.
>
s/interestingly/frustratingly/. -aa has some interesting changes to
the write scheduling as well. I just wish I knew what problem they're
solving.
-
next prev parent reply other threads:[~2002-01-03 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 3:33 kswapd etc hogging machine Art Hays
2002-01-03 4:01 ` M. Edward Borasky
2002-01-03 4:13 ` Dave Jones
2002-01-03 5:15 ` Andrew Morton
2002-01-03 5:48 ` Daniel Phillips
2002-01-03 5:54 ` Jeffrey W. Baker
2002-01-03 12:32 ` Alan Cox
2002-01-03 16:51 ` Rik van Riel
2002-01-03 17:27 ` Stephan von Krawczynski
2002-01-03 17:32 ` Rik van Riel
2002-01-03 23:42 ` Stephan von Krawczynski
2002-01-03 18:59 ` Andrew Morton [this message]
2002-01-04 7:06 ` Art Hays
2002-01-03 12:37 ` Alan Cox
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=3C34AA0B.3D4B2891@zip.com.au \
--to=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=art@lsr.nei.nih.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=znmeb@aracnet.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