From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: dino@in.ibm.com, paulus@samba.org, akpm@osdl.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@osdl.org, mingo@elte.hu, hawkes@sgi.com
Subject: Re: [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
Date: Thu, 25 Aug 2005 00:02:29 +0000 [thread overview]
Message-ID: <430D0A95.30208@yahoo.com.au> (raw)
In-Reply-To: <20050824133107.2ca733c3.pj@sgi.com>
Paul Jackson wrote:
> So long as the cpuset code stops making any calls to partition_sched_domains()
> whatsoever, then we should be back where we were in 2.6.12, so far as the
> scheduler is concerned - right?
>
That's right - sorry I just meant disabling the dynamic sched
domains behaviour of the cpu_exclusive cpusets.
> I hope that the following (untested, unbuilt) patch, that I suggested
> in my "Mon, 22 Aug 2005 13:38:23 -0700" message best meets you
> suggestion above ... and I quote:
>
I apologise, I missed that patch you sent. I think it looks OK,
and that it looks like what I was thinking about.
We need to revert to a stable behaviour, however we can't risk
major surgery to get there.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: dino@in.ibm.com, paulus@samba.org, akpm@osdl.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@osdl.org, mingo@elte.hu, hawkes@sgi.com
Subject: Re: [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
Date: Thu, 25 Aug 2005 10:02:29 +1000 [thread overview]
Message-ID: <430D0A95.30208@yahoo.com.au> (raw)
In-Reply-To: <20050824133107.2ca733c3.pj@sgi.com>
Paul Jackson wrote:
> So long as the cpuset code stops making any calls to partition_sched_domains()
> whatsoever, then we should be back where we were in 2.6.12, so far as the
> scheduler is concerned - right?
>
That's right - sorry I just meant disabling the dynamic sched
domains behaviour of the cpu_exclusive cpusets.
> I hope that the following (untested, unbuilt) patch, that I suggested
> in my "Mon, 22 Aug 2005 13:38:23 -0700" message best meets you
> suggestion above ... and I quote:
>
I apologise, I missed that patch you sent. I think it looks OK,
and that it looks like what I was thinking about.
We need to revert to a stable behaviour, however we can't risk
major surgery to get there.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-08-25 0:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 8:04 [PATCH 2.6.13-rc6] cpu_exclusive sched domains on partial nodes temp fix Paul Jackson
2005-08-23 8:04 ` Paul Jackson
2005-08-23 8:10 ` Ingo Molnar
2005-08-23 8:10 ` Ingo Molnar
2005-08-23 15:07 ` Dinakar Guniguntala
2005-08-23 15:19 ` Dinakar Guniguntala
2005-08-24 0:19 ` John Hawkes
2005-08-24 0:19 ` John Hawkes
2005-08-24 11:15 ` [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix Paul Jackson
2005-08-24 11:15 ` Paul Jackson
2005-08-24 11:26 ` Dinakar Guniguntala
2005-08-24 11:38 ` Dinakar Guniguntala
2005-08-24 11:46 ` Paul Jackson
2005-08-24 11:46 ` Paul Jackson
2005-08-24 12:01 ` Nick Piggin
2005-08-24 12:01 ` Nick Piggin
2005-08-24 20:31 ` Paul Jackson
2005-08-24 20:31 ` Paul Jackson
2005-08-25 0:02 ` Nick Piggin [this message]
2005-08-25 0:02 ` Nick Piggin
2005-08-25 0:57 ` Paul Jackson
2005-08-25 0:57 ` Paul Jackson
2005-08-25 14:41 ` Dinakar Guniguntala
2005-08-25 14:53 ` Dinakar Guniguntala
2005-08-25 15:20 ` Paul Jackson
2005-08-25 15:20 ` Paul Jackson
2005-08-24 16:09 ` John Hawkes
2005-08-24 16:09 ` John Hawkes
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=430D0A95.30208@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=hawkes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=pj@sgi.com \
--cc=torvalds@osdl.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 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.