On 7/30/2018 5:19 PM, Ori Kam wrote:
> Currenlty the encap/decap actions only support encapsulation
> of VXLAN and NVGRE L2 packets.
> There is a need to add more L2 tunnels and also L3 tunnels.
>
> One issue with the current approch is the duplication of code.
> For example the code for handling
homas Monjalon
> ; Yongseok Koh ;
> ferruh.yi...@intel.com; arybche...@solarflare.com; dev@dpdk.org
> Subject: RE: [dpdk-dev] [RFC] ethdev: add generic L2/L3 tunnel
> encapsulation actions
>
>
>
> > -Original Message-
> > From: Stephen Hemminger [mailto:step...@network
uh.yi...@intel.com; arybche...@solarflare.com; dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] ethdev: add generic L2/L3 tunnel
> encapsulation actions
>
> On Mon, 30 Jul 2018 19:19:25 +0300
> Ori Kam wrote:
>
> > Currenlty the encap/decap actions only support encapsulation
>
On Mon, 30 Jul 2018 19:19:25 +0300
Ori Kam wrote:
> Currenlty the encap/decap actions only support encapsulation
> of VXLAN and NVGRE L2 packets.
> There is a need to add more L2 tunnels and also L3 tunnels.
>
> One issue with the current approch is the duplication of code.
> For example the cod
Currenlty the encap/decap actions only support encapsulation
of VXLAN and NVGRE L2 packets.
There is a need to add more L2 tunnels and also L3 tunnels.
One issue with the current approch is the duplication of code.
For example the code for handling NVGRE and VXLAN are exactly the same,
and each ne
5 matches
Mail list logo
