From: "Lange Tang" <lange_tang@163.com>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "mst@redhat.com" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>,
"jasowangio@gmail.com" <jasowangio@gmail.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Tang Longjun" <tanglongjun@kylinos.cn>
Subject: Re:Re: [PATCH 2/3] virtio_net: introduce an RX queue watchdog for stuck detection
Date: Fri, 20 Nov 2026 15:11:53 +0800 (CST) [thread overview]
Message-ID: <2cca370d.59a4.1a1f7cc263c.Coremail.lange_tang@163.com> (raw)
In-Reply-To: <20261112085333.77476864@kernel.org>
At 2026-11-13 00:53:33, "Jakub Kicinski" <kuba@kernel.org> wrote:
>On Mon, 9 Nov 2026 17:43:09 +0800 Longjun Tang wrote:
>> The backend raises an interrupt after adding buffers to the used ring,
>> and the hypervisor injects it. If one is lost (e.g., a transient KVM
>> failure), NAPI will not be scheduled and the driver stops consuming
>> buffers. The ring eventually fills up, the backend stops notifying, and
>> the queue is left permanently stuck.
>
>Can you say more about what platform you're hitting this problem on?
>An what's the virtio backend?
arm64 guest; the backend is OVS-DPDK (vhost-user). To be honest, I inferred the lost
interrupt from the guest side (virtio_net RX queue stuck) rather than tracing the backend,
and reproduced the stall by temporarily masking the interrupt injection.
next prev parent reply other threads:[~2026-11-20 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 9:43 [PATCH 0/3] virtio_net: introduce an RX queue watchdog for stuck detection Longjun Tang
2026-11-09 9:43 ` [PATCH 1/3] virtio: add virtqueue_get_last_used_idx() helper Longjun Tang
2026-11-12 16:51 ` Jakub Kicinski
2026-11-20 7:10 ` Lange Tang
2026-11-12 22:50 ` Michael S. Tsirkin
2026-11-20 7:13 ` Lange Tang
2026-11-09 9:43 ` [PATCH 2/3] virtio_net: introduce an RX queue watchdog for stuck detection Longjun Tang
2026-11-12 16:53 ` Jakub Kicinski
2026-11-20 7:11 ` Lange Tang [this message]
2026-11-12 22:51 ` Michael S. Tsirkin
2026-11-20 7:14 ` Lange Tang
2026-11-09 9:43 ` [PATCH 3/3] virtio_net: add rx_timeouts per-queue statistic Longjun Tang
2026-11-12 22:52 ` Michael S. Tsirkin
2026-11-20 7:15 ` Lange Tang
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=2cca370d.59a4.1a1f7cc263c.Coremail.lange_tang@163.com \
--to=lange_tang@163.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tanglongjun@kylinos.cn \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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