From: Ming Lei <ming.lei@redhat.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-block <linux-block@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [bug report] nvme-tcp poll queue causes busy loop and 100% CPU in nvme_tcp_poll() on the latest linux-block/for-next
Date: Wed, 21 Jan 2026 16:53:10 +0800 [thread overview]
Message-ID: <aXCT9sFChMdhwNYw@fedora> (raw)
In-Reply-To: <CAHj4cs9JJu+dDZqAvCd1qPM1CZuV-_b-AHxXpU-vJrGHHO-ExA@mail.gmail.com>
On Wed, Jan 21, 2026 at 10:50:00AM +0800, Yi Zhang wrote:
> Hi
>
> This issue was observed on the latest linux-block/for-next during CKI
> test, where enabling the poll queues leads to a tight busy polling
> loop and 100% CPU usage during "nvme connect".
> It seems was introduced from v6.19-rc1 and cannot reproduced on v6.18.
> I will try to bisect it.
It may be related with f22ecf9c14c1 ("blk-mq: delete task running check
in blk_hctx_poll()").
I guess it only happens when `nvme connect` takes a bit long time, not sure if
it can be reproduced 100%.
Thanks,
Ming
next prev parent reply other threads:[~2026-01-21 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 2:50 [bug report] nvme-tcp poll queue causes busy loop and 100% CPU in nvme_tcp_poll() on the latest linux-block/for-next Yi Zhang
2026-01-21 8:25 ` Christoph Hellwig
2026-01-21 8:53 ` Ming Lei [this message]
2026-01-21 9:03 ` Yi Zhang
[not found] ` <CAHj4cs_BWMOsn7MwNc=YNsmN=TM_r8WK_o2qa3DedqA4rtHefw@mail.gmail.com>
2026-01-22 3:48 ` Ming Lei
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=aXCT9sFChMdhwNYw@fedora \
--to=ming.lei@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yi.zhang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.