[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1201604243.28547.101.camel@lappy>
Date: Tue, 29 Jan 2008 11:57:22 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: linux-kernel <linux-kernel@...r.kernel.org>
Cc: Ingo Molnar <mingo@...e.hu>, vatsa <vatsa@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
Paul Jackson <pj@....com>,
Nick Piggin <nickpiggin@...oo.com.au>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Steve Grubb <sgrubb@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Gregory Haskins <ghaskins@...ell.com>,
Dmitry Adamushko <dmitry.adamushko@...il.com>,
"Li, Tong N" <tong.n.li@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Paul Menage <menage@...gle.com>,
David Rientjes <rientjes@...gle.com>
Subject: Re: scheduler scalability - cgroups, cpusets and load-balancing
Here I go, talking to myself..
On Tue, 2008-01-29 at 10:53 +0100, Peter Zijlstra wrote:
> My thoughts were to make stronger use of disjoint cpu-sets. cgroups and
> cpusets are related, in that cpusets provide a property to a cgroup.
> However, load_balance_monitor()'s interaction with sched domains
> confuses me - it might DTRT, but I can't tell.
>
> [ It looks to me it balances a group over the largest SD the current cpu
> has access to, even though that might be larger than the SD associated
> with the cpuset of that particular cgroup. ]
Hmm, with a bit more thought I think that does indeed DTRT. Because, if
the cpu belongs to a disjoint cpuset, the highest sd (with
load-balancing enabled) would be that. Right?
[ Just a bit of a shame we have all cgroups represented on each cpu. ]
Also, might be a nice idea to split the daemon up if there are indeed
disjoint sets - currently there is only a single daemon which touches
the whole system.
--
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