From: Chris Friesen <chris.friesen@genband.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Artem S. Tashkinov" <t.artem@lycos.com>, linux-kernel@vger.kernel.org
Subject: Re: HT (Hyper Threading) aware process scheduling doesn't work as it should
Date: Mon, 31 Oct 2011 12:59:16 -0600 [thread overview]
Message-ID: <4EAEF004.8070005@genband.com> (raw)
In-Reply-To: <20111030212644.GA7106@khazad-dum.debian.net>
On 10/30/2011 03:26 PM, Henrique de Moraes Holschuh wrote:
> On Sun, 30 Oct 2011, Artem S. Tashkinov wrote:
>> I've found out that even on Linux 3.0.8 the process scheduler doesn't correctly distributes
>> the load amongst virtual CPUs. E.g. on a 4-core system (8 total virtual CPUs) the process
>> scheduler often run some instances of four different tasks on the same physical CPU.
>
> Please check how your sched_mc_power_savings and sched_smt_power_savings
> tunables. Here's the doc from lesswats.org:
>
> 'sched_mc_power_savings' tunable under /sys/devices/system/cpu/ controls
> the Multi-core related tunable. By default, this is set to '0' (for
> optimal performance). By setting this to '1', under light load
> scenarios, the process load is distributed such that all the cores in a
> processor package are busy before distributing the process load to other
> processor packages.
>
> [...]
>
> 'sched_smt_power_savings' tunable under /sys/devices/system/cpu/
> controls the multi-threading related tunable. By default, this is set to
> '0' (for optimal performance). By setting this to '1', under light load
> scenarios, the process load is distributed such that all the threads in
> a core and all the cores in a processor package are busy before
> distributing the process load to threads and cores, in other processor
> packages.
I'm currently running Fedora 14 (2.6.35.14-97.fc14.x86_64 kernel) on an
i5 560M cpu. It's supposed to have 2 cores, with hyperthreading.
I created a tiny cpu burner program that just busy-loops. Running two
instances on my system they were always scheduled on separate physical
cpus regardless of the values in sched_mc_power_savings or
sched_smt_power_savings.
Running four instances they were always spread across all four "cpus".
With the newer 8-core chips (plus HT) in multi-socket boards with
package-level turbo-boost and NUMA memory access this is going to get
really interesting...
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-10-31 19:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 19:57 HT (Hyper Threading) aware process scheduling doesn't work as it should Artem S. Tashkinov
2011-10-30 21:26 ` Henrique de Moraes Holschuh
2011-10-30 21:51 ` Artem S. Tashkinov
2011-10-31 9:16 ` Henrique de Moraes Holschuh
2011-10-31 9:40 ` Artem S. Tashkinov
2011-10-31 11:58 ` Henrique de Moraes Holschuh
2011-11-01 4:14 ` Zhu Yanhai
2011-11-01 5:15 ` ffab ffa
2011-10-31 18:59 ` Chris Friesen [this message]
2011-11-01 6:01 ` Mike Galbraith
2011-10-30 22:12 ` Arjan van de Ven
2011-10-30 22:29 ` Artem S. Tashkinov
2011-10-31 3:19 ` Yong Zhang
2011-10-31 8:18 ` Artem S. Tashkinov
2011-10-31 10:06 ` Con Kolivas
2011-10-31 11:42 ` Mike Galbraith
2011-11-01 0:41 ` Con Kolivas
2011-11-01 0:58 ` Gene Heskett
2011-11-01 5:08 ` Mike Galbraith
2011-11-03 8:18 ` Ingo Molnar
2011-11-03 9:44 ` Artem S. Tashkinov
2011-11-03 10:29 ` Ingo Molnar
2011-11-03 12:42 ` Henrique de Moraes Holschuh
2011-11-03 13:06 ` Artem S. Tashkinov
2011-11-03 13:00 ` Mike Galbraith
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=4EAEF004.8070005@genband.com \
--to=chris.friesen@genband.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=t.artem@lycos.com \
/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.