From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, Christoph Hellwig <hch@lst.de>,
"Bart Van Assche" <bart.vanassche@sandisk.com>
Subject: [PATCH v3 0/4] Extend blk-mq-debugfs functionality further
Date: Thu, 1 Jun 2017 08:55:09 -0700 [thread overview]
Message-ID: <20170601155513.26712-1-bart.vanassche@sandisk.com> (raw)
Hello Jens,
This series contains four patches that add new features to the blk-mq-debugfs
code. Please consider these patches for kernel v4.13.
Thanks,
Bart.
Changes between v2 and v3:
- Renamed a function in the patch that shows busy requests. In the same patch,
added a comment as requested by Ming.
- Added Reviewed-by tags to those patches that got an additional review.
Changes compared to v1:
- Left out the first patch of this series because it's already upstream.
- Renamed "ctx" into "params" in the patch that shows the busy requests.
- In the same patch, switched from blk_mq_debugfs_rq_show() to
__blk_mq_debugfs_rq_show().
The patches in this series are:
Bart Van Assche (4):
blk-mq-debugfs: Show atomic request flags
blk-mq-debugfs: Show requeue list
blk-mq-debugfs: Show busy requests
blk-mq-debugfs: Add 'kick' operation
block/blk-mq-debugfs.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 76 insertions(+), 1 deletion(-)
--
2.12.2
next reply other threads:[~2017-06-01 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:55 Bart Van Assche [this message]
2017-06-01 15:55 ` [PATCH v3 1/4] blk-mq-debugfs: Show atomic request flags Bart Van Assche
2017-06-01 15:55 ` [PATCH v3 2/4] blk-mq-debugfs: Show requeue list Bart Van Assche
2017-06-01 15:55 ` [PATCH v3 3/4] blk-mq-debugfs: Show busy requests Bart Van Assche
2017-06-02 2:07 ` Ming Lei
2017-06-01 15:55 ` [PATCH v3 4/4] blk-mq-debugfs: Add 'kick' operation Bart Van Assche
2017-06-01 17:14 ` [PATCH v3 0/4] Extend blk-mq-debugfs functionality further Eduardo Valentin
2017-06-01 19:03 ` 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=20170601155513.26712-1-bart.vanassche@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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