DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: dev@dpdk.org
Cc: orika@mellanox.com, beilei.xing@intel.com, qi.z.zhang@intel.com
Subject: [dpdk-dev] rte_flow: Different devices have different field indianess?
Date: Fri, 27 Mar 2020 15:29:16 +0100	[thread overview]
Message-ID: <2aa27e9f-6063-0842-8819-f6f0fd17267c@kth.se> (raw)

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 14:29 Tom Barbette [this message]
2020-03-27 14:44 ` Andrew Rybchenko
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=2aa27e9f-6063-0842-8819-f6f0fd17267c@kth.se \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).