patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Eli Britstein <elibr@nvidia.com>, Matan Azrad <matan@nvidia.com>,
	"Gregory Etelson" <getelson@nvidia.com>
Cc: <xiaoyun.li@intel.com>, Shahaf Shuler <shahafs@nvidia.com>,
	"Slava Ovsiienko" <viacheslavo@nvidia.com>, <stable@dpdk.org>,
	<dev@dpdk.org>, "Ori Kam" <orika@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH V2 1/2] app/testpmd: add tunnel types
Date: Thu, 14 Oct 2021 18:15:30 +0100	[thread overview]
Message-ID: <54df14f1-8e54-a90e-a108-5bb149804e58@intel.com> (raw)
In-Reply-To: <20210923084301.5139-1-elibr@nvidia.com>

On 9/23/2021 9:43 AM, Eli Britstein wrote:
> 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>

Hi Matan, Gregory,

Set looks good to me but can you please help reviewing it?

Thanks,
ferruh

  parent reply	other threads:[~2021-10-14 17:44 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 ` 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   ` Ferruh Yigit [this message]
2021-10-14 18:29   ` [dpdk-stable] [PATCH V2 1/2] app/testpmd: add " Gregory Etelson
2021-10-19 21:52     ` [dpdk-stable] [dpdk-dev] " 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=54df14f1-8e54-a90e-a108-5bb149804e58@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=elibr@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@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).