From: Omar Sandoval <osandov@osandov.com>
To: Jens Axboe <axboe@fb.com>, linux-block@vger.kernel.org
Cc: Bart Van Assche <bart.vanassche@sandisk.com>, kernel-team@fb.com
Subject: [PATCH 0/9] blk-mq-debugfs: scheduler support and cleanups
Date: Wed, 3 May 2017 12:18:53 -0700 [thread overview]
Message-ID: <cover.1493839103.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This series makes more enhancements to blk-mq-debugfs.
- Patch 1 is a subjective change.
- Patches 2 and 3 are cleanups.
- Patch 4 is Bart's patch from a couple of weeks ago, necessitated by
patch 6.
- Patch 5 is another cleanup.
- Patch 6 reworks the lifetimes of the debugfs attributes to be tied to
the structure lifetimes themselves rather being duct taped on to
sysfs. This is what I should have done in the first place, and would
have also been a way to fix the same thing we fixed in e869b5462f83
("blk-mq: Unregister debugfs attributes earlier"), but I didn't think
of doing it this way until I started adding scheduler support.
- Patch 7 allows schedulers to register debugfs attributes, implemented
in patches 8 and 9 for kyber and mq-deadline, respectively.
Please take a look and give it a spin.
Thanks!
Bart Van Assche (1):
blk-mq: Do not invoke queue operations on a dead queue
Omar Sandoval (8):
blk-mq-debugfs: separate flags with |
blk-mq-debugfs: clean up flag definitions
blk-mq-debugfs: get rid of a bunch of boilerplate
blk-mq: move debugfs declarations to a separate header file
blk-mq: untangle debugfs and sysfs
blk-mq-debugfs: allow schedulers to register debugfs attributes
kyber: add debugfs attributes
mq-deadline: add debugfs attributes
block/blk-core.c | 8 +-
block/blk-mq-debugfs.c | 851 +++++++++++++++++++++--------------------------
block/blk-mq-debugfs.h | 79 +++++
block/blk-mq-sched.c | 24 +-
block/blk-mq-sysfs.c | 10 -
block/blk-mq.c | 7 +
block/blk-mq.h | 28 --
block/blk-sysfs.c | 3 +
block/kyber-iosched.c | 130 ++++++++
block/mq-deadline.c | 123 +++++++
include/linux/blk-mq.h | 5 +
include/linux/blkdev.h | 2 +-
include/linux/elevator.h | 7 +
13 files changed, 751 insertions(+), 526 deletions(-)
create mode 100644 block/blk-mq-debugfs.h
--
2.12.2
next reply other threads:[~2017-05-03 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 19:18 Omar Sandoval [this message]
2017-05-03 19:18 ` [PATCH 1/9] blk-mq-debugfs: separate flags with | Omar Sandoval
2017-05-03 19:18 ` [PATCH 2/9] blk-mq-debugfs: clean up flag definitions Omar Sandoval
2017-05-03 19:18 ` [PATCH 3/9] blk-mq-debugfs: get rid of a bunch of boilerplate Omar Sandoval
2017-05-03 20:51 ` Bart Van Assche
2017-05-03 23:22 ` Omar Sandoval
2017-05-03 19:18 ` [PATCH 4/9] blk-mq: Do not invoke queue operations on a dead queue Omar Sandoval
2017-05-03 19:18 ` [PATCH 5/9] blk-mq: move debugfs declarations to a separate header file Omar Sandoval
2017-05-03 19:18 ` [PATCH 6/9] blk-mq: untangle debugfs and sysfs Omar Sandoval
2017-05-03 19:19 ` [PATCH 7/9] blk-mq-debugfs: allow schedulers to register debugfs attributes Omar Sandoval
2017-05-03 19:19 ` [PATCH 8/9] kyber: add " Omar Sandoval
2017-05-03 19:19 ` [PATCH 9/9] mq-deadline: " Omar Sandoval
2017-05-03 19:57 ` [PATCH 10/9] blk-mq-debugfs: rename hw queue directories from <n> to hctx<n> Omar Sandoval
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.1493839103.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.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 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.