public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 07:56:13 +1000	[thread overview]
Message-ID: <200505190756.16413.kernel@kolivas.org> (raw)
In-Reply-To: <377362e10505181142252ec930@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]

On Thu, 19 May 2005 04:42, Tetsuji "Maverick" Rai wrote:
> I'm wondering linux kernel's HT support is correct or not, or whether
> it's a feature of P4 HT.
>
> I'm running boinc/seti in the background with nice=19 on my P4 2.8G HT
> enabled linux box, kernel 2.6.11.9, where SMT/HT is enabled.
>
> I often watch system monitor applet on gnome desktop or top command in
> a termianl window and see when no other applications than boinc is
> running, boinc takes full power of both virtual cpus.   It is designed
> to run to "fill" the idle power of the cpu(s).   However any
> application is running, there is always some "idle" part appears on
> virtual cpus, hence it looks like it wastes up to half of cpu power as
> "idle."
>
> For ex, see this "top" result while a vmware is running.   (HT is
> enabled)  setiathome-4.7(blah--) are the background boinc applications
> with nice=19.

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.

Cheers,
Con

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-18 21:56 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 [this message]
2005-05-19  6:58   ` Tetsuji "Maverick" Rai
2005-05-19  7:18     ` Con Kolivas
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=200505190756.16413.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox