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: Thu, 19 May 2005 18:46:27 +0900	[thread overview]
Message-ID: <377362e105051902467cae323e@mail.gmail.com> (raw)
In-Reply-To: <200505191718.55615.kernel@kolivas.org>

But I would like a kernel to let boinc (the "nice=19" processes) fill
the idle time as much as possible.  The current kernel scheduler seems
very sensitive to low-nice (higher priority) processes.

How can I change this sensitivity?   I'm looking at kernel/sched.c,
but it's more complicated than a few years ago when I hacked this
before :) and that I'm using HT (SMP)..  Will you tell me any hint
where to modify, and/or what to take care of?  or any pointer to
proper resources on the Internet?

When I use gnome desktop with a system monitor applet, I see there's
always some idle part and top also shows the idle time on gnome even
if I don't run any specific applications besides system daemons and
gnome background processes.  However without gnome/X window, top shows
no or very small idle power (as a matter of course.)  So I want the
kernel to be less sensitive.  Maybe it will utilize more cpu power.

best regards,

On 5/19/05, Con Kolivas <kernel@kolivas.org> wrote:
> 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
> 


-- 
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/

  reply	other threads:[~2005-05-19  9:47 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 [this message]
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=377362e105051902467cae323e@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.