[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080129105104.d70f36ef.pj@sgi.com>
Date: Tue, 29 Jan 2008 10:51:04 -0600
From: Paul Jackson <pj@....com>
To: "Gregory Haskins" <ghaskins@...ell.com>
Cc: a.p.zijlstra@...llo.nl, mingo@...e.hu, dmitry.adamushko@...il.com,
rostedt@...dmis.org, menage@...gle.com, rientjes@...gle.com,
tong.n.li@...el.com, tglx@...utronix.de, akpm@...ux-foundation.org,
dhaval@...ux.vnet.ibm.com, vatsa@...ux.vnet.ibm.com,
sgrubb@...hat.com, linux-kernel@...r.kernel.org,
ebiederm@...ssion.com, nickpiggin@...oo.com.au
Subject: Re: scheduler scalability - cgroups, cpusets and load-balancing
Gregory wrote:
> This is correct. We have the balance policy polymorphically associated
> with each sched_class, and the CFS load-balancer and RT "load" (really,
> priority) balancer can coexist together at the same time and across
> arbitrary #s of cores
So ... we have the option of having all sched_classes coexist polymorphically.
That I didn't realize until this thread.
Now ... do we -want- to ?)
That is, what is the easiest kernel-user API to work with and understand?
Is it one where we essentially expose sched_class to user space, and let
them pick their sched_class, or pick none of the above (don't balance)?
Or is it one where, other than the special case my batch schedulers need
to not balance at all, we expose nothing more to user space, and provide
all sched_class load balancers to all sched_domains (other than those
not balanced at all)?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists