From: Jens Axboe <axboe@kernel.dk>
To: yukuai3@huawei.com, bvanassche@acm.org, ming.lei@redhat.com,
nilay@linux.ibm.com, hare@suse.de,
Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com
Subject: Re: [PATCH v3 0/2] blk-mq: fix update nr_requests regressions
Date: Fri, 05 Sep 2025 13:54:32 -0600 [thread overview]
Message-ID: <175710207227.395498.3249940818566938241.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250821060612.1729939-1-yukuai1@huaweicloud.com>
On Thu, 21 Aug 2025 14:06:10 +0800, Yu Kuai wrote:
> Changes in v3:
> - call depth_updated() directly in init_sched() method in patch 1;
> - fix typos in patch 2;
> - add review for patch 2;
> Changes in v2:
> - instead of refactor and cleanups and fix updating nr_requests
> thoroughly, fix the regression in patch 2 the easy way, and dealy
> refactor and cleanups to next merge window.
>
> [...]
Applied, thanks!
[1/2] blk-mq: fix elevator depth_updated method
commit: 7d337eef4affc5e26e0570513168c69ddbc40f92
[2/2] blk-mq: fix blk_mq_tags double free while nr_requests grown
commit: ba28afbd9eff2a6370f23ef4e6a036ab0cfda409
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-09-05 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 6:06 Yu Kuai
2025-08-21 6:06 ` [PATCH v3 1/2] blk-mq: fix elevator depth_updated method Yu Kuai
2025-08-21 12:21 ` Nilay Shroff
2025-08-21 14:57 ` Li Nan
2025-08-22 6:00 ` Hannes Reinecke
2025-08-21 6:06 ` [PATCH v3 2/2] blk-mq: fix blk_mq_tags double free while nr_requests grown Yu Kuai
2025-08-21 14:57 ` Li Nan
2025-08-22 6:02 ` Hannes Reinecke
2025-08-26 6:27 ` [PATCH v3 0/2] blk-mq: fix update nr_requests regressions Yu Kuai
2025-09-05 7:20 ` Yu Kuai
2025-09-05 19:52 ` Jens Axboe
2025-09-05 19:54 ` Jens Axboe [this message]
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=175710207227.395498.3249940818566938241.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®