From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu
Subject: Re: Performance of Ingo's O(1) scheduler on NUMA-Q
Date: Thu, 07 Feb 2002 05:08:43 -0800 [thread overview]
Message-ID: <241920000.1013087323@flay> (raw)
In-Reply-To: <23350000.1012000033@flay>
In-Reply-To: <Pine.LNX.4.33.0201211626030.12418-100000@localhost.localdomain> <119440000.1011836623@flay> <23350000.1012000033@flay>
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.
Mike Kravetz is working on NUMA additions to Ingo's scheduler
which should give further improvements.
Martin.
next prev parent reply other threads:[~2002-02-07 21:12 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 ` Martin J. Bligh [this message]
2002-02-07 23:23 ` Performance of Ingo's O(1) scheduler on NUMA-Q Ingo Molnar
2002-02-08 15:15 ` Daniel Egger
2002-02-11 17:39 ` Martin J. Bligh
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=241920000.1013087323@flay \
--to=martin.bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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