From: Con Kolivas <kernel@kolivas.org>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] BFS CPU scheduler v0.450 with SMT nice support for linux-3.16
Date: Sat, 16 Aug 2014 15:40:13 +1000 [thread overview]
Message-ID: <2233658.OcMy7hG7Vc@hex> (raw)
This is to announce a resync and update of the Brain Fuck Scheduler,
version 0.450 for the latest stable linux kernel.
In addition to the usual round of fixes and changes to resync with mainline
changes, this release brings a new feature of configurable SMT nice support.
The configuration help follows to explain:
Enabling Hyperthreading on Intel CPUs decreases the effectiveness
of the use of 'nice' levels and different scheduling policies
(e.g. realtime) due to sharing of CPU power between hyperthreads.
SMT nice support makes each logical CPU aware of what is running on
its hyperthread siblings, maintaining appropriate distribution of
CPU according to nice levels and scheduling policies at the expense
of slightly increased overhead.
This code is based on my original idea from ten years ago discussed here:
http://lwn.net/Articles/73614/
A full discussion of the rationale and development follows here:
http://ck-hack.blogspot.com/2014/08/smthyperthreading-nice-and-scheduling.html
The patch against linux-3.16(.x) is available here:
http://ck.kolivas.org/patches/bfs/3.0/3.16/3.16-sched-bfs-450.patch
A -ck branded linux-3.16-ck1 patch is available here:
http://ck.kolivas.org/patches/3.0/3.16/3.16-ck1/
All patches available here:
http://ck.kolivas.org/patches
Code blog:
http://ck-hack.blogspot.com
Enjoy!
お楽しみください
--
-ck
next reply other threads:[~2014-08-16 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 5:40 Con Kolivas [this message]
2014-12-03 8:12 [ANNOUNCE] BFS CPU scheduler v0.450 with SMT nice support for linux-3.16 Hillf Danton
2014-12-07 20:26 ` Con Kolivas
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=2233658.OcMy7hG7Vc@hex \
--to=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.