From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1716] virtio_xmit_cleanup failed when vm rx/tx queues from 1024 to 4096
Date: Thu, 29 May 2025 08:16:28 +0000 [thread overview]
Message-ID: <bug-1716-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1716
Bug ID: 1716
Summary: virtio_xmit_cleanup failed when vm rx/tx queues from
1024 to 4096
Product: DPDK
Version: 22.11
Hardware: Other
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: updoing@sina.com
Target Milestone: ---
Created attachment 319
--> https://bugs.dpdk.org/attachment.cgi?id=319&action=edit
viritio patch
In a virtual machine scenario running a DPDK application with virtio drivers,
when the host machine adjusted the guest VM's transmit/receive queue size from
1024 to 4096, the DPDK application's allocated 2048 mbufs became insufficient.
After this adjustment, the condition vq->vq_nentries - vq->vq_free_thresh was
never triggered, resulting in the cleanup operation not occurring.
virtio_dev_rx_queue_setup the third param nb_desc is not used when
vq->vq_free_cnt great then nb_desc. vq->vq_free_cnt is assigned a value through
vq->n_nentries when virtio driver has inited. i40e driver vq has a nb_rx_desc
value, our dpdk app nb_desc setup 2048, malloc 2048 mbufs, so our dpdk app
rx/tx burst is failed on the line.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3432 bytes --]
reply other threads:[~2025-05-29 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1716-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).