From: Ming Lei <ming.lei@redhat.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-block@vger.kernel.org, hch@lst.de, axboe@kernel.dk,
yi.zhang@redhat.com, czhong@redhat.com, yukuai@fnnas.com,
gjoyce@ibm.com
Subject: Re: [PATCHv4 4/5] block: use {alloc|free}_sched data methods
Date: Tue, 11 Nov 2025 10:58:54 +0800 [thread overview]
Message-ID: <aRKmbtp0J_VPH4v9@fedora> (raw)
In-Reply-To: <20251110081457.1006206-5-nilay@linux.ibm.com>
On Mon, Nov 10, 2025 at 01:44:51PM +0530, Nilay Shroff wrote:
> The previous patch introduced ->alloc_sched_data and
> ->free_sched_data methods. This patch builds upon that
> by now using these methods during elevator switch and
> nr_hw_queue update.
>
> It's also ensured that scheduler-specific data is
> allocated and freed through the new callbacks outside
> of the ->freeze_lock and ->elevator_lock locking contexts,
> thereby preventing any dependency on pcpu_alloc_mutex.
>
> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
> ---
> block/blk-mq-sched.c | 32 ++++++++++++++++++++++++--------
> block/blk-mq-sched.h | 8 ++++++--
> block/elevator.c | 34 ++++++++++++++++++++++------------
> block/elevator.h | 4 +++-
> 4 files changed, 55 insertions(+), 23 deletions(-)
>
> diff --git a/block/blk-mq-sched.c b/block/blk-mq-sched.c
> index c7091ea4dccd..0ea8f0004274 100644
> --- a/block/blk-mq-sched.c
> +++ b/block/blk-mq-sched.c
> @@ -428,12 +428,17 @@ void blk_mq_free_sched_tags(struct elevator_tags *et,
> }
>
> void blk_mq_free_sched_res(struct elevator_resources *res,
> + struct elevator_type *type,
> struct blk_mq_tag_set *set)
> {
> if (res->et) {
> blk_mq_free_sched_tags(res->et, set);
> res->et = NULL;
> }
> + if (res->data) {
> + blk_mq_free_sched_data(type, res->data);
> + res->data = NULL;
> + }
> }
>
> void blk_mq_free_sched_res_batch(struct xarray *elv_tbl,
> @@ -458,7 +463,7 @@ void blk_mq_free_sched_res_batch(struct xarray *elv_tbl,
> WARN_ON_ONCE(1);
> continue;
> }
> - blk_mq_free_sched_res(&ctx->res, set);
> + blk_mq_free_sched_res(&ctx->res, ctx->type, set);
> }
> }
> }
> @@ -540,15 +545,24 @@ struct elevator_tags *blk_mq_alloc_sched_tags(struct blk_mq_tag_set *set,
> return NULL;
> }
>
> -int blk_mq_alloc_sched_res(struct elevator_resources *res,
> - struct blk_mq_tag_set *set, unsigned int nr_hw_queues)
> +int blk_mq_alloc_sched_res(struct request_queue *q,
> + struct elevator_type *type,
> + struct elevator_resources *res,
> + struct blk_mq_tag_set *set,
> + unsigned int nr_hw_queues)
As mentioned, `struct request_queue *q` parameter can be added from
beginning, then `struct blk_mq_tag_set *set` can be avoided.
Otherwise, this patch looks fine.
Thanks,
Ming
next prev parent reply other threads:[~2025-11-11 2:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 8:14 [PATCHv4 0/5] block: restructure elevator switch path and fix a lockdep splat Nilay Shroff
2025-11-10 8:14 ` [PATCHv4 1/5] block: unify elevator tags and type xarrays into struct elv_change_ctx Nilay Shroff
2025-11-11 6:55 ` Yu Kuai
2025-11-11 8:37 ` Nilay Shroff
2025-11-11 10:02 ` Yu Kuai
2025-11-11 12:00 ` Nilay Shroff
2025-11-10 8:14 ` [PATCHv4 2/5] block: move elevator tags into struct elevator_resources Nilay Shroff
2025-11-11 2:52 ` Ming Lei
2025-11-11 6:49 ` Nilay Shroff
2025-11-10 8:14 ` [PATCHv4 3/5] block: introduce alloc_sched_data and free_sched_data elevator methods Nilay Shroff
2025-11-11 2:53 ` Ming Lei
2025-11-11 7:20 ` Yu Kuai
2025-11-11 8:39 ` Nilay Shroff
2025-11-10 8:14 ` [PATCHv4 4/5] block: use {alloc|free}_sched data methods Nilay Shroff
2025-11-11 2:58 ` Ming Lei [this message]
2025-11-11 6:51 ` Nilay Shroff
2025-11-10 8:14 ` [PATCHv4 5/5] block: define alloc_sched_data and free_sched_data methods for kyber Nilay Shroff
2025-11-11 3:01 ` Ming Lei
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=aRKmbtp0J_VPH4v9@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=czhong@redhat.com \
--cc=gjoyce@ibm.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=yi.zhang@redhat.com \
--cc=yukuai@fnnas.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 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).