[dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd

Ori Kam orika at mellanox.com
Fri Oct 5 16:00:59 CEST 2018



> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit at intel.com>
> Sent: Friday, October 5, 2018 4:35 PM
> To: Ori Kam <orika at mellanox.com>; wenzhuo.lu at intel.com;
> jingjing.wu at intel.com; bernard.iremonger at intel.com;
> arybchenko at solarflare.com; stephen at networkplumber.org; Adrien Mazarguil
> <adrien.mazarguil at 6wind.com>
> Cc: dev at dpdk.org; Dekel Peled <dekelp at mellanox.com>; Thomas Monjalon
> <thomas at monjalon.net>; Nélio Laranjeiro <nelio.laranjeiro at 6wind.com>;
> Yongseok Koh <yskoh at mellanox.com>; Shahaf Shuler
> <shahafs at 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&data=02%7C01%7Corika%40mellanox.com%7
> C2b9d669ee5d1459c1afe08d62ac76dee%7Ca652971c7d2e4d9ba6a4d149256f4
> 61b%7C0%7C0%7C636743433379968780&sdata=BJPaGlCcjAHeIxNsQ%2B
> 1crdhT3UwDWj1Z931Osy6I4Qo%3D&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


More information about the dev mailing list