From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gregory Etelson <getelson@nvidia.com>,
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>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH V2 1/2] app/testpmd: add tunnel types
Date: Tue, 19 Oct 2021 22:52:37 +0100 [thread overview]
Message-ID: <2f28b603-c2ea-5554-e4f1-f730d3cf7d50@intel.com> (raw)
In-Reply-To: <BN6PR1201MB02279458CA346004D1EDF5B3A5B89@BN6PR1201MB0227.namprd12.prod.outlook.com>
On 10/14/2021 7:29 PM, Gregory Etelson wrote:
>> Subject: [PATCH V2 1/2] app/testpmd: add
>> tunnel types
>>
>> Current testpmd implementation supports
>> VXLAN only for tunnel offload.
>> Add GRE, NVGRE and GENEVE for tunnel offload
>> flow matches.
>>
>> For example:
>> testpmd> flow tunnel create 0 type vxlan
>> port 0: flow tunnel #1 type vxlan
>> testpmd> flow tunnel create 0 type nvgre
>> port 0: flow tunnel #2 type nvgre
>> testpmd> flow tunnel create 0 type gre
>> port 0: flow tunnel #3 type gre
>> testpmd> flow tunnel create 0 type geneve
>> port 0: flow tunnel #4 type geneve
>>
>> Fixes: 1b9f274623b8 ("app/testpmd: add
>> commands for tunnel offload")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Eli Britstein <elibr@nvidia.com>
>
> Reviewed-by: Gregory Etelson <getelson@nvidia.com>
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-10-19 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f07404a3-bd3a-aaad-3194-01159bb762a4@intel.com>
2021-09-23 8:43 ` [dpdk-stable] " Eli Britstein
2021-09-23 8:43 ` [dpdk-stable] [PATCH V2 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-19 21:52 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2021-10-14 17:15 ` [dpdk-stable] [PATCH V2 1/2] app/testpmd: add " Ferruh Yigit
2021-10-14 18:29 ` Gregory Etelson
2021-10-19 21:52 ` Ferruh Yigit [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=2f28b603-c2ea-5554-e4f1-f730d3cf7d50@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=elibr@nvidia.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@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).