From: Raslan Darawsheh <rasland@mellanox.com>
To: Jack Min <jackmin@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Suspected-Phishing][PATCH v4] net/mlx5: support IP-in-IP tunnel
Date: Sun, 14 Jul 2019 12:26:33 +0000 [thread overview]
Message-ID: <DB3PR0502MB3964C66E4872683AA1EB3766C2CC0@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <ef05b06fb050ca48fd7fd7ce8ddd876632f7b7a1.1562770515.git.jackmin@mellanox.com>
Hi,
> -----Original Message-----
> From: Xiaoyu Min <jackmin@mellanox.com>
> Sent: Wednesday, July 10, 2019 6:00 PM
> To: Raslan Darawsheh <rasland@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Shahaf Shuler <shahafs@mellanox.com>;
> Yongseok Koh <yskoh@mellanox.com>; John McNamara
> <john.mcnamara@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org
> Subject: [Suspected-Phishing][PATCH v4] net/mlx5: support IP-in-IP tunnel
>
> Enabled IP-in-IP tunnel type support on DV/DR flow engine.
> This includes the following combination:
> - IPv4 over IPv4
> - IPv4 over IPv6
> - IPv6 over IPv4
> - IPv6 over IPv6
>
> MLX5 NIC supports IP-in-IP tunnel via FLEX Parser so need to make sure fw
> using FLEX Paser profile 0.
>
> mlxconfig -d <mst device> -y set FLEX_PARSER_PROFILE_ENABLE=0
>
> The example testpmd commands would be:
>
> - Match on IPv4 over IPv4 packets and do inner RSS:
>
> testpmd> flow create 0 ingress pattern eth / ipv4 proto is 0x04 /
> ipv4 / udp / end actions rss level 2 queues 0 1 2 3 end / end
>
> - Match on IPv6 over IPv4 packets and do inner RSS:
>
> testpmd> flow create 0 ingress pattern eth / ipv4 proto is 0x29 /
> ipv6 / udp / end actions rss level 2 queues 0 1 2 3 end / end
>
> Signed-off-by: Xiaoyu Min <jackmin@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> v2:
> * updated release note
> v3:
> * rebased on 19.08-rc1
> v4:
> * add example testpmd commands in commit log
> ---
> doc/guides/nics/mlx5.rst | 15 ++++++++++-
> doc/guides/rel_notes/release_19_08.rst | 1 +
> drivers/net/mlx5/mlx5_flow.c | 35 ++++++++++++++++++++++++
> drivers/net/mlx5/mlx5_flow.h | 6 ++++-
> drivers/net/mlx5/mlx5_flow_dv.c | 37 ++++++++++++++++++++++++++
> 5 files changed, 92 insertions(+), 2 deletions(-)
>
Patch applied on next-net-mlx after fixing conflict in documentation.
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2019-07-14 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 2:04 [dpdk-dev] [PATCH] " Xiaoyu Min
2019-07-02 5:51 ` [dpdk-dev] [PATCH v2] " Xiaoyu Min
2019-07-10 10:15 ` [dpdk-dev] [PATCH v3] " Xiaoyu Min
2019-07-10 14:19 ` [dpdk-dev] [Suspected-Phishing][PATCH " Slava Ovsiienko
2019-07-10 14:35 ` Slava Ovsiienko
2019-07-10 14:40 ` Jack Min
2019-07-10 14:59 ` [dpdk-dev] [PATCH v4] " Xiaoyu Min
2019-07-14 12:26 ` Raslan Darawsheh [this message]
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=DB3PR0502MB3964C66E4872683AA1EB3766C2CC0@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=jackmin@mellanox.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=shahafs@mellanox.com \
--cc=viacheslavo@mellanox.com \
--cc=yskoh@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).