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 449F7A0524; Mon, 27 Jul 2020 11:29:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0705D1BFE2; Mon, 27 Jul 2020 11:29:18 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 5B5062C01 for ; Mon, 27 Jul 2020 11:29:16 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 33420A052B; Mon, 27 Jul 2020 11:29:16 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 27 Jul 2020 09:29:15 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mb@smartsharesystems.com 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 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 516] Multiple Intel Ethernet drivers do not conform to rte_eth_rx_burst() API 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=3D516 Bug ID: 516 Summary: Multiple Intel Ethernet drivers do not conform to rte_eth_rx_burst() API Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: mb@smartsharesystems.com Target Milestone: --- When calling rte_eth_rx_burst() with nb_pkts > 32, many of the receive func= tion implementations in the Intel Ethernet drivers only return 32 packets, but t= hey must return all available packets, up to nb_pkts. The API description of rte_eth_rx_burst() says: The rte_eth_rx_burst() function returns the number of packets actually retrieved, which is the number of rte_mbuf data structures effectively supp= lied into the rx_pkts array. A return value equal to nb_pkts indicates that the = RX queue contained at least rx_pkts packets, and this is likely to signify that other received packets remain in the input queue. Applications implementing= a "retrieve as much received packets as possible" policy can check this speci= fic case and keep invoking the rte_eth_rx_burst() function until a value less t= han nb_pkts is returned. The driver implementation does not conform to the documented behavior for "retrieve as much received packets as possible" applications. I initially ran into this bug on the ixgbe driver using the SSE vector rece= ive routine. It looks like some of the receive function implementations in most of the I= ntel Ethernet drivers assume that rte_eth_rx_burst() will not be called with nb_= pkts > 32. Looking at the source code, at least the ixgbe, i40e and fm10k drivers have= the same bug. Originally posted on the mailing list: http://inbox.dpdk.org/dev/98CBD80474FA8B44BF855DF32C47DC35C61127@smartserve= r.smartshare.dk/ --=20 You are receiving this mail because: You are the assignee for the bug.=