From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 418] failsafe/tap PMD drops first UDP packet
Date: Wed, 11 Mar 2020 01:29:30 +0000 [thread overview]
Message-ID: <bug-418-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=418
Bug ID: 418
Summary: failsafe/tap PMD drops first UDP packet
Product: DPDK
Version: 20.02
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
On Azure, the first UDP packet of a flow is being dropped somewhere in the maze
of TAP PMD and Failsafe PMD. The packet arrives into the kernel device
(netvsc) and is visible with tcpdump but is lost after that. Subsequent UDP
packets get redirected to VF and have no problem.
This is a TAP/Failsafe PMD problem, and not generic to DPDK.
The Netvsc PMD does not have this problem.
The suggested fix is to use netvsc PMD instead..
To reproduce:
Setup two 8 core VMs, with accelerated networking, running Ubuntu 18.
On machine 1 run testpmd in rx only mode. My command line was:
# testpmd -l 4,5 -w 0002:00:02.0 --vdev="net_vdev_netvsc0,iface=eth1" --
--forward-mode=rxonly --stats-period=1
On machine 2 run netcat in UDP client mode.
$ nc -u 192.168.100.12 1234
Type on machine 2. The first line (packet) is lost and stat does not increment.
Second line (packet) does show up.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-03-11 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 1:29 bugzilla [this message]
2021-02-08 16:39 ` bugzilla
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-418-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).