mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Philip Martin <philip@codematters.co.uk>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <piggin@cyberone.com.au>
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Mon, 2 Feb 2004 19:46:26 -0800	[thread overview]
Message-ID: <20040202194626.191cbb95.akpm@osdl.org> (raw)
In-Reply-To: <87oesieb75.fsf@codematters.co.uk>

Philip Martin <philip@codematters.co.uk> wrote:
>
> My test is a software build of about 200 source files (written in C)
>  that I usually build using "nice make -j4".  Timing the build on
>  2.4.24 I typically get something like
> 
>  242.27user 81.06system 2:44.18elapsed 196%CPU (0avgtext+0avgdata 0maxresident)k
>  0inputs+0outputs (1742270major+1942279minor)pagefaults 0swaps
> 
>  and on 2.6.1 I get
> 
>  244.08user 116.33system 3:27.40elapsed 173%CPU (0avgtext+0avgdata 0maxresident)k
>  0inputs+0outputs (0major+3763670minor)pagefaults 0swaps

I didn't notice the increase in system time.

Could you generate a kernel profile?  Add `profile=1' to the kernel boot
command line and run:

sudo readprofile -r
sudo readprofile -M10
time make -j4
readprofile -n -v -m /boot/System.map | sort -n +2 | tail -40 | tee ~/profile.txt >&2

on both 2.4 and 2.6?  Make sure the System.map is appropriate to the
currently-running kernel.



  parent reply	other threads:[~2004-02-03  3:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 21:34 Philip Martin
2004-02-01 23:11 ` Andrew Morton
2004-02-01 23:42   ` Philip Martin
2004-02-01 23:52   ` Nick Piggin
2004-02-02  0:51     ` Philip Martin
2004-02-02  5:15       ` Nick Piggin
2004-02-02  8:58         ` Nick Piggin
2004-02-02 18:36           ` Philip Martin
2004-02-02 23:36             ` Nick Piggin
2004-02-02 23:49               ` Andrew Morton
2004-02-03  1:01                 ` Philip Martin
2004-02-03  3:02                   ` Nick Piggin
2004-02-03 16:44                     ` Philip Martin
2004-02-03  0:34               ` Philip Martin
2004-02-03  3:52                 ` Nick Piggin
2004-02-02 18:08         ` Philip Martin
2004-02-03  3:46 ` Andrew Morton [this message]
2004-02-03 16:46   ` Philip Martin
2004-02-03 21:29     ` Andrew Morton
2004-02-03 21:53       ` Philip Martin
2004-02-04  5:48         ` Nick Piggin
2004-02-04 17:50           ` Philip Martin
2004-02-04 23:38             ` Philip Martin
2004-02-05  2:49               ` Nick Piggin
2004-02-05 14:27                 ` Philip Martin
2004-02-14  0:10       ` Philip Martin
2004-02-03  6:55 Samium Gromoff
2004-02-03  7:07 ` Andrew Morton
2004-02-03  7:52   ` Samium Gromoff
2004-02-03  7:57     ` Nick Piggin
2004-02-03 15:58       ` Valdis.Kletnieks
2004-02-03  7:13 ` Nick Piggin

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=20040202194626.191cbb95.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philip@codematters.co.uk \
    --cc=piggin@cyberone.com.au \
    /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

Powered by JetHome