From: Andrea Arcangeli <andrea@suse.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>, "Robert Love" <rml@tech9.net>,
"Oleg Drokin" <green@namesys.com>
Subject: Re: 23 second kernel compile (aka which patches help scalibility on NUMA)
Date: Sat, 9 Mar 2002 22:07:51 +0100 [thread overview]
Message-ID: <20020309220751.C13379@dualathlon.random> (raw)
In-Reply-To: <200203092044.43456.Dieter.Nuetzel@hamburg.de> <135154151.1015676353@[10.10.2.3]>
In-Reply-To: <135154151.1015676353@[10.10.2.3]>
On Sat, Mar 09, 2002 at 12:19:13PM -0800, Martin J. Bligh wrote:
> some other stuff as well. The -aa tree also seems to be
> incompatible (or rather, not trivially fixable) with the O(1)
> scheduler.
To apply the O(1) scheduler you only need to backout the dyn-sched and
numa-sched patches first (dyn-sched will be definitely obsoleted by the
O(1) scheduler, numa-sched should be changed like Mike described a few
weeks ago but probably O(1) will just work better than my current
numa-sched). There are no other changes to the scheduler, the
child-first is an optimization and parent-timeslice is an important
bugfix.
Andrea
next prev parent reply other threads:[~2002-03-10 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 19:44 23 second kernel compile (aka which patches help scalibility on NUMA) Dieter Nützel
2002-03-09 20:19 ` Martin J. Bligh
2002-03-09 21:07 ` Andrea Arcangeli [this message]
2002-03-10 9:26 ` Samuel Ortiz
2002-03-10 17:13 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 5:47 Martin J. Bligh
2002-03-09 16:43 ` Erik Andersen
2002-03-09 17:53 ` Martin J. Bligh
2002-03-09 18:37 ` Fabio Massimo Di Nitto
2002-03-11 18:23 ` Timothy D. Witham
2002-03-11 2:14 ` Andrea Arcangeli
2002-03-11 2:23 ` Rik van Riel
2002-03-11 4:12 ` Andrea Arcangeli
2002-03-11 10:45 ` Denis Vlasenko
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=20020309220751.C13379@dualathlon.random \
--to=andrea@suse.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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