From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: [PATCH V3 0/3] blk-mq: driver tag related cleanup
Date: Tue, 30 Jun 2020 22:03:54 +0800 [thread overview]
Message-ID: <20200630140357.2251174-1-ming.lei@redhat.com> (raw)
Hi Jens,
The 1st & 2nd patch moves get/put driver tag helpers into blk-mq.c, and
the 3rd patch centralise related handling into blk_mq_get_driver_tag,
so both flush & blk-mq code get simplified.
V3:
- rebase on latest for-5.9/block, only 3/3 is changed.
V2:
- add reviewed-by tag
- don't put blk_mq_tag_busy() into blk_mq_get_driver_tag
- use BLK_MQ_NO_TAG in blk-flush.c
Ming Lei (3):
blk-mq: move blk_mq_get_driver_tag into blk-mq.c
blk-mq: move blk_mq_put_driver_tag() into blk-mq.c
blk-mq: centralise related handling into blk_mq_get_driver_tag
block/blk-flush.c | 17 +++++-------
block/blk-mq-tag.c | 58 ----------------------------------------
block/blk-mq-tag.h | 41 +++++++++++++++++-----------
block/blk-mq.c | 66 +++++++++++++++++++++++++++++++++++++++++-----
block/blk-mq.h | 20 --------------
block/blk.h | 5 ----
6 files changed, 91 insertions(+), 116 deletions(-)
Cc: Christoph Hellwig <hch@infradead.org>
--
2.25.2
next reply other threads:[~2020-06-30 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 14:03 Ming Lei [this message]
2020-06-30 14:03 ` [PATCH V3 1/3] blk-mq: move blk_mq_get_driver_tag into blk-mq.c Ming Lei
2020-06-30 14:03 ` [PATCH V3 2/3] blk-mq: move blk_mq_put_driver_tag() " Ming Lei
2020-06-30 14:03 ` [PATCH V3 3/3] blk-mq: centralise related handling into blk_mq_get_driver_tag Ming Lei
2020-07-02 4:37 ` Qian Cai
2020-07-02 6:20 ` Ming Lei
2020-06-30 18:58 ` [PATCH V3 0/3] blk-mq: driver tag related cleanup 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=20200630140357.2251174-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--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).