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 2FD7CA0562; Sun, 29 Mar 2020 16:51:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7C5891C11C; Sun, 29 Mar 2020 16:48:41 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id ED3111C11C for ; Sun, 29 Mar 2020 16:48:39 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 8EBCAA0598; Sun, 29 Mar 2020 16:48:39 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Sun, 29 Mar 2020 14:48:37 +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: 20.02 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: barbette@kth.se X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: 20.05 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 cc 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 430] i40e has wrong byte order in rte_flow_item_eth (ethdev) 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=3D430 Bug ID: 430 Summary: i40e has wrong byte order in rte_flow_item_eth (ethdev) Product: DPDK Version: 20.02 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: barbette@kth.se CC: arybchenko@solarflare.com, beilei.xing@intel.com, qi.z.zhang@intel.com, thomas@monjalon.net Target Milestone: 20.05 Following a recent discussion on the mailing list, I'm opening this bug bec= ause rte_flow_item_eth takes its ethertype in host byte order with i40e, while it should be in network byte order. In consequence, with testpmd one must give the inverted endianness for the ethertype : testpmd> flow create 0 ingress pattern eth type is 0x0800 / end actions mar= k id 5 / end port_flow_complain(): Caught PMD error type 13 (specific pattern item): cau= se: 0x227fd75540, Unsupported ether_type.: Invalid argument testpmd> flow create 0 ingress pattern eth type is 0x0008 / end actions mar= k id 5 / end Flow rule #0 created I only tested the ethertype, but it may affect other fields? As per Andrew Rybchenko's comment, the type of rte_flow_item_eth is rte_be1= 6_t so the correct behaviour is network byte order. --=20 You are receiving this mail because: You are the assignee for the bug.=