public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Patrick McFarland <unknown@panax.com>, linux-kernel@vger.kernel.org
Subject: Re: Which is better at vm, and why? 2.2 or 2.4
Date: Sat, 13 Oct 2001 14:29:26 -0700	[thread overview]
Message-ID: <20011013142926.B28547@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011013130228.E249@localhost> <Pine.LNX.4.10.10110131305490.17521-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10110131305490.17521-100000@coffee.psychology.mcmaster.ca>

On Sat, Oct 13, 2001 at 01:48:05PM -0400, Mark Hahn wrote:
> > Now, the great kernel hacker, ac, said that 2.2 is better at vm in low
> > memory situations than 2.4 is. Why is this? Why hasnt someone fixed the 2.4
> > code? 
> 
> not to slight TGKH AC, but he's also the 2.2 maintainer; perhaps there's 
> some paternal protectiveness there ;)
> 
> my test for VM is to compile a kernel on my crappy old BP6 with mem=64m;
> I use a dedicated partition with a fresh ext2, unpack the same source tree,
> make -j2 7 times, drop 1 outlier, and average:
> 
> 2.2.19: 584.462user 57.492system 385.112elapsed 166.5%CPU
> 2.4.12: 582.318user 40.535system 337.093elapsed 184.5%CPU
>

Is this:
> 2.2.19: 
584.462user 
57.492system 
385.112elapsed 
166.5%CPU

> 2.4.12: 
582.318user 
40.535system 
337.093elapsed 
184.5%CPU

???

If so, then 2.4.12 won on user, system and elapsed.  What's with the CPU
percentage?  Are you on a dual system?

> notice that elapsed is noticably faster even than the 1+17 second
> benefit to user and system times.  Rik's VM seems to be slightly

No, that's Andrea's VM (since 2.4.10pre11).  Rik's is in 2.4.xx-ac.

Mike

  reply	other threads:[~2001-10-13 21:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 17:02 Which is better at vm, and why? 2.2 or 2.4 Patrick McFarland
2001-10-13 17:16 ` Alan Cox
2001-10-13 18:06   ` M. Edward Borasky
2001-10-13 18:17     ` Patrick McFarland
2001-10-13 18:29       ` Rik van Riel
2001-10-13 18:42         ` Patrick McFarland
2001-10-13 18:53           ` Patrick McFarland
2001-10-13 18:58             ` Rik van Riel
2001-10-13 19:04               ` Patrick McFarland
2001-10-13 19:10                 ` Rik van Riel
2001-10-13 19:28             ` Wilson
2001-10-13 20:12               ` [solid]
2001-10-13 20:21               ` Patrick McFarland
2001-10-13 19:17           ` Rik van Riel
2001-10-13 18:37       ` M. Edward Borasky
2001-10-20  0:38     ` Daniel Phillips
2001-10-20  1:05       ` Robert Love
2001-10-20 19:56         ` Mike Fedyk
2001-10-20 20:03           ` Robert Love
2001-10-13 17:48 ` Mark Hahn
2001-10-13 21:29   ` Mike Fedyk [this message]
2001-10-13 21:47     ` Mark Hahn
     [not found] <20011013132327.F249@localhost>
     [not found] ` <E15sSey-0003Jf-00@the-village.bc.nu>
2001-10-13 17:33   ` Patrick McFarland
     [not found]     ` <E15sSti-0003ME-00@the-village.bc.nu>
2001-10-13 17:49       ` Patrick McFarland

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=20011013142926.B28547@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=unknown@panax.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