All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael wang <wangyun@linux.vnet.ibm.com>
To: Alex Shi <alex.shi@linaro.org>, Mike Galbraith <efault@gmx.de>
Cc: mingo@redhat.com, peterz@infradead.org, morten.rasmussen@arm.com,
	vincent.guittot@linaro.org, daniel.lezcano@linaro.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched: select_idle_sibling macro optimize
Date: Fri, 17 Jan 2014 11:15:32 +0800	[thread overview]
Message-ID: <52D8A054.5030203@linux.vnet.ibm.com> (raw)
In-Reply-To: <52D891FB.9020308@linaro.org>

On 01/17/2014 10:14 AM, Alex Shi wrote:
[snip]
>>
>> When is that gonna happen?
> 
> I had seen this in a Intel platform, you may have both CPU domain and MC
> domain layer, because the domain flag is different, then they can not be
> merged. and then the CPU domain just has one group.

CPU and MC are different domains, isn't it?

General should like:

CPU	cpu0				cpu1
MC	core0		core1		core0		core1
SMT	cpu 0	cpu 1	cpu 2	cpu 3	cpu 4	cpu 5	cpu 6	cpu 7

So for cpu0:

CPU	sg0:cpu0,1,2,3	sg1:cpu4,5,6,7
MC	sg0:cpu0,1	sg1:cpu2,3
SMT	sg0:cpu0	sg1:cpu1

If one domain only have one group, that's sounds really a weird topology...

Regards,
Michael Wang

>>
>> -Mike
>>
>>
> 
> 


  reply	other threads:[~2014-01-17  3:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 14:23 [RFC PATCH] sched: select_idle_sibling macro optimize Alex Shi
2014-01-16 13:13 ` Alex Shi
2014-01-16 13:52   ` Mike Galbraith
2014-01-17  2:14     ` Alex Shi
2014-01-17  3:15       ` Michael wang [this message]
2014-01-17  3:36       ` Mike Galbraith
2014-01-17  5:40         ` Alex Shi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D8A054.5030203@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=alex.shi@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.