From: Peter Zijlstra <peterz@infradead.org>
To: Phil Endecott <phil_wueww_endecott@chezphil.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nice and hyperthreading on atom
Date: Sat, 06 Sep 2008 18:31:28 +0200 [thread overview]
Message-ID: <1220718688.8687.19.camel@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1220715811849@dmwebmail.dmwebmail.chezphil.org>
On Sat, 2008-09-06 at 16:43 +0100, Phil Endecott wrote:
> Dear Experts,
>
> I have an ASUS Eee with an Atom processor, which has hyperthreading
> enabled. If I have two processes, one nice and the other normal, they
> each get 50% of the CPU time. Of course this is what you'd expect if
> the scheduler didn't understand that the two virtual processors are not
> really independent. I'd like to fix it.
>
> Google finds patches posted by Con Kolivas a looong time ago to address
> this. Can anyone tell me what has happened in the meantime? Maybe
> this feature is now in the kernel, but there's something I have to do
> to enable it (e.g. choose the right scheduler). Or maybe it never made
> it in, for some reason.
Assuming the hardware makes each 'virtual' cpu get a similar share of
the hardware resources, there is nothing the operating system can do.
The OS just sees two cpus, and its impossible to schedule two tasks of
different weight on two cpus so that execution time is fair and work is
conserved - this is called an infeasible weight distribution.
So unless the Atom has some interface to influence how the resources are
distributed between the execution contexts (for which Linux currently
lacks any and all support) there is nothing we can do.
next prev parent reply other threads:[~2008-09-06 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 15:43 Phil Endecott
2008-09-06 16:31 ` Peter Zijlstra [this message]
2008-09-06 16:42 ` Arjan van de Ven
2008-09-06 18:24 ` Phil Endecott
2008-09-06 18:30 ` Ulrich Drepper
2008-09-07 9:34 ` Peter Zijlstra
2008-09-07 13:58 ` Phil Endecott
2008-09-08 1:09 ` Bill Davidsen
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=1220718688.8687.19.camel@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil_wueww_endecott@chezphil.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