From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A7808A057C;
	Fri, 27 Mar 2020 15:29:20 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 046581C1F6;
	Fri, 27 Mar 2020 15:29:20 +0100 (CET)
Received: from smtp-3.sys.kth.se (smtp-3.sys.kth.se [130.237.48.192])
 by dpdk.org (Postfix) with ESMTP id 34FAA1C1F5
 for <dev@dpdk.org>; Fri, 27 Mar 2020 15:29:19 +0100 (CET)
Received: from smtp-3.sys.kth.se (localhost.localdomain [127.0.0.1])
 by smtp-3.sys.kth.se (Postfix) with ESMTP id DA1647033;
 Fri, 27 Mar 2020 15:29:18 +0100 (CET)
X-Virus-Scanned: by amavisd-new at kth.se
Received: from smtp-3.sys.kth.se ([127.0.0.1])
 by smtp-3.sys.kth.se (smtp-3.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id Fz8u7X9IJgEs; Fri, 27 Mar 2020 15:29:18 +0100 (CET)
X-KTH-Auth: barbette [2a02:a03f:4070:7c00:9497:bf60:4477:6ee1]
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default;
 t=1585319358; bh=mYfEyANRK2kXaIk5osWdlEc/g6KT585IWfdrnZX1/wQ=;
 h=To:Cc:From:Subject:Date;
 b=l9pGo2Q0pUyl6K76s1bV49Kkis7+SAevKtR/myBM5Tlv05H8On1zX1t00NyGjMVJK
 SlQJcrSaF1AU20H0+PuptLLOzDsOxgFEsxO8K/CZFII/KsnHBr3+nDBBFA2pzRviQq
 Scif93IhABKrY3ZKDY6xlUkRAh4qiiIE9CL6Be9U=
X-KTH-mail-from: barbette@kth.se
Received: from [IPv6:2a02:a03f:4070:7c00:9497:bf60:4477:6ee1] (unknown
 [IPv6:2a02:a03f:4070:7c00:9497:bf60:4477:6ee1])
 by smtp-3.sys.kth.se (Postfix) with ESMTPSA id C46889618;
 Fri, 27 Mar 2020 15:29:17 +0100 (CET)
To: dev@dpdk.org
Cc: orika@mellanox.com, beilei.xing@intel.com, qi.z.zhang@intel.com
From: Tom Barbette <barbette@kth.se>
Message-ID: <2aa27e9f-6063-0842-8819-f6f0fd17267c@kth.se>
Date: Fri, 27 Mar 2020 15:29:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 7bit
Subject: [dpdk-dev] rte_flow: Different devices have different field
	indianess?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi all,

It seems rte_flow_item_eth takes its ethertype in host byte order with 
i40e, but in network byte order with mlx5.

Wouldn't it be nice to unify that? Else is there a way to know in which 
byte order the spec should be given? I guess that expands to all fields, 
but I only compared the ethertype field.

Thanks,

Tom