From: Omar Sandoval <osandov@osandov.com>
To: linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@fb.com>, kernel-team@fb.com
Subject: [PATCH v2 0/5] kyber: better heuristics
Date: Thu, 27 Sep 2018 15:55:50 -0700 [thread overview]
Message-ID: <cover.1538088475.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This is my series to improve the heuristics used by Kyber. Patches 1 and
2 are preparation. Patch 3 is a minor optimization. Patch 4 is the main
change, and includes a detailed description of the new heuristics. Patch
5 adds tracepoints for debugging. This is basically the same as the RFC
I posted back in August [1] with one added tracepoint (kyber_throttled)
and rebased on linux-block/for-next.
Thanks!
1: https://www.spinics.net/lists/linux-block/msg29453.html
Omar Sandoval (5):
block: move call of scheduler's ->completed_request() hook
block: export blk_stat_enable_accounting()
kyber: don't make domain token sbitmap larger than necessary
kyber: implement improved heuristics
kyber: add tracepoints
block/blk-mq-sched.h | 4 +-
block/blk-mq.c | 5 +-
block/blk-stat.c | 1 +
block/kyber-iosched.c | 547 ++++++++++++++++++++---------------
include/linux/elevator.h | 2 +-
include/trace/events/kyber.h | 96 ++++++
6 files changed, 409 insertions(+), 246 deletions(-)
create mode 100644 include/trace/events/kyber.h
--
2.19.0
next reply other threads:[~2018-09-28 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 22:55 Omar Sandoval [this message]
2018-09-27 22:55 ` [PATCH v2 1/5] block: move call of scheduler's ->completed_request() hook Omar Sandoval
2018-09-27 22:55 ` [PATCH v2 2/5] block: export blk_stat_enable_accounting() Omar Sandoval
2018-09-27 22:55 ` [PATCH v2 3/5] kyber: don't make domain token sbitmap larger than necessary Omar Sandoval
2018-09-27 22:55 ` [PATCH v2 4/5] kyber: implement improved heuristics Omar Sandoval
2018-09-27 22:55 ` [PATCH v2 5/5] kyber: add tracepoints Omar Sandoval
2018-09-27 23:35 ` [PATCH v2 0/5] kyber: better heuristics 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=cover.1538088475.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=axboe@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).