From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling changes in -mm tree
Date: Sun, 20 Mar 2005 09:00:33 -0800 [thread overview]
Message-ID: <533200000.1111338032@[10.10.2.4]> (raw)
In-Reply-To: <20050319140754.23d76496.akpm@osdl.org>
--Andrew Morton <akpm@osdl.org> wrote (on Saturday, March 19, 2005 14:07:54 -0800):
> "Martin J. Bligh" <mbligh@aracnet.com> wrote:
>>
>> I don't think these are doing much for performance. Or at least
>> *something* in your tree isn't ...
>>
>> Kernbench:
>> Elapsed System User CPU
>> elm3b67 2.6.11 50.24 146.60 1117.61 2516.67
>> elm3b67 2.6.11-mm1 52.27 141.14 1099.91 2374.33
>> elm3b67 2.6.11-mm2 51.88 142.41 1104.85 2403.67
>> elm3b67 2.6.11-mm4 51.23 145.04 1100.70 2431.00
>>
>> (elm3b67 is a 16x x440 ia32 NUMA system + HT)
>
> Sounds like the CPU scheduler, yes
>
>> Is there an easy way to just test those sched changes alone?
>
> Nick has tossed out and redone all the scheduler patches from -mm4, but I
> assume it's all pretty much the same.
>
> At http://www.zip.com.au/~akpm/linux/patches/stuff/mbligh.gz is a rollup
> (against 2.6.12-rc1) of
Kernbench:
Elapsed System User CPU
elm3b67 2.6.12-rc1 49.02 147.91 1105.49 2556.00
elm3b67 mbligh 52.30 142.24 1105.83 2385.33
That doesn't seem like an improvement ;-) (last run is just adding above patch)
I'll try to get you results on a couple more machines, but I'm fighting
with the test harness to get it to behave (plus I now have to rerun all
the tests with CONFIG_BROKEN turned on to get CONFIG_SCSI_QLOGIC_ISP to
work).
M.
prev parent reply other threads:[~2005-03-20 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 16:18 Martin J. Bligh
2005-03-19 22:07 ` Andrew Morton
2005-03-20 17:00 ` Martin J. Bligh [this message]
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='533200000.1111338032@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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®