All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Tom Barbette <barbette@kth.se>, <dev@dpdk.org>
Cc: <orika@mellanox.com>, <beilei.xing@intel.com>, <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] rte_flow: Different devices have different field indianess?
Date: Fri, 27 Mar 2020 17:44:16 +0300	[thread overview]
Message-ID: <fe15b4b2-f5e7-2b9f-1705-98f8a1564815@solarflare.com> (raw)
In-Reply-To: <2aa27e9f-6063-0842-8819-f6f0fd17267c@kth.se>

On 3/27/20 5:29 PM, Tom Barbette wrote:
> Hi all,
> 
> It seems rte_flow_item_eth takes its ethertype in host byte order with
> i40e, but in network byte order with mlx5.

If so, it is definitely bug in i40e, since struct rte_flow_item_eth
defines type as rte_be16_t type.

> 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


  reply	other threads:[~2020-03-27 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 14:29 [dpdk-dev] rte_flow: Different devices have different field indianess? Tom Barbette
2020-03-27 14:44 ` Andrew Rybchenko [this message]
2020-03-27 14:51   ` Tom Barbette
2020-03-30  0:48     ` Xing, Beilei
2020-03-28 20:49   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fe15b4b2-f5e7-2b9f-1705-98f8a1564815@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=barbette@kth.se \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=qi.z.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.