From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Nick Piggin <piggin@cyberone.com.au>
Subject: [PATCH] 2.6.0 batch scheduling, HT aware
Date: Tue, 23 Dec 2003 11:38:21 +1100 [thread overview]
Message-ID: <200312231138.21734.kernel@kolivas.org> (raw)
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.
Patch available here:
http://ck.kolivas.org/patches/2.6/2.6.0/
Con
next reply other threads:[~2003-12-23 0:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:38 Con Kolivas [this message]
2003-12-23 1:11 ` [PATCH] 2.6.0 batch scheduling, HT aware Nick Piggin
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=200312231138.21734.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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