From: Nick Piggin <piggin@cyberone.com.au>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.0 batch scheduling, HT aware
Date: Tue, 23 Dec 2003 12:11:02 +1100 [thread overview]
Message-ID: <3FE79626.1060105@cyberone.com.au> (raw)
In-Reply-To: <200312231138.21734.kernel@kolivas.org>
Con Kolivas wrote:
>I've done a resync and update of my batch scheduling that is also hyper-thread
>aware.
>
>What is batch scheduling? Specifying a task as batch allows it to only use cpu
>time if there is idle time available, rather than having a proportion of the
>cpu time based on niceness.
>
>Why do I need hyper-thread aware batch scheduling?
>
>If you have a hyperthread (P4HT) processor and run it as two logical cpus you
>can have a very low priority task running that can consume 50% of your
>physical cpu's capacity no matter how high priority tasks you are running.
>For example if you use the distributed computing client setiathome you will
>be effectively be running at half your cpu's speed even if you run setiathome
>at nice 20. Batch scheduling for normal cpus allows only idle time to be used
>for batch tasks, and for HT cpus only allows idle time when both logical cpus
>are idle.
>
>This is not being pushed for mainline kernel inclusion, but the issue of how
>to prevent low priority tasks slowing down HT cpus needs to be considered for
>the mainline HT scheduler if it ever gets included. This patch provides a
>temporising measure for those with HT processors, and a demonstrative way to
>handle them in mainline.
>
I wonder how does Intel suggest we handle this problem? Batch scheduling
aside, I wonder how to do any sort of priorities at all? I think POWER5
can do priorities in hardware, that is the only sane way I can think of
doing it.
I think this patch is much too ugly to get into such an elegant scheduler.
No fault to you Con because its an ugly problem.
How about this: if a task is "delta" priority points below a task running
on another sibling, move it to that sibling (so priorities via timeslice
start working). I call it active unbalancing! I might be able to make it
fit if there is interest. Other suggestions?
next prev parent reply other threads:[~2003-12-23 1:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:38 [PATCH] 2.6.0 batch scheduling, HT aware Con Kolivas
2003-12-23 1:11 ` Nick Piggin [this message]
2003-12-23 1:24 ` Con Kolivas
2003-12-23 1:36 ` Nick Piggin
2003-12-23 2:42 ` Con Kolivas
2003-12-23 2:57 ` Nick Piggin
2003-12-23 3:15 ` Con Kolivas
2003-12-23 3:16 ` Con Kolivas
2003-12-26 23:03 ` Pavel Machek
2003-12-23 15:51 ` bill davidsen
2003-12-23 22:09 ` Con Kolivas
2003-12-30 0:35 ` bill davidsen
2004-01-02 20:10 ` Bill Davidsen
2003-12-26 22:56 ` Pavel Machek
2003-12-26 23:42 ` Con Kolivas
2003-12-26 23:49 ` Con Kolivas
2003-12-27 11:09 ` Pavel Machek
2003-12-27 11:15 ` Con Kolivas
2003-12-30 0:29 ` bill davidsen
2003-12-29 7:02 ` Nick Piggin
2003-12-29 12:49 ` Pavel Machek
2003-12-27 8:52 ` Mika Penttilä
2003-12-30 0:32 ` bill davidsen
2004-01-02 20:05 ` Bill Davidsen
2004-01-02 20:56 ` Davide Libenzi
2004-01-02 21:10 ` Valdis.Kletnieks
2004-01-02 23:34 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 1:59 Nakajima, Jun
2003-12-23 2:40 ` Nick Piggin
2003-12-23 5:33 Nakajima, Jun
2003-12-23 10:13 ` Nick Piggin
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=3FE79626.1060105@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=jun.nakajima@intel.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.