From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
efault@gmx.de, pjt@google.com
Subject: Re: Re: HT (Hyper Threading) aware process scheduling doesn't work as it should
Date: Thu, 3 Nov 2011 09:44:05 +0000 (GMT) [thread overview]
Message-ID: <1758553229.334475.1320313445172.JavaMail.mail@webmail11> (raw)
In-Reply-To: 20111103081835.GA9330@elte.hu
> On Nov 3, 2011, Ingo Molnar wrote:
>
> If sched_mc is set to zero then this looks like a serious load
> balancing bug - you are perfectly right that we should balance
> between physical packages first and ending up with the kind of
> asymmetry you describe for any observable length is a bug.
>
> You have not outlined your exact workload - do you run a simple CPU
> consuming loop with no sleeping done whatsoever, or something more
> complex?
>
> Peter, Paul, Mike, any ideas?
Actually I am just running 4 copies of bzip2 compressor (< /dev/zero > /dev/null).
A person named ffab ffa said ( http://lkml.org/lkml/2011/11/1/11 ) that I probably
misunderstand/misinterpret physical cores. He says that cores thread siblings on
e.g., Intel Core 2600K are 0-4, 1-5, 2-6 and 3-7
and when I am running this test I have the following VCPUs distribution:
1, 6, 7, 8 (0-4, 1-5, 2-6, 7-8 - all four physical cores loaded)
1, 2, 7, 8 (0-4, 1-5, 2-6, 7-8 - all four physical cores loaded)
According to the cores thread siblings distribution the HT aware process scheduler
indeed works correctly.
However sometimes I see this picture:
3, 4, 5, 6 (2-6, 1-5, 2-6, 7-8 - three physical cores loaded)
So, now the question is whether VCPUs quite an illogical enumeration is good for
power users as I highly doubt that 0-4, 1-5, 2-6 and 3-7 order can be easily
remembered and grasped. Besides neither top, not htop are HT aware so just by
looking at their output it gets very difficult to see and understand if the process
scheduler works as it should.
next prev parent reply other threads:[~2011-11-03 9:44 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
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 [this message]
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=1758553229.334475.1320313445172.JavaMail.mail@webmail11 \
--to=t.artem@lycos.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox