From: Igor Chudov <ichudov@gmail.com>
To: Andreas Mohr <andi@lisas.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading on 4 core CPU DECREASES performance???
Date: Wed, 28 Oct 2009 16:11:51 -0500 [thread overview]
Message-ID: <e86b7d350910281411k6dfb260dlfce76e260c797a9@mail.gmail.com> (raw)
In-Reply-To: <20091028204628.GA8519@rhlx01.hs-esslingen.de>
On Wed, Oct 28, 2009 at 3:46 PM, Andreas Mohr <andi@lisas.de> wrote:
>> I would like to know how can I make the scheduler to prefer to spread
>> the tasks across physical cores as opposed to bundling two on one core
>> and leaving some cores idle.
>
> Did you have /sys/devices/system/cpu/sched_smt_power_savings activated?
Andreas, no, I did not have it activated, it was set to 0. I did check
it before and double checked it now.
next prev parent reply other threads:[~2009-10-28 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 19:24 Hyperthreading on 4 core CPU DECREASES performance??? Igor Chudov
2009-10-28 20:46 ` Andreas Mohr
2009-10-28 21:11 ` Igor Chudov [this message]
2009-10-28 22:24 ` Alan Cox
2009-10-29 0:00 ` Igor Chudov
2009-10-29 0:44 ` Ben Gamari
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=e86b7d350910281411k6dfb260dlfce76e260c797a9@mail.gmail.com \
--to=ichudov@gmail.com \
--cc=andi@lisas.de \
--cc=linux-kernel@vger.kernel.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