From: Con Kolivas <kernel@kolivas.org>
To: "Tetsuji \"Maverick\" Rai" <tetsuji.rai@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HT scheduler: is it really correct? or is it feature of HT?
Date: Thu, 19 May 2005 17:18:55 +1000 [thread overview]
Message-ID: <200505191718.55615.kernel@kolivas.org> (raw)
In-Reply-To: <377362e1050518235812f1cbbb@mail.gmail.com>
On Thu, 19 May 2005 04:58 pm, Tetsuji "Maverick" Rai wrote:
> On 5/19/05, Con Kolivas <kernel@kolivas.org> wrote:
> > ------------snip---------------
> > Hyperthread sibling cpus share cpu power. If you let a nice 19 task run
> > full power on the sibling cpu of a nice 0 task it will drain performance
> > from the nice 0 task and make it run approximately 40% slower. The only
> > way around this is to temporarily make the sibling run idle so that a
> > nice 0 task gets the appropriate proportion of cpu resources compared to
> > a nice 19 task. It is intentional and quite unique to the linux cpu
> > scheduler as far as I can tell. On any other scheduler or OS a nice 19
> > "background" task will make your machine run much slower.
> >
> Thanks. I understood it's a feature of linux kernel and am satisfied
> with it. Actually on Windows xp my application sometimes slows down
> maybe due to inpropoer scheduler.
Well I invented it so it's very unlikely that Windows* will have it (?yet) :D
Cheers,
Con
next prev parent reply other threads:[~2005-05-19 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 18:42 HT scheduler: is it really correct? or is it feature of HT? Tetsuji "Maverick" Rai
2005-05-18 21:56 ` Con Kolivas
2005-05-19 6:58 ` Tetsuji "Maverick" Rai
2005-05-19 7:18 ` Con Kolivas [this message]
2005-05-19 9:46 ` Tetsuji "Maverick" Rai
2005-05-19 10:46 ` Tetsuji "Maverick" Rai
2005-05-19 11:23 ` Con Kolivas
2005-05-19 11:31 ` Tetsuji "Maverick" Rai
2005-05-19 12:12 ` Tetsuji "Maverick" Rai
2005-05-19 16:08 ` Tetsuji "Maverick" Rai
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=200505191718.55615.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tetsuji.rai@gmail.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.