From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Daniel Egger <degger@fhm.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance of Ingo's O(1) scheduler on NUMA-Q
Date: Mon, 11 Feb 2002 09:39:07 -0800 [thread overview]
Message-ID: <400310000.1013449147@flay> (raw)
In-Reply-To: <1013181364.31423.9.camel@sonja>
In-Reply-To: <Pine.LNX.4.33.0202080021520.7544-100000@localhost.localdomain> <1013181364.31423.9.camel@sonja>
>> > Measuring kernel compile times on a 16 way NUMA-Q, adding Ingo's
>> > scheduler patch takes kernel compiles down from 47 seconds to 31
>> > seconds .... pretty impressive benefit.
>
>> cool! By the way, could you try a test-compile with a 'big' .config file?
>
> I'd assume that a 16way machine still taking 31s to compile the kernel
> is already having a 'big' config file.
It's a fairly normal config file, but the machine isn't feeling very
in touch with it's NUMAness, so it scales badly. If I only use one
quad (4 processsors), the same compile takes 47s.
M.
prev parent reply other threads:[~2002-02-11 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 15:05 [patch] O(1) scheduler, -J4 Ingo Molnar
2002-01-21 15:32 ` [patch] O(1) scheduler, -J4, 2.4.18-pre4 Ingo Molnar
2002-01-24 1:43 ` Ingo's O(1) scheduler vs. wait_init_idle Martin J. Bligh
2002-01-24 9:21 ` Ingo Molnar
2002-01-24 17:47 ` Martin J. Bligh
2002-01-24 19:59 ` Ingo Molnar
2002-01-26 17:19 ` Jesse Barnes
2002-01-25 23:07 ` Performance of Ingo's O(1) scheduler on 8 way NUMA-Q Martin J. Bligh
2002-02-07 13:08 ` Performance of Ingo's O(1) scheduler on NUMA-Q Martin J. Bligh
2002-02-07 23:23 ` Ingo Molnar
2002-02-08 15:15 ` Daniel Egger
2002-02-11 17:39 ` 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=400310000.1013449147@flay \
--to=martin.bligh@us.ibm.com \
--cc=degger@fhm.edu \
--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