From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/3] blk-mq: Support sharing tags across hardware queues
Date: Tue, 26 Nov 2019 09:56:53 -0800 [thread overview]
Message-ID: <20191126175656.67638-1-bvanassche@acm.org> (raw)
Hi Jens,
Although the block layer already supports sharing hardware queues across
request queues, it does not yet support sharing tags across hardware queues.
Some SCSI hardware needs this functionality because this is a good match for
how some SCSI HBA's work. This patch does not incur a performance overhead
for block drivers that do not share tags across hardware queues.
Note: my original plan was to post this patch series after the merge window
has closed. I'm posting this now to allow comparison with alternative
approaches.
Thanks,
Bart.
Bart Van Assche (2):
blk-mq: Move the TAG_ACTIVE and SCHED_RESTART flags from hctx into
blk_mq_tags
block: Add support for sharing tags across hardware queues
John Garry (1):
blk-mq: Remove some unused function arguments
block/blk-mq-debugfs.c | 42 ++++++++++++++++++++++++++++++++++++++----
block/blk-mq-sched.c | 8 ++++----
block/blk-mq-sched.h | 2 +-
block/blk-mq-tag.c | 19 +++++++++++--------
block/blk-mq-tag.h | 13 +++++++++++--
block/blk-mq.c | 38 +++++++++++++++++++++++++-------------
block/blk-mq.h | 2 +-
include/linux/blk-mq.h | 10 ++++++----
8 files changed, 97 insertions(+), 37 deletions(-)
next reply other threads:[~2019-11-26 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 17:56 Bart Van Assche [this message]
2019-11-26 17:56 ` [PATCH 1/3] blk-mq: Remove some unused function arguments Bart Van Assche
2019-11-26 17:56 ` [PATCH 2/3] blk-mq: Move the TAG_ACTIVE and SCHED_RESTART flags from hctx into blk_mq_tags Bart Van Assche
2019-11-27 0:43 ` Ming Lei
2019-11-26 17:56 ` [PATCH 3/3] block: Add support for sharing tags across hardware queues Bart Van Assche
2019-11-27 9:51 ` John Garry
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=20191126175656.67638-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--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;
as well as URLs for NNTP newsgroup(s).