[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1337193010.27694.146.camel@twins>
Date: Wed, 16 May 2012 20:30:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Vincent Guittot <vincent.guittot@...aro.org>
Cc: paulmck@...ux.vnet.ibm.com, smuckle@...cinc.com, khilman@...com,
Robin.Randhawa@....com, suresh.b.siddha@...el.com,
thebigcorporation@...il.com, venki@...gle.com,
panto@...oniou-consulting.com, mingo@...e.hu, paul.brett@...el.com,
pdeschrijver@...dia.com, pjt@...gle.com, efault@....de,
fweisbec@...il.com, geoff@...radead.org, rostedt@...dmis.org,
tglx@...utronix.de, amit.kucheria@...aro.org,
linux-kernel <linux-kernel@...r.kernel.org>,
linaro-sched-sig@...ts.linaro.org,
Morten Rasmussen <Morten.Rasmussen@....com>,
Juri Lelli <juri.lelli@...il.com>
Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP
On Tue, 2012-05-15 at 17:35 +0200, Peter Zijlstra wrote:
> But really short, look at kernel/sched/core.c:default_topology[]
The reason I want to push this into the arch is that the current one
size fits all topology really doesn't fit.
On x86 there's stuff like the Intel Core2 Quad which is two dual-core
dies glued together resulting in a socket with 2 cache domains. And the
current topology simply cannot represent this.
There's the s390 'book' domain, which is now littering generic code.
And AMD Magny-Cours which has two nodes on a socket.
But I want to very much limit the arch interface so that we don't get
the current mess of arch maintainers having to guess at things like
SD_INIT_BOOK and what all these various random numbers in there mean.
--
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