From: Alex Shi <alex.shi@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Alex Shi <lkml.alex@gmail.com>,
rob@landley.net, mingo@redhat.com, peterz@infradead.org,
gregkh@linuxfoundation.org, andre.przywara@amd.com, rjw@sisk.pl,
paul.gortmaker@windriver.com, akpm@linux-foundation.org,
paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
pjt@google.com, vincent.guittot@linaro.org,
Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/18] sched: simplified fork, enable load average into LB and power awareness scheduling
Date: Fri, 14 Dec 2012 09:56:22 +0800 [thread overview]
Message-ID: <50CA8746.5050604@intel.com> (raw)
In-Reply-To: <20121213113549.GB31485@liondog.tnic>
On 12/13/2012 07:35 PM, Borislav Petkov wrote:
> On Thu, Dec 13, 2012 at 11:07:43AM +0800, Alex Shi wrote:
>>>> now, on the other hand, if you have two threads of a process that
>>>> share a bunch of data structures, and you'd spread these over 2
>>>> sockets, you end up bouncing data between the two sockets a lot,
>>>> running inefficient --> bad for power.
>>>
>>> Yeah, that should be addressed by the NUMA patches people are
>>> working on right now.
>>
>> Yes, as to balance/powersaving policy, we can tight pack tasks
>> firstly, then NUMA balancing will make memory follow us.
>>
>> BTW, NUMA balancing is more related with page in memory. not LLC.
>
> Sure, let's look at the worst and best cases:
>
> * worst case: you have memory shared by multiple threads on one node
> *and* working set doesn't fit in LLC.
>
> Here, if you pack threads tightly only on one node, you still suffer the
> working set kicking out parts of itself out of LLC.
>
> If you spread threads around, you still cannot avoid the LLC thrashing
> because the LLC of the node containing the shared memory needs to cache
> all those transactions. *In* *addition*, you get the cross-node traffic
> because the shared pages are on the first node.
>
> Major suckage.
>
> Does it matter? I don't know. It can be decided on a case-by-case basis.
> If people care about singlethread perf, they would likely want to spread
> around and buy in the cross-node traffic.
>
> If they care for power, then maybe they don't want to turn on the second
> socket yet.
>
> * the optimal case is where memory follows threads and gets spread
> around such that LLC doesn't get thrashed and cross-node traffic gets
> avoided.
>
> Now, you can think of all those other scenarios in between :-/
You are right. thanks for explanation! :)
Actually, what I went to say is that numa balancing target is pages in
different node memory, but of course, it may improve LLC performance.
>
> Thanks.
>
next prev parent reply other threads:[~2012-12-14 1:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 8:22 Alex Shi
2012-12-10 8:22 ` [PATCH 01/18] sched: select_task_rq_fair clean up Alex Shi
2012-12-11 4:23 ` Preeti U Murthy
2012-12-11 5:28 ` Alex Shi
2012-12-11 6:30 ` Preeti U Murthy
2012-12-11 11:53 ` Alex Shi
2012-12-12 5:26 ` Preeti U Murthy
2012-12-21 4:28 ` Namhyung Kim
2012-12-23 12:17 ` Alex Shi
2012-12-10 8:22 ` [PATCH 02/18] sched: fix find_idlest_group mess logical Alex Shi
2012-12-11 5:08 ` Preeti U Murthy
2012-12-11 5:29 ` Alex Shi
2012-12-11 5:50 ` Preeti U Murthy
2012-12-11 11:55 ` Alex Shi
2012-12-10 8:22 ` [PATCH 03/18] sched: don't need go to smaller sched domain Alex Shi
2012-12-10 8:22 ` [PATCH 04/18] sched: remove domain iterations in fork/exec/wake Alex Shi
2012-12-10 8:22 ` [PATCH 05/18] sched: load tracking bug fix Alex Shi
2012-12-10 8:22 ` [PATCH 06/18] sched: set initial load avg of new forked task as its load weight Alex Shi
2012-12-21 4:33 ` Namhyung Kim
2012-12-23 12:00 ` Alex Shi
2012-12-10 8:22 ` [PATCH 07/18] sched: compute runnable load avg in cpu_load and cpu_avg_load_per_task Alex Shi
2012-12-12 3:57 ` Preeti U Murthy
2012-12-12 5:52 ` Alex Shi
2012-12-13 8:45 ` Alex Shi
2012-12-21 4:35 ` Namhyung Kim
2012-12-23 11:42 ` Alex Shi
2012-12-10 8:22 ` [PATCH 08/18] sched: consider runnable load average in move_tasks Alex Shi
2012-12-12 4:41 ` Preeti U Murthy
2012-12-12 6:26 ` Alex Shi
2012-12-21 4:43 ` Namhyung Kim
2012-12-23 12:29 ` Alex Shi
2012-12-10 8:22 ` [PATCH 09/18] Revert "sched: Introduce temporary FAIR_GROUP_SCHED dependency for load-tracking" Alex Shi
2012-12-10 8:22 ` [PATCH 10/18] sched: add sched_policy in kernel Alex Shi
2012-12-10 8:22 ` [PATCH 11/18] sched: add sched_policy and it's sysfs interface Alex Shi
2012-12-10 8:22 ` [PATCH 12/18] sched: log the cpu utilization at rq Alex Shi
2012-12-10 8:22 ` [PATCH 13/18] sched: add power aware scheduling in fork/exec/wake Alex Shi
2012-12-10 8:22 ` [PATCH 14/18] sched: add power/performance balance allowed flag Alex Shi
2012-12-10 8:22 ` [PATCH 15/18] sched: don't care if the local group has capacity Alex Shi
2012-12-10 8:22 ` [PATCH 16/18] sched: pull all tasks from source group Alex Shi
2012-12-10 8:22 ` [PATCH 17/18] sched: power aware load balance, Alex Shi
2012-12-10 8:22 ` [PATCH 18/18] sched: lazy powersaving balance Alex Shi
2012-12-11 0:51 ` [PATCH 0/18] sched: simplified fork, enable load average into LB and power awareness scheduling Alex Shi
2012-12-11 12:10 ` Alex Shi
2012-12-11 15:48 ` Borislav Petkov
2012-12-11 16:03 ` Arjan van de Ven
2012-12-11 16:13 ` Borislav Petkov
2012-12-11 16:40 ` Arjan van de Ven
2012-12-12 9:52 ` Amit Kucheria
2012-12-12 13:55 ` Alex Shi
2012-12-12 14:21 ` Vincent Guittot
2012-12-13 2:51 ` Alex Shi
2012-12-12 14:41 ` Borislav Petkov
2012-12-13 3:07 ` Alex Shi
2012-12-13 11:35 ` Borislav Petkov
2012-12-14 1:56 ` Alex Shi [this message]
2012-12-12 1:14 ` 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=50CA8746.5050604@intel.com \
--to=alex.shi@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andre.przywara@amd.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.alex@gmail.com \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=rob@landley.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome