From: Con Kolivas <kernel@kolivas.org>
To: linux-kernel@vger.kernel.org
Cc: axboe@fb.com
Subject: [ANNOUNCE] linux-4.7-ck5
Date: Fri, 23 Sep 2016 10:36:39 +1000 [thread overview]
Message-ID: <2474593.neva78N1XK@hex> (raw)
Announcing the latest release of the -ck patchset for improved responsiveness
and interactivity.
http://ck.kolivas.org/patches/4.0/4.7/4.7-ck5/
This is normally just a branded version of BFS with some different default
kernel options, however this version incorporates Jens Axboe's writeback
throttling patch version 7 which in my testing made a dramatic improvement to
behaviour under heavy write loads (no benchmarks.)
https://marc.info/?l=linux-block&m=147325975312628
A note about CPU scheduler cgroups - BFS does not support any of the cgroup
features but does implement a basic stub for the primary "CPU controller"
cgroup which creates the relevant cgroup filesystem but using it does nothing.
The reason for implementing this was that some applications now refuse to work
without it though they'll happily work with these stubs, even if they don't do
anything.
Enjoy!
お楽しみ下さい
--
-ck
next reply other threads:[~2016-09-23 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 0:36 Con Kolivas [this message]
2016-09-23 16:39 ` [ANNOUNCE] linux-4.7-ck5 Jens Axboe
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=2474593.neva78N1XK@hex \
--to=kernel@kolivas.org \
--cc=axboe@fb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox