From: Phy Prabab <phyprabab@yahoo.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [PATCH] Staircase Scheduler v6.3 for 2.6.7-rc2
Date: Mon, 7 Jun 2004 14:40:34 -0700 (PDT) [thread overview]
Message-ID: <20040607214034.27475.qmail@web51807.mail.yahoo.com> (raw)
In-Reply-To: <200406080712.44759.kernel@kolivas.org>
OOOPPPSSSS....
I need to make a correction on my previous data. I
had inadvertantly turned off interactivity and also
increased the compute time to 100. I confirmed that
just setting interactivity off, does not solve my
problem:
2.6.7-rc3-s63 (0 @ /proc/sys/kernel/interactive):
A: 37.30user 40.56system 1:42.01elapsed 76%CPU
B: 37.29user 40.35system 1:23.87elapsed 92%CPU
C: 37.30user 40.56system 1:36.01elapsed 81%CPU
2.6.7-rc3-s63 (0 @ /proc/sys/kernel/interactive & 1
/proc/sys/kernel/compute):
A: 37.28user 40.36system 1:25.60elapsed 90%CPU
B: 37.22user 40.35system 1:22.17elapsed 94%CPU
C: 37.27user 40.35system 1:24.71elapsed 91%CPU
The question here, noticing that user and kernel time
are the same, where is the dead time coming from and
why is it sooooo much more deterministic with compute
time at 100 vs 10? Maybe I am misinterpreting the
data, but this suggests to me that something is going
awry (ping-pong, no settle, ???) within the kernl?
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?
Thank you for your time.
Phy
--- Con Kolivas <kernel@kolivas.org> wrote:
> On Tue, 8 Jun 2004 05:57, Phy Prabab wrote:
> > I have had a chance to test this patch.
>
> Thanks
>
> > I have a make
> > system that has presented 2.6 kernels with
> problems,
> > so I am using this as the test. Observations
> show
> > that turning off interactive is much more
> > deterministic:
> >
> > 2.6.7-rc2-bk8-s63:
> > echo 0 > /proc/sys/kernel/interactive
> >
> > 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
> >
> > 2.6.7-rc2-bk8-s63:
> > A: 35.32user 38.51system 1:26.47elapsed 85%CPU
> > B: 35.43user 38.35system 1:20.79elapsed 91%CPU
> > C: 35.61user 38.23system 1:25.00elapsed 86%CPU
> >
> > However, something is still slower than the 2.4.x
> > kernels:
> >
> > 2.4.23:
> > 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
> >
> > Nice work, as I can now turn off some
> functionality
> > within the kernel that is causing me some slow
> down.
>
> Glad to see it does what you require. Turning off
> "interactive" should still
> provide moderately good interactive performance at
> low to moderate loads, but
> is much stricter about cpu usage distribution as you
> can see.
>
> Cheers,
> Con
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
next prev parent reply other threads:[~2004-06-07 21:42 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 [this message]
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
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=20040607214034.27475.qmail@web51807.mail.yahoo.com \
--to=phyprabab@yahoo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--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®