Re: [PATCH] cpuset and sched domains: sched_load_balance flag

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Nick Piggin <nickpiggin@...>
Cc: <akpm@...>, <menage@...>, <linux-kernel@...>, <dino@...>, <cpw@...>, <mingo@...>
Date: Monday, October 1, 2007 - 2:15 pm

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
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] cpuset and sched domains: sched_load_balance flag, Paul Jackson, (Mon Oct 1, 2:15 pm)
[PATCH] cpuset decrustify update and validate masks, Paul Jackson, (Sun Sep 30, 6:44 am)