From: Suanming Mou <suanmingm@mellanox.com>
To: viacheslavo@mellanox.com, matan@mellanox.com
Cc: orika@mellanox.com, rasland@mellanox.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] net/mlx5: scatter FCS with decapsulation
Date: Wed, 15 Jul 2020 21:10:19 +0800 [thread overview]
Message-ID: <1594818621-438919-1-git-send-email-suanmingm@mellanox.com> (raw)
There are some limitations on the some NICs (at least on ConnectX-6DX
and BlueField2) with supporting FCS (frame checksum) scattering for
the tunnel decapsulated packets.
For the case only one of the features can be supported in the same time,
and the new devarg "decap_en" is introduced to provide the choice to the
users.
If FCS scattering feature is not supposed to be engaged by application,
this new devarg should be specified as "decap_en=0", forcing the FCS
feature enable and rejecting tunnel decap actions in the rte_flow engine.
If FCS scatter is not needed and application supposes to use tunnel
decapsulation in rte_flow, the devarg can be omitted or set to non-zero
value (this is default settings).
Suanming Mou (2):
common/mlx5: add scatter FCS with decap capability query
net/mlx5: add decap enable device argument
doc/guides/nics/mlx5.rst | 15 +++++++++++++++
drivers/common/mlx5/mlx5_devx_cmds.c | 2 ++
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/common/mlx5/mlx5_prm.h | 4 +++-
drivers/net/mlx5/linux/mlx5_os.c | 12 ++++++++++--
drivers/net/mlx5/mlx5.c | 6 ++++++
drivers/net/mlx5/mlx5.h | 1 +
drivers/net/mlx5/mlx5_flow_dv.c | 5 +++++
8 files changed, 43 insertions(+), 3 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-07-15 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 13:10 Suanming Mou [this message]
2020-07-15 13:10 ` [dpdk-dev] [PATCH 1/2] common/mlx5: add scatter FCS with decap capability query Suanming Mou
2020-07-15 13:10 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add decap enable device argument Suanming Mou
2020-07-19 9:45 ` [dpdk-dev] [PATCH 0/2] net/mlx5: scatter FCS with decapsulation Raslan Darawsheh
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=1594818621-438919-1-git-send-email-suanmingm@mellanox.com \
--to=suanmingm@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=rasland@mellanox.com \
--cc=viacheslavo@mellanox.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).