From: Paul Jackson <pj@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: suresh.b.siddha@intel.com, vatsa@in.ibm.com,
nickpiggin@yahoo.com.au, mingo@elte.hu, hawkes@sgi.com,
dino@in.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
ak@suse.de
Subject: Re: [PATCH 2.6.16-mm1 2/2] sched_domains: Allocate sched_groups dynamically
Date: Thu, 6 Jul 2006 22:26:32 -0700 [thread overview]
Message-ID: <20060706222632.2e403bd1.pj@sgi.com> (raw)
In-Reply-To: <20060706173607.F13512@unix-os.sc.intel.com>
Suresh wrote:
> It is quite possible that the kernel you are testing doesn't have multi-core
> scheduler domain. If so, then you may not run into this issue.
Aha - we have a winner.
CONFIG_SCHED_MC was not enabled in this kernel.
Now what I see matches what it should.
On a Hyper-Thread (but not Multi-Core) x86_64 system that I
tested with CONFIG_SCHED_MC enabled, your patch was required to
keep single-cpu cpu_exclusive cpusets from instantly locking
up the system.
On a Multi-Core (but not Hyper-Thread) IA64 Montecito system
that did -not- have CONFIG_SCHED_MC enabled, there is no
such problem with single-cpu cpu_exclusive cpusets in the
first place. It worked ok, even without the patch.
Thank-you.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2006-07-07 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 8:28 [PATCH 2.6.16-mm1 2/2] sched_domains: Allocate sched_groups dynamically Srivatsa Vaddagiri
2006-03-27 21:18 ` Siddha, Suresh B
2006-07-07 0:01 ` Paul Jackson
2006-07-07 0:08 ` Siddha, Suresh B
2006-07-07 0:34 ` Paul Jackson
2006-07-07 0:36 ` Siddha, Suresh B
2006-07-07 5:26 ` Paul Jackson [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=20060706222632.2e403bd1.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=hawkes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=vatsa@in.ibm.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.