All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Yu Kuai <yukuai3@huawei.com>
Subject: Re: [PATCH 6/6] blk-mq: manage hctx map via xarray
Date: Tue, 1 Mar 2022 05:37:17 -0800	[thread overview]
Message-ID: <Yh4hjS0S3vXfLWlH@infradead.org> (raw)
In-Reply-To: <20220228090430.1064267-7-ming.lei@redhat.com>

> -			hctxs[i] = blk_mq_alloc_and_init_hctx(set, q, i,
> -					old_node);
> -			WARN_ON_ONCE(!hctxs[i]);
> +			WARN_ON_ONCE(!blk_mq_alloc_and_init_hctx(set, q, i,
> +						old_node));


Please avoid doing the actual work inside a WARN_ON statement.

>  
>  	for (; j < end; j++) {
> -		struct blk_mq_hw_ctx *hctx = hctxs[j];
> +		struct blk_mq_hw_ctx *hctx = blk_mq_get_hctx(q, j);
>  
> -		if (hctx) {
> +		if (hctx)
>  			blk_mq_exit_hctx(q, set, hctx, j);
> -			hctxs[j] = NULL;
> -		}
>  	}

Instead of a for loop that does xa_loads repeatedly this can just
use xa_for_each_range.  Same for a bunch of other loops like that,
e.g. in blk_mq_unregister_dev or the __blk_mq_register_dev failure
path.

> @@ -919,12 +919,12 @@ static inline void *blk_mq_rq_to_pdu(struct request *rq)
>  static inline struct blk_mq_hw_ctx *blk_mq_get_hctx(struct request_queue *q,
>  		unsigned int hctx_idx)
>  {
> -	return q->queue_hw_ctx[hctx_idx];
> +	return xa_load(&q->hctx_table, hctx_idx);
>  }
>  
>  #define queue_for_each_hw_ctx(q, hctx, i)				\
>  	for ((i) = 0; (i) < (q)->nr_hw_queues &&			\
> -	     ({ hctx = blk_mq_get_hctx((q), (i)); 1; }); (i)++)
> +	     (hctx = blk_mq_get_hctx((q), (i))); (i)++)

This should be using a xa_for_each loop.

With various places converted to loops I'm not even sure we really
want the blk_mq_get_hctx helper at all.

  parent reply	other threads:[~2022-03-01 13:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  9:04 [PATCH 0/6] blk-mq: update_nr_hw_queues related improvement & bugfix Ming Lei
2022-02-28  9:04 ` [PATCH 1/6] blk-mq: figure out correct numa node for hw queue Ming Lei
2022-03-01 13:30   ` Christoph Hellwig
2022-03-01 19:19   ` John Garry
2022-03-02  1:47     ` Ming Lei
2022-03-02  9:02       ` John Garry
2022-03-02  9:22         ` Ming Lei
2022-03-02 10:11           ` John Garry
2022-02-28  9:04 ` [PATCH 2/6] blk-mq: simplify reallocation of hw ctxs a bit Ming Lei
2022-03-01 13:30   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 3/6] blk-mq: re-config poll after queue map is changed Ming Lei
2022-03-01 13:31   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 4/6] block: mtip32xx: don't touch q->queue_hw_ctx Ming Lei
2022-03-01 13:32   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 5/6] blk-mq: add helper of blk_mq_get_hctx to retrieve hctx via its index Ming Lei
2022-03-01 13:33   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 6/6] blk-mq: manage hctx map via xarray Ming Lei
2022-02-28 17:36   ` kernel test robot
2022-02-28 17:57   ` kernel test robot
2022-03-01  9:08     ` Ming Lei
2022-03-01  9:08       ` Ming Lei
2022-03-01 13:37   ` Christoph Hellwig [this message]
2022-03-02  2:06     ` Ming Lei
2022-03-02  8:24       ` Christoph Hellwig
2022-03-02  9:53         ` Ming Lei
2022-03-02  9:59           ` Christoph Hellwig

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=Yh4hjS0S3vXfLWlH@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=yukuai3@huawei.com \
    /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.