From: Ming Lei <ming.lei@redhat.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-block@vger.kernel.org, hch@lst.de, yukuai1@huaweicloud.com,
axboe@kernel.dk, yi.zhang@redhat.com, czhong@redhat.com,
gjoyce@ibm.com
Subject: Re: [PATCH 2/3] block: introduce alloc_sched_data and free_sched_data elevator methods
Date: Thu, 23 Oct 2025 15:48:41 +0800 [thread overview]
Message-ID: <aPnd2WMKE5gjkM0s@fedora> (raw)
In-Reply-To: <59cf7e0f-1069-4766-9234-cc91985470e4@linux.ibm.com>
On Thu, Oct 23, 2025 at 11:27:26AM +0530, Nilay Shroff wrote:
>
>
> On 10/22/25 10:09 AM, Ming Lei wrote:
> > On Thu, Oct 16, 2025 at 11:00:48AM +0530, Nilay Shroff wrote:
> >> The recent lockdep splat [1] highlights a potential deadlock risk
> >> involving ->elevator_lock and ->freeze_lock dependencies on -pcpu_alloc_
> >> mutex. The trace shows that the issue occurs when the Kyber scheduler
> >> allocates dynamic memory for its elevator data during initialization.
> >>
> >> To address this, introduce two new elevator operation callbacks:
> >> ->alloc_sched_data and ->free_sched_data.
> >
> > This way looks good.
> >
> >>
> >> When an elevator implements these methods, they are invoked during
> >> scheduler switch before acquiring ->freeze_lock and ->elevator_lock.
> >> This allows safe allocation and deallocation of per-elevator data
> >
> > This per-elevator data should be very similar with `struct elevator_tags`
> > from block layer viewpoint: both have same lifetime, and follow same
> > allocation constraint(per-cpu lock).
> >
> > Can we abstract elevator data structure to cover both? Then I guess the
> > code should be more readable & maintainable, what do you think of this way?
> >
> > One easiest way could be to add 'void *data' into `struct elevator_tags`,
> > just the naming of `elevator_tags` is not generic enough, but might not
> > a big deal.
> >
> Hmm, good point! I'd rather suggest if we could instead rename
> struct elevator_tags to struct elevator_resources and then
> add void *data field to it. Something like this:
>
> struct elevator_tags {
> unsigned int nr_hw_queues;
> unsigned int nr_requests;
> struct blk_mq_tags *tags[];
> void *data;
'data' can't follow `tags[]`.
> };
>
> What do you think?
It is good. The patch may be split into two:
- add data to `struct elevator_tags` for covering the lockdep issue
- renaming
Then it will become easier for review.
Thanks
Ming
next prev parent reply other threads:[~2025-10-23 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 5:30 [PATCH 0/3] block: restructure elevator switch path and fix a lockdep splat Nilay Shroff
2025-10-16 5:30 ` [PATCH 1/3] block: unify elevator tags and type xarrays into struct elv_change_ctx Nilay Shroff
2025-10-22 4:11 ` Ming Lei
2025-10-23 5:53 ` Nilay Shroff
2025-10-16 5:30 ` [PATCH 2/3] block: introduce alloc_sched_data and free_sched_data elevator methods Nilay Shroff
2025-10-22 4:39 ` Ming Lei
2025-10-23 5:57 ` Nilay Shroff
2025-10-23 7:48 ` Ming Lei [this message]
2025-10-23 8:28 ` Nilay Shroff
2025-10-27 17:38 ` Nilay Shroff
2025-10-28 2:43 ` Ming Lei
2025-10-28 4:51 ` Nilay Shroff
2025-10-16 5:30 ` [PATCH 3/3] 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=aPnd2WMKE5gjkM0s@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=yukuai1@huaweicloud.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