All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tetsuji \"Maverick\" Rai" <tetsuji.rai@gmail.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HT scheduler: is it really correct? or is it feature of HT?
Date: Fri, 20 May 2005 01:08:38 +0900	[thread overview]
Message-ID: <377362e105051909085cea3357@mail.gmail.com> (raw)
In-Reply-To: <200505192123.24784.kernel@kolivas.org>

After several tests, I found the default value is the best also to me.
 Thanks Con for nice advises and hints on scheduler.   It's fun to
see/modify kernel source files.  But I think kernel isn't my higher
priority.

regards,

On 5/19/05, Con Kolivas <kernel@kolivas.org> wrote:
> On Thu, 19 May 2005 08:46 pm, Tetsuji "Maverick" Rai wrote:
> > I've done a temporary minor hacking, which tells kernel only the half
> > value of nice in all processes.  Actually idle percentage was lowered,
> > but the response of the main application became slower (as a matter of
> > course.)
> >
> > I'm not sure which is better..if possible I want to take advantages of
> > each one :)   Am I expecting too much?
> 
> Yes you are. Hyperthreading (currently depending on workload) only gives you
> on average 15-25% more cpu with multiple threads. You can't get something for
> nothing. Either the nice 0 task runs slower because a low priority task is
> bound to the sibling, or it runs at the same speed and the low priority task
> runs for less. If you want the nice 19 task to use more cpu run it at nice 0
> - because this is effectively what you are trying to do. If you want more cpu
> you need extra true physical cpus, not logical cores.
> 
> Your code does not do what you think it is doing either. If you want to change
> the bias between nice levels across logical cores search the code for where
> the value of sd->per_cpu_gain is set. It is currently set to 25% and you want
> to increase it (although as I said you will derive no real world benefit as
> your nice 0 task will just slow down).
> 
> Cheers,
> Con
> 


-- 
Luckiest in the world / Weapon of Mass Distraction
http://maverick6664.bravehost.com/
Aviation Jokes: http://www.geocities.com/tetsuji_rai/
Background: http://maverick.ns1.name/

      parent reply	other threads:[~2005-05-19 16:09 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
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 [this message]

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=377362e105051909085cea3357@mail.gmail.com \
    --to=tetsuji.rai@gmail.com \
    --cc=kernel@kolivas.org \
    --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 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.