From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <piggin@cyberone.com.au>,
"Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v10
Date: Wed, 3 Sep 2003 11:55:03 +1000 [thread overview]
Message-ID: <200309031155.04056.kernel@kolivas.org> (raw)
In-Reply-To: <3F552CBB.1060906@cyberone.com.au>
On Wed, 3 Sep 2003 09:50, Nick Piggin wrote:
> Martin J. Bligh wrote:
> >>>Not convinced of that - mm performs worse than mainline for me.
> >>
> >>Well, one of Con's patches caused a lot of idle time on volanomark.
> >>The reason for the change was unclear. I guess either a fairness or
> >>wakeup latency change (yes, it was a very scientific process, ahem).
> >>
> >>Anyway, in the process of looking at the load balancing, we found
> >>and fixed a problem (although it might now possibly over balance).
> >>This did cure most of the idle problems.
> >>
> >>So it could just be small changes causing things to go out of whack.
> >>I will try to get better data after (if ever) the thing is working
> >>nicely on the desktop.
> >
> >I think Con and I worked out that the degredations I was seeing
> >(on kernbench and SDET) were due to (in his words) "my hacks throwing the
> >cc cpu hogs onto the expired array more frequently".
>
> This didn't explain the huge idle time increases on volanomark and
> SPECjbb I think.
Yeah this was before the profile showed it to be idle time, and before I
isolated it to Ingo's A3 patch.
Con
next prev parent reply other threads:[~2003-09-03 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 6:31 [PATCH] Nick's scheduler policy v10 Nick Piggin
2003-08-31 20:20 ` Martin J. Bligh
2003-08-31 20:41 ` Martin J. Bligh
2003-09-01 1:47 ` Nick Piggin
2003-09-01 18:31 ` Martin J. Bligh
2003-09-02 8:04 ` Nick Piggin
2003-09-02 14:57 ` Martin J. Bligh
2003-09-02 23:50 ` Nick Piggin
2003-09-03 1:55 ` Con Kolivas [this message]
2003-09-01 1:44 ` Nick Piggin
2003-09-04 22:55 ` bill davidsen
2003-09-04 23:27 ` Mike Fedyk
2003-09-05 3:41 ` Bill Davidsen
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=200309031155.04056.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--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