From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
paulus@samba.org, mingo@elte.hu, hawkes@sgi.com, dino@in.ibm.com
Subject: Re: [PATCH 2.6.13-rc7 2/2] completely disable cpu_exclusive sched domain
Date: Fri, 26 Aug 2005 11:32:34 +1000 [thread overview]
Message-ID: <430E7132.9060800@yahoo.com.au> (raw)
In-Reply-To: <20050825194756.7341.83327.sendpatchset@jackhammer.engr.sgi.com>
Paul Jackson wrote:
> At the suggestion of Nick Piggin and Dinakar, totally disable
> the facility to allow cpu_exclusive cpusets to define dynamic
> sched domains in Linux 2.6.13, in order to avoid problems
> first reported by John Hawkes (corrupt sched data structures
> and kernel oops).
>
> This has been built for ppc64, i386, ia64, x86_64, sparc, alpha.
> It has been built, booted and tested for cpuset functionality
> on an SN2 (ia64).
>
> Dinakar or Nick - could you verify that it for sure does avoid
> the problems Hawkes reported. Hawkes is out of town, and I don't
> have the recipe to reproduce what he found.
>
Thanks Paul, I was never able to reproduce the problem, but
I'm sure Dinakar should be able to test.
Acked-by: Nick Piggin <npiggin@suse.de>
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2005-08-26 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 19:47 [PATCH 2.6.13-rc7 1/2] undo partial cpu_exclusive sched domain disabling Paul Jackson
2005-08-25 19:47 ` [PATCH 2.6.13-rc7 2/2] completely disable cpu_exclusive sched domain Paul Jackson
2005-08-26 1:32 ` Nick Piggin [this message]
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=430E7132.9060800@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox