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: [PATCHv5 4/5] block: use {alloc|free}_sched data methods
Date: Wed, 12 Nov 2025 18:38:58 +0800 [thread overview]
Message-ID: <aRRjwlUDXDHdv2C8@fedora> (raw)
In-Reply-To: <20251112052848.1433256-5-nilay@linux.ibm.com>
On Wed, Nov 12, 2025 at 10:56:05AM +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>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
next prev parent reply other threads:[~2025-11-12 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 5:26 [PATCHv5 0/5] block: restructure elevator switch path and fix a lockdep splat Nilay Shroff
2025-11-12 5:26 ` [PATCHv5 1/5] block: unify elevator tags and type xarrays into struct elv_change_ctx Nilay Shroff
2025-11-12 5:26 ` [PATCHv5 2/5] block: move elevator tags into struct elevator_resources Nilay Shroff
2025-11-12 10:37 ` Ming Lei
2025-11-12 5:26 ` [PATCHv5 3/5] block: introduce alloc_sched_data and free_sched_data elevator methods Nilay Shroff
2025-11-12 10:34 ` Ming Lei
2025-11-12 13:05 ` Nilay Shroff
2025-11-12 5:26 ` [PATCHv5 4/5] block: use {alloc|free}_sched data methods Nilay Shroff
2025-11-12 10:38 ` Ming Lei [this message]
2025-11-12 5:26 ` [PATCHv5 5/5] block: define alloc_sched_data and free_sched_data methods for kyber Nilay Shroff
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=aRRjwlUDXDHdv2C8@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