DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
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@6wind.com
Cc: dev@dpdk.org, dekelp@mellanox.com, thomas@monjalon.net,
	nelio.laranjeiro@6wind.com, yskoh@mellanox.com,
	shahafs@mellanox.com
Subject: Re: [dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd
Date: Fri, 5 Oct 2018 14:35:12 +0100	[thread overview]
Message-ID: <64e05e52-b1d0-1d23-fde8-1c4d726b8d1f@intel.com> (raw)
In-Reply-To: <1538251641-91511-1-git-send-email-orika@mellanox.com>

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://mails.dpdk.org/archives/dev/2018-September/111781.html
> 
> 
> 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...

  parent reply	other threads:[~2018-10-05 13:35 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 ` Ferruh Yigit [this message]
2018-10-05 14:00   ` [dpdk-dev] [PATCH 0/3] app/testpmd: add l3 encap/decap cmd Ori Kam
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=64e05e52-b1d0-1d23-fde8-1c4d726b8d1f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=orika@mellanox.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).