Nick wrote:Hmmm ... this could be the key to this discussion. Nick - can two sched domains overlap? And if they do, what does that mean on any user or application behaviour. From the cpuset side - this patch handles overlap by joining the 'cpus' into one sched domain. If two cpusets with overlapping 'cpus' are both marked 'sched_load_balance', then this patch forms a single, combined sched domain. As best as I can tell, you and I are actually in agreement in the case that there is no overlap. If the several cpusets which have 'sched_load_balance' enabled have mutually disjoint 'cpus' (no overlap), then my patch forms exactly one sched domain for each such cpuset, having the same 'cpus'. The issue is the overlapping cases - are overlapping sched domains allowed, and if so, how do they affect user space? -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 -
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
