From: Ming Lei <ming.lei@redhat.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 1/4] block: add mq_ops->queue_rqs hook
Date: Thu, 18 Nov 2021 08:18:29 +0800 [thread overview]
Message-ID: <YZWb1TiNLBtdQrt6@T590> (raw)
In-Reply-To: <20211117204101.GA3295649@dhcp-10-100-145-180.wdc.com>
On Wed, Nov 17, 2021 at 12:41:01PM -0800, Keith Busch wrote:
> On Tue, Nov 16, 2021 at 08:38:04PM -0700, Jens Axboe wrote:
> > If we have a list of requests in our plug list, send it to the driver in
> > one go, if possible. The driver must set mq_ops->queue_rqs() to support
> > this, if not the usual one-by-one path is used.
>
> It looks like we still need to sync with the request_queue quiesce flag.
I think this approach is good.
> Something like the following (untested) on top of this patch should do
> it:
>
> ---
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 688ebf6a7a7b..447d0b77375d 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -263,6 +263,9 @@ void blk_mq_wait_quiesce_done(struct request_queue *q)
> unsigned int i;
> bool rcu = false;
>
> + if (q->tag_set->flags & BLK_MQ_F_BLOCKING)
> + synchronize_srcu(q->srcu);
> +
> queue_for_each_hw_ctx(q, hctx, i) {
> if (hctx->flags & BLK_MQ_F_BLOCKING)
> synchronize_srcu(hctx->srcu);
> @@ -2201,6 +2204,25 @@ static void blk_mq_commit_rqs(struct blk_mq_hw_ctx *hctx, int *queued,
> *queued = 0;
> }
>
> +static void queue_lock(struct request_queue *q, int *srcu_idx)
> + __acquires(q->srcu)
> +{
> + if (!(q->tag_set->flags & BLK_MQ_F_BLOCKING)) {
> + *srcu_idx = 0;
> + rcu_read_lock();
> + } else
> + *srcu_idx = srcu_read_lock(q->srcu);
> +}
> +
> +static void queue_unlock(struct request_queue *q, int srcu_idx)
> + __releases(q->srcu)
> +{
> + if (!(q->tag_set->flags & BLK_MQ_F_BLOCKING))
> + rcu_read_unlock();
> + else
> + srcu_read_unlock(q->srcu, srcu_idx);
> +}
> +
> static void blk_mq_plug_issue_direct(struct blk_plug *plug, bool from_schedule)
> {
> struct blk_mq_hw_ctx *hctx = NULL;
> @@ -2216,7 +2238,14 @@ static void blk_mq_plug_issue_direct(struct blk_plug *plug, bool from_schedule)
> */
> rq = rq_list_peek(&plug->mq_list);
> if (rq->q->mq_ops->queue_rqs) {
> - rq->q->mq_ops->queue_rqs(&plug->mq_list);
> + struct request_queue *q = rq->q;
> + int srcu_idx;
> +
> + queue_lock(q, &srcu_idx);
> + if (!blk_queue_quiesced(q))
> + q->mq_ops->queue_rqs(&plug->mq_list);
> + queue_unlock(q, srcu_idx);
> +
> if (rq_list_empty(plug->mq_list))
> return;
> }
> @@ -3727,6 +3756,8 @@ int blk_mq_init_allocated_queue(struct blk_mq_tag_set *set,
> blk_queue_rq_timeout(q, set->timeout ? set->timeout : 30 * HZ);
>
> q->tag_set = set;
> + if (set->flags & BLK_MQ_F_BLOCKING)
> + init_srcu_struct(q->srcu);
>
> q->queue_flags |= QUEUE_FLAG_MQ_DEFAULT;
> if (set->nr_maps > HCTX_TYPE_POLL &&
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index bd4370baccca..ae7591dc9cbb 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -373,6 +373,8 @@ struct request_queue {
> * devices that do not have multiple independent access ranges.
> */
> struct blk_independent_access_ranges *ia_ranges;
> +
> + struct srcu_struct srcu[];
Basically it is same with my previous post[1], but the above patch doesn't
handle request queue allocation/freeing correctly in case of BLK_MQ_F_BLOCKING.
[1] https://lore.kernel.org/linux-block/20211103160018.3764976-1-ming.lei@redhat.com/
Thanks,
Ming
next prev parent reply other threads:[~2021-11-18 0:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 3:38 [PATCHSET 0/4] Add support for list issue Jens Axboe
2021-11-17 3:38 ` [PATCH 1/4] block: add mq_ops->queue_rqs hook Jens Axboe
2021-11-17 6:25 ` Christoph Hellwig
2021-11-17 15:41 ` Jens Axboe
2021-11-17 8:20 ` Ming Lei
2021-11-17 15:43 ` Jens Axboe
2021-11-17 20:48 ` Keith Busch
2021-11-17 23:59 ` Ming Lei
2021-11-17 20:41 ` Keith Busch
2021-11-18 0:18 ` Ming Lei [this message]
2021-11-18 2:02 ` Keith Busch
2021-11-18 2:14 ` Ming Lei
2021-11-17 3:38 ` [PATCH 2/4] nvme: split command copy into a helper Jens Axboe
2021-11-17 6:15 ` Christoph Hellwig
2021-11-17 15:44 ` Jens Axboe
2021-11-18 7:54 ` Chaitanya Kulkarni
2021-11-17 3:38 ` [PATCH 3/4] nvme: separate command prep and issue Jens Axboe
2021-11-17 6:17 ` Christoph Hellwig
2021-11-17 15:45 ` Jens Axboe
2021-11-18 7:59 ` Chaitanya Kulkarni
2021-11-17 3:38 ` [PATCH 4/4] nvme: add support for mq_ops->queue_rqs() Jens Axboe
2021-11-17 8:39 ` Christoph Hellwig
2021-11-17 15:55 ` Jens Axboe
2021-11-17 15:58 ` Jens Axboe
2021-11-17 19:41 ` Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 21:45 [PATCHSET v2 0/4] Add support for list issue Jens Axboe
2021-12-03 21:45 ` [PATCH 1/4] block: add mq_ops->queue_rqs hook Jens Axboe
2021-12-04 10:43 ` Hannes Reinecke
2021-12-04 20:13 ` Jens Axboe
2021-12-05 9:07 ` Hannes Reinecke
2021-12-05 13:09 ` Jens Axboe
2021-12-16 16:05 [PATCHSET v4 0/4] Add support for list issue Jens Axboe
2021-12-16 16:05 ` [PATCH 1/4] block: add mq_ops->queue_rqs hook Jens Axboe
2021-12-16 16:38 [PATCHSET v5 0/4] Add support for list issue Jens Axboe
2021-12-16 16:38 ` [PATCH 1/4] block: add mq_ops->queue_rqs hook 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=YZWb1TiNLBtdQrt6@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.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