From: Dimitri Sivanich <sivanich@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patch for isolated scheduler domains
Date: Thu, 22 Jul 2004 23:13:49 -0500 [thread overview]
Message-ID: <20040723041349.GB15188@sgi.com> (raw)
In-Reply-To: <4100859C.9060409@yahoo.com.au>
On Fri, Jul 23, 2004 at 01:27:24PM +1000, Nick Piggin wrote:
> Cool. Have you actually tried running it? With Ingo's correction, it
> should work fine but I don't think anyone has tested this.
>
Yup, I've been running it on an Altix.
I've created a version for sched.c (all platform) which I'll be posting
soon. That will include code for both CONFIG_NUMA_SCHED and non
CONFIG_NUMA_SCHED configurations.
next prev parent reply other threads:[~2004-07-23 4:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 16:41 [RFC] Patch for isolated scheduler domains Dimitri Sivanich
2004-07-22 17:54 ` Ingo Molnar
2004-07-23 3:27 ` Nick Piggin
2004-07-23 4:13 ` Dimitri Sivanich [this message]
2004-07-23 4:29 ` Nick Piggin
2004-07-22 19:34 ` Paul Jackson
2004-07-23 20:03 ` Jesse Barnes
2004-07-24 5:26 ` Nick Piggin
2004-07-24 15:40 ` Jesse Barnes
2004-07-25 4:26 ` Nick Piggin
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=20040723041349.GB15188@sgi.com \
--to=sivanich@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.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