[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d80b9fc4-515e-4ce8-9f3c-28bdf2676336@kernel.org>
Date: Thu, 31 Jul 2025 02:01:13 +0800
From: Yu Kuai <yukuai@...nel.org>
To: Bart Van Assche <bvanassche@....org>, Yu Kuai <yukuai1@...weicloud.com>,
dlemoal@...nel.org, hare@...e.de, jack@...e.cz, tj@...nel.org,
josef@...icpanda.com, axboe@...nel.dk, yukuai3@...wei.com
Cc: cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
johnny.chenyi@...wei.com
Subject: Re: [PATCH v2 2/5] mq-deadline: switch to use elevator lock
Hi,
在 2025/7/31 1:21, Bart Van Assche 写道:
> On 7/30/25 1:22 AM, Yu Kuai wrote:
>> @@ -466,10 +466,9 @@ static struct request
>> *dd_dispatch_request(struct blk_mq_hw_ctx *hctx)
>> struct request *rq;
>> enum dd_prio prio;
>> - spin_lock(&dd->lock);
>> rq = dd_dispatch_prio_aged_requests(dd, now);
>
> The description says "no functional changes" but I think I see a
> functional change above. Please restrict this patch to changing
> &dd->lock into dd->lock only.
Ok, you mean that the lock is moved to the caller is functional change,
right?
Thanks,
Kuai
>
> Thanks,
>
> Bart.
>
Powered by blists - more mailing lists