From: Jens Axboe <axboe@kernel.dk>
To: Cong Zhang <cong.zhang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: skip CPU offline notify on unmapped hctx
Date: Tue, 30 Dec 2025 09:02:44 -0700 [thread overview]
Message-ID: <176711056497.410043.6155561525733424852.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251230-blk_mq_no_ctx_checking-v1-1-2168131383e6@oss.qualcomm.com>
On Tue, 30 Dec 2025 17:17:05 +0800, Cong Zhang wrote:
> If an hctx has no software ctx mapped, blk_mq_map_swqueue() never
> allocates tags and leaves hctx->tags NULL. The CPU hotplug offline
> notifier can still run for that hctx, return early since hctx cannot
> hold any requests.
>
>
Applied, thanks!
[1/1] blk-mq: skip CPU offline notify on unmapped hctx
commit: 10845a105bbcb030647a729f1716c2309da71d33
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-12-30 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 9:17 [PATCH] blk-mq: skip CPU offline notify on unmapped hctx Cong Zhang
2025-12-30 11:42 ` Ming Lei
2025-12-30 16:02 ` 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=176711056497.410043.6155561525733424852.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=cong.zhang@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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