From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 399] ixgbe X540 PMD RSS is zero for NFSv3 NULL reply
Date: Thu, 13 Feb 2020 22:34:42 +0000 [thread overview]
Message-ID: <bug-399-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=399
Bug ID: 399
Summary: ixgbe X540 PMD RSS is zero for NFSv3 NULL reply
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: daveb@infinite.io
Target Milestone: ---
Created attachment 84
--> https://bugs.dpdk.org/attachment.cgi?id=84&action=edit
tcpdump -i eth3 -w /tmp/client80.mount.pcap host 10.240.160.1
We see packets with rte_mbuf.hash.rss == 0 for NFSv3 NULL reply packets, and
NFSv3 NFSACL reply packets, but all other packets appear correct.
Attached is a pcap, which when replayed through DPDK 18.11.3 having a copper
X540-based 10GbE NIC should show the zero RSS hashes for a restricted set of
packets. It is okay on others, but an NFSv3 mount command will have its frames
directed to the wrong core due to rte_mbuf.hash.rss == 0.
This problem does NOT exhibit with the 82599 ixgbe PMD.
If you open this pcap with wireshark, this filter expression will limit your
view to only those packets that get a zero RSS hash. All other packets in this
pcap had correct RSS values in rte_mbuf.hash.rss.
rpc.procedure == 0 and rpc.msgtyp == 1 and (tcp.port == 2049)
This will select packets: 20, 44, 71, 91, 118, 138, 165, 185, 211, 230, 256,
275, 301, 320, 346, 365, 391, 410, 436, 455. Each of these packets had
rte_mbuf.hash.rss == 0. All other packets had valid hash.rss values.
The attached pcap holds the traffic as seen by the client, generated by this
command:
seq 10 | while read a; do sudo time mount -t nfs -o vers=3 10.240.160.1:/jot
/mnt/daveb; sudo umount /mnt/daveb; done
Our application is a bump-on-the-wire between client and server. All packets
flow through our box (and DPDK 18.11.3) both directions. The only packets with
a bad RSS are those indicated above. The NIC in our box is (from kern.log):
Feb 7 16:43:06 firefly kernel: PE310G4BPi40T found, firmware version: 0xac
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-13 22:34 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-399-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.