From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles (Chas) Williams" <3chas3@gmail.com> Subject: Re: [PATCH] bnx2x: tx_start_bd->vlan_or_ethertype is le16 Date: Tue, 01 Dec 2015 18:58:14 -0500 Message-ID: <1449014294.2645.42.camel@gmail.com> References: <1446571576-28399-1-git-send-email-3chas3@gmail.com> <20151201143754.06675ca9@xeon-e3> <3362628.iLARgdqr6m@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com [209.85.192.50]) by dpdk.org (Postfix) with ESMTP id 9EA1137A6 for ; Wed, 2 Dec 2015 00:58:16 +0100 (CET) Received: by qgeb1 with SMTP id b1so20394478qge.1 for ; Tue, 01 Dec 2015 15:58:16 -0800 (PST) In-Reply-To: <3362628.iLARgdqr6m@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 2015-12-02 at 00:34 +0100, Thomas Monjalon wrote: > 2015-12-01 14:37, Stephen Hemminger: > > Harish Patil wrote: > > > >2015-11-03 12:26, Chas Williams: > > > >> --- a/drivers/net/bnx2x/bnx2x.c > > > >> +++ b/drivers/net/bnx2x/bnx2x.c > > > >> - tx_start_bd->vlan_or_ethertype = eh->ether_type; > > > >> + tx_start_bd->vlan_or_ethertype > > > >> + = rte_cpu_to_le_16(rte_be_to_cpu_16(eh->ether_type)); > > > > > > Minor question - any specific reason to use rte_be_to_cpu_16() on > > > ether_type alone before converting from native order to le16? > > > > ether_type is in network byte order (big endian) > > and hardware wants little endian. On x86 the second step is a nop. > > Doesn't it deserve a macro rte_ntole16()? > It may be in lib/librte_eal/common/include/generic/rte_byteorder.h. I looked I didn't see anything. This value, according to the linux driver, wants to be little endian regardless of the host endian.