From: Andrew Morton <akpm@osdl.org>
To: Phy Prabab <phyprabab@yahoo.com>
Cc: kernel@kolivas.org, linux-kernel@vger.kernel.org,
zwane@linuxpower.ca, wli@holomorphy.com
Subject: Re: [PATCH] Staircase Scheduler v6.3 for 2.6.7-rc2
Date: Mon, 7 Jun 2004 19:50:11 -0700 [thread overview]
Message-ID: <20040607195011.34f8e84e.akpm@osdl.org> (raw)
In-Reply-To: <20040607214034.27475.qmail@web51807.mail.yahoo.com>
Phy Prabab <phyprabab@yahoo.com> wrote:
>
> Also please note the degredation between
> 2.6.7-rc2-bk8-s63:
>
> A: 35.57user 38.18system 1:20.28elapsed 91%CPU
> B: 35.54user 38.40system 1:19.48elapsed 93%CPU
> C: 35.48user 38.28system 1:20.94elapsed 91%CPU
>
> Interesting how much more time is spent in both user
> and kernel space between the two kernels. Also note
> that 2.4.x exhibits even greater delta:
>
> A: 28.32user 29.51system 1:01.17elapsed 93%CPU
> B: 28.54user 29.40system 1:01.48elapsed 92%CPU
> B: 28.23user 28.80system 1:00.21elapsed 94%CPU
>
> Could anyone suggest a way to understand why the
> difference between the 2.6 kernels and the 2.4
> kernels?
This is very very bad.
It's a uniprocessor machine, yes?
Could you describe the workload a bit more? Is it something which others
can get their hands on?
It spends a lot of time in the kernel for a build system. I wonder why.
At a guess I'd say either a) you're hitting some path in the kernel which
is going for a giant and bogus romp through memory, trashing CPU caches or
b) your workload really dislikes run-child-first-after-fork or c) the page
allocator is serving up pages which your access pattern dislikes or d)
something else.
It's certainly interesting.
next prev parent reply other threads:[~2004-06-08 2:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 15:39 Con Kolivas
2004-06-06 16:59 ` Jan Killius
2004-06-06 17:40 ` Felipe Alfaro Solana
2004-06-06 22:58 ` Con Kolivas
2004-06-06 20:43 ` Prakash K. Cheemplavam
2004-06-06 22:55 ` Con Kolivas
2004-06-06 20:59 ` Felipe Alfaro Solana
2004-06-06 22:57 ` Con Kolivas
2004-06-06 23:47 ` Con Kolivas
2004-06-07 13:56 ` William Lee Irwin III
2004-06-07 13:57 ` William Lee Irwin III
2004-06-07 14:04 ` William Lee Irwin III
2004-06-07 14:07 ` William Lee Irwin III
2004-06-07 15:00 ` William Lee Irwin III
2004-06-07 15:11 ` William Lee Irwin III
2004-06-07 19:57 ` Phy Prabab
2004-06-07 21:12 ` Con Kolivas
2004-06-07 21:40 ` Phy Prabab
2004-06-07 21:34 ` Con Kolivas
2004-06-08 0:06 ` Phy Prabab
2004-06-07 22:08 ` Con Kolivas
2004-06-08 2:50 ` Andrew Morton [this message]
2004-06-08 3:02 ` Con Kolivas
2004-06-08 3:05 ` Nick Piggin
2004-06-08 1:07 ` Con Kolivas
2004-06-08 5:51 ` Phy Prabab
2004-06-08 5:42 ` Phy Prabab
2004-06-08 5:50 ` Zwane Mwaikambo
2004-06-29 11:10 ` Pavel Machek
2004-06-29 11:14 ` Con Kolivas
2004-06-29 12:05 ` Felipe Alfaro Solana
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=20040607195011.34f8e84e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phyprabab@yahoo.com \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®