From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id DB965A0544; Thu, 13 Feb 2020 23:34:45 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 391EC1C029; Thu, 13 Feb 2020 23:34:45 +0100 (CET) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 3D9621C020 for ; Thu, 13 Feb 2020 23:34:44 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 07256A0545; Thu, 13 Feb 2020 23:34:43 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Thu, 13 Feb 2020 22:34:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 18.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daveb@infinite.io X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 399] ixgbe X540 PMD RSS is zero for NFSv3 NULL reply X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D399 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=3D84&action=3Dedit tcpdump -i eth3 -w /tmp/client80.mount.pcap host 10.240.160.1 We see packets with rte_mbuf.hash.rss =3D=3D 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 fr= ames directed to the wrong core due to rte_mbuf.hash.rss =3D=3D 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 =3D=3D 0 and rpc.msgtyp =3D=3D 1 and (tcp.port =3D=3D 2= 049) 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 =3D=3D 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=3D3 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 packe= ts 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 --=20 You are receiving this mail because: You are the assignee for the bug.=