From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 390] netvsc: There are always too many packets in tx-drop queue in testpmd tx-side
Date: Wed, 05 Feb 2020 18:00:42 +0000 [thread overview]
Message-ID: <bug-390-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=390
Bug ID: 390
Summary: netvsc: There are always too many packets in tx-drop
queue in testpmd tx-side
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: mgamal@redhat.com
Target Milestone: ---
Description of problem:
While we test dpdk on Azure with testpmd, there are too many packets in tx-drop
queue.
Version-Release number of selected component (if applicable):
DPDK-18.11
How reproducible:
100%
Steps to Reproduce:
1.Prepare 2 vms on Azure with dpdk installed
2.The 1st vm, start testpmd with txonly mode. The 2nd one start testpmd with
rx-only mode.And set 1st vm's peer mac address as the 2nd vm's mac address.
Conversely, set 2nd vm's peer mac address as the 1st one's mac address.
#TX-SIDE
#./testpmd -c 0xf -n 1 -w 0002:00:02.0
--vdev="net_vdev_netvsc0,iface=eth1,force=1" -- --port-topology=chained
--nb-cores 1 --forward-mode=txonly --eth-peer=1,00:0d:3a:a1:4b:43
--stats-period 1
#RX-SIDE
#./testpmd -c 0xf -n 1 -w 0002:00:02.0
--vdev="net_vdev_netvsc0,iface=eth1,force=1" -- --port-topology=chained
--nb-cores 1 --forward-mode=rxonly --eth-peer=1,00:0d:3a:a1:41:c7
--stats-period 1
3.Keep testpmd running up to 1 minute,then stop testpmd.
4.Check 2 vms' output
Actual results:
tx-side
++++++++ Accumulated forward statistics for all ports++++++++++
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 340381695 TX-dropped: 241822721 TX-total: 582204416
++++++++++++++++++++++++++++++++++++++++++++++
rx-side
++++++++ Accumulated forward statistics for all ports++++++
RX-packets: 339493162 RX-dropped: 0 RX-total: 339493162
TX-packets: 0 TX-dropped: 0 TX-total: 0
+++++++++++++++++++++++++++++++++++++++++++++
Expected results:
There shouldn't be too many(40%-50%) packets in TX-dropped queue
Additional info:
The bug occurs in latest DPDK upstream
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-05 18:00 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-390-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 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.