From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dimitri Sivanich <sivanich@sgi.com>
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: Fri, 23 Jul 2004 04:29:05 +0000 [thread overview]
Message-ID: <41009411.1080401@yahoo.com.au> (raw)
In-Reply-To: <20040723041349.GB15188@sgi.com>
Dimitri Sivanich wrote:
> 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.
>
Great.
> 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.
Sorry to throw a spanner in the works, but could you have a look
at the "[PATCH] consolidate sched domains" I just sent in, and
see if you can work on top of that.
I really should have done that patch earlier :\
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dimitri Sivanich <sivanich@sgi.com>
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: Fri, 23 Jul 2004 14:29:05 +1000 [thread overview]
Message-ID: <41009411.1080401@yahoo.com.au> (raw)
In-Reply-To: <20040723041349.GB15188@sgi.com>
Dimitri Sivanich wrote:
> 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.
>
Great.
> 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.
Sorry to throw a spanner in the works, but could you have a look
at the "[PATCH] consolidate sched domains" I just sent in, and
see if you can work on top of that.
I really should have done that patch earlier :\
next prev parent reply other threads:[~2004-07-23 4:29 UTC|newest]
Thread overview: 16+ 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 16:41 ` Dimitri Sivanich
2004-07-22 17:54 ` Ingo Molnar
2004-07-22 17:54 ` Ingo Molnar
2004-07-23 3:27 ` Nick Piggin
2004-07-23 3:27 ` Nick Piggin
2004-07-23 4:13 ` Dimitri Sivanich
2004-07-23 4:13 ` Dimitri Sivanich
2004-07-23 4:29 ` Nick Piggin [this message]
2004-07-23 4:29 ` Nick Piggin
2004-07-22 19:34 ` Paul Jackson
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=41009411.1080401@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sivanich@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.