![]() | |||||||||||||
Messages in this thread |
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||||
| Last update: 2006-07-07 05:29 [from the cache] ©2003-2008 | |||||||||||||