Bug 12054 - exclusive cpusets are not causing unique root-domains
Summary: exclusive cpusets are not causing unique root-domains
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Haskins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-17 07:02 UTC by Greg Haskins
Modified: 2008-11-24 08:06 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.28-rc1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Greg Haskins 2008-11-17 07:02:20 UTC
On Mon, 2008-11-03 at 15:07 -0600, Dimitri Sivanich wrote:
>   
> >> When load balancing gets switched off for a set of cpus via the
> >> sched_load_balance flag in cpusets, those cpus wind up with the
> >> globally defined def_root_domain attached.  The def_root_domain is
> >> attached when partition_sched_domains calls detach_destroy_domains().
> >> A new root_domain is never allocated or attached as a sched domain
> >> will never be attached by __build_sched_domains() for the non-load
> >> balanced processors.
> >>
> >> The problem with this scenario is that on systems with a large number
> >> of processors with load balancing switched off, we start to see the
> >> cpupri->pri_to_cpu->lock in the def_root_domain becoming contended.
> >> This starts to become much more apparent above 8 waking RT threads
> >> (with each RT thread running on it's own cpu, blocking and waking up
> >> continuously).
> >>
Comment 1 Greg Haskins 2008-11-24 08:05:17 UTC
This issue has been fixed in upstream via commit

f29c9b1ccb52904ee442a933cf3dee628f9f4e62
Comment 2 Greg Haskins 2008-11-24 08:06:12 UTC
Dimitri, please reopen if you find that the issue still exists.

Note You need to log in before you can comment on or make changes to this bug.