DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	"jingjing.wu@intel.com" <jingjing.wu@intel.com>,
	"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Dekel Peled" <dekelp@mellanox.com>,
	"Thomas Monjalon" <thomas@monjalon.net>,
	"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
	"Yongseok Koh" <yskoh@mellanox.com>,
	"Shahaf Shuler" <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd
Date: Fri, 5 Oct 2018 14:00:59 +0000	[thread overview]
Message-ID: <AM4PR05MB3425AD41314555E1BCA81BDFDBEB0@AM4PR05MB3425.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <64e05e52-b1d0-1d23-fde8-1c4d726b8d1f@intel.com>



> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Friday, October 5, 2018 4:35 PM
> To: Ori Kam <orika@mellanox.com>; wenzhuo.lu@intel.com;
> jingjing.wu@intel.com; bernard.iremonger@intel.com;
> arybchenko@solarflare.com; stephen@networkplumber.org; Adrien Mazarguil
> <adrien.mazarguil@6wind.com>
> Cc: dev@dpdk.org; Dekel Peled <dekelp@mellanox.com>; Thomas Monjalon
> <thomas@monjalon.net>; Nélio Laranjeiro <nelio.laranjeiro@6wind.com>;
> Yongseok Koh <yskoh@mellanox.com>; Shahaf Shuler
> <shahafs@mellanox.com>
> Subject: Re: [dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd
> 
> On 9/29/2018 9:07 PM, Ori Kam wrote:
> > Currently testpmd have support only for encapsulation and decapsulation
> > for L2 tunnels.
> >
> > This series adds commands for L3 tunnels types, L3 tunnel is a tunnel
> > that the inner packet is missing the L2 part. The encapsulation uses
> > the encap_l3 command in-order to remove the inner l2.
> > For decapsulation since the inner packet is missing the L2 there is
> > a need to supply it to the NIC using the decap_l3.
> >
> > The tunnels are are implemented are: MPLSoGRE and MPLSoUDP
> > while the decap can be used for all L3 tunnels.
> >
> > This series is based on add generic L2/L3 tunnel encapsulation actions [1]
> >
> > [1]
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.d
> pdk.org%2Farchives%2Fdev%2F2018-
> September%2F111781.html&amp;data=02%7C01%7Corika%40mellanox.com%7
> C2b9d669ee5d1459c1afe08d62ac76dee%7Ca652971c7d2e4d9ba6a4d149256f4
> 61b%7C0%7C0%7C636743433379968780&amp;sdata=BJPaGlCcjAHeIxNsQ%2B
> 1crdhT3UwDWj1Z931Osy6I4Qo%3D&amp;reserved=0
> >
> >
> > Ori Kam (3):
> >   app/testpmd: add MPLSoUDP encapsulation
> >   app/testpmd: add MPLSoGRE encapsulation
> >   app/testpmd: add decap l3 command
> 
> Same here, can you please rebase on latest next-net. Getting a few old rte_flow
> related patch caused conflict with almost all outstanding rte_flow patches...

Sure I will send a new version.

Ori

  reply	other threads:[~2018-10-05 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 20:07 Ori Kam
2018-09-29 20:07 ` [dpdk-dev] [PATCH 1/3] app/testpmd: add MPLSoUDP encapsulation Ori Kam
2018-09-29 20:07 ` [dpdk-dev] [PATCH 2/3] app/testpmd: add MPLSoGRE encapsulation Ori Kam
2018-09-29 20:07 ` [dpdk-dev] [PATCH 3/3] app/testpmd: add decap l3 command Ori Kam
2018-10-05 13:35 ` [dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd Ferruh Yigit
2018-10-05 14:00   ` Ori Kam [this message]
2018-10-07 14:41 ` [dpdk-dev] [PATCH v2 " Ori Kam
2018-10-07 14:41   ` [dpdk-dev] [PATCH v2 1/3] app/testpmd: add MPLSoUDP encapsulation Ori Kam
2018-10-07 14:41   ` [dpdk-dev] [PATCH v2 2/3] app/testpmd: add MPLSoGRE encapsulation Ori Kam
2018-10-07 14:41   ` [dpdk-dev] [PATCH v2 3/3] app/testpmd: add decap l3 command Ori Kam
2018-10-09 16:48   ` [dpdk-dev] [PATCH v2 0/3] app/testpmd: add l3 encap/decap cmd 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=AM4PR05MB3425AD41314555E1BCA81BDFDBEB0@AM4PR05MB3425.eurprd05.prod.outlook.com \
    --to=orika@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@intel.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).