From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HT (Hyper Threading) aware process scheduling doesn't work as it should
Date: Mon, 31 Oct 2011 09:58:17 -0200 [thread overview]
Message-ID: <20111031115817.GA20448@khazad-dum.debian.net> (raw)
In-Reply-To: <574299906.69412.1320054001912.JavaMail.mail@webmail05>
On Mon, 31 Oct 2011, Artem S. Tashkinov wrote:
> > On Oct 31, 2011, Henrique de Moraes Holschuh wrote:
> >
> > On Sun, 30 Oct 2011, Artem S. Tashkinov wrote:
> > > > Please make sure both are set to 0. If they were not 0 at the time you
> > > > ran your tests, please retest and report back.
> > >
> > > That's 0 & 0 for me.
> >
> > How idle is your system during the test?
>
> load average: 0.00, 0.00, 0.00
I believe cpuidle will interfere with the scheduling in that case. Could
you run your test with higher loads (start with one, and go up to eight
tasks that are CPU-hogs, measuring each step)?
> I have to insist that people conduct this test on their own without trusting my
> words. Probably there's something I overlook or don't fully understand but from
What you should attempt to do is to give us a reproducible test case. A
shell script or C/perl/python/whatever program that when run clearly shows
the problem you're complaining about on your system. Failing that, a very
detailed description (read: step by step) of how you're testing things.
I can't see anything wrong in my X5550 workstation (4 cores, 8 threads,
single processor, i.e. not NUMA) running 3.0.8.
> what I see, there's a serious issue here (at least Microsoft XP and 7 work exactly
So far it looks like that, since your system is almost entirely idle, it
could be trying to minimize task-run latency by scheduling work to the few
cores/threads that are not in deep sleep (they take time to wake up, are
often cache-cold, etc).
Please use tools/power/x86/turbostat to track core usage and idle-states
instead of top/htop. That might give you better information, and I
think you will appreciate getting to know that tool. Note: turbostat
reports *averages* for each thread.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2011-10-31 11:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 19:57 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 [this message]
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
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=20111031115817.GA20448@khazad-dum.debian.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome