From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Eli Britstein <elibr@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "xiaoyun.li@intel.com" <xiaoyun.li@intel.com>,
Matan Azrad <matan@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/mlx5: add support for more tunnel types
Date: Mon, 18 Oct 2021 08:48:54 +0000 [thread overview]
Message-ID: <DM6PR12MB3753FC302C8D1C8E148B221EDFBC9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210913142535.9084-2-elibr@nvidia.com>
> -----Original Message-----
> From: Eli Britstein <elibr@nvidia.com>
> Sent: Monday, September 13, 2021 17:26
> To: dev@dpdk.org
> Cc: xiaoyun.li@intel.com; Matan Azrad <matan@nvidia.com>; Shahaf Shuler
> <shahafs@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Gregory
> Etelson <getelson@nvidia.com>; Eli Britstein <elibr@nvidia.com>
> Subject: [PATCH 2/2] net/mlx5: add support for more tunnel types
>
> Accept RTE_FLOW_ITEM_TYPE_GRE, RTE_FLOW_ITEM_TYPE_NVGRE and
> RTE_FLOW_ITEM_TYPE_GENEVE as valid tunnel types.
>
> Signed-off-by: Eli Britstein <elibr@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-10-18 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:25 [dpdk-dev] [PATCH 1/2] app/testpmd: add " Eli Britstein
2021-09-13 14:25 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-18 8:48 ` Slava Ovsiienko [this message]
2021-09-20 15:57 ` [dpdk-dev] [PATCH 1/2] app/testpmd: add " Ferruh Yigit
2021-09-23 8:43 ` [dpdk-dev] [PATCH V2 " Eli Britstein
2021-09-23 8:43 ` [dpdk-dev] [PATCH V2 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-19 21:52 ` Ferruh Yigit
2021-10-14 17:15 ` [dpdk-dev] [PATCH V2 1/2] app/testpmd: add " Ferruh Yigit
2021-10-14 18:29 ` Gregory Etelson
2021-10-19 21:52 ` Ferruh Yigit
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=DM6PR12MB3753FC302C8D1C8E148B221EDFBC9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=elibr@nvidia.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=xiaoyun.li@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).