From: Thomas Monjalon <thomas@monjalon.net>
To: Ori Kam <orika@mellanox.com>
Cc: dev@dpdk.org, "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
shreyansh.jain@nxp.com, jerin.jacob@cavium.com,
arybchenko@solarflare.com, "Patil,
Harish" <harish.patil@cavium.com>,
rasesh.mody@cavium.com, hemant.agrawal@nxp.com,
"Alejandro Lucero" <alejandro.lucero@netronome.com>,
wenzhuo.lu@intel.com, "John Daley" <johndale@cisco.com>,
"Shukla, Santosh" <santosh.shukla@cavium.com>
Subject: Re: [dpdk-dev] [RFC] ethdev: support tunnel encapsulation action
Date: Mon, 11 Jun 2018 13:20:47 +0200 [thread overview]
Message-ID: <2382625.dHMyoomdcn@xps> (raw)
In-Reply-To: <AM4PR05MB342565DB5E7524B587737ACFDB780@AM4PR05MB3425.eurprd05.prod.outlook.com>
11/06/2018 13:03, Ori Kam:
> Due to the very short release cycle for this
> 18.08 release, and the need for good discussions,
> It is more reasonable to target 18.11 for this proposal.
I agree the timeframe is too short in 18.08 to accept such
a new generic API.
> The intent is to have a good generic API for all tunnel encapsulation
> and working well with all HW constraints.
>
> So please let's start the multi-vendor discussion now.
Adding more people as Cc to let the discussion starting.
> For your information I have submitted a patch for MPLS only (as v2)
> to be integrated in 18.08 in the meantime.
Yes it is more reasonnable to extend the API introduced in 18.05,
by adding MPLS in 18.08.
This API requires to declare every tunnel protocols we want to offload.
If a more generic API can be found, it could replace the "18.05 one" later.
prev parent reply other threads:[~2018-06-11 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 15:48 Ori Kam
2018-06-11 6:53 ` Nélio Laranjeiro
2018-06-11 7:27 ` Ori Kam
2018-06-11 7:53 ` Nélio Laranjeiro
2018-06-11 10:46 ` [dpdk-dev] [RFC v2] ethdev: support MPLS " Ori Kam
2018-06-11 11:03 ` [dpdk-dev] [RFC] ethdev: support " Ori Kam
2018-06-11 11:20 ` Thomas Monjalon [this message]
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=2382625.dHMyoomdcn@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=arybchenko@solarflare.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harish.patil@cavium.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@cavium.com \
--cc=johndale@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=orika@mellanox.com \
--cc=rasesh.mody@cavium.com \
--cc=santosh.shukla@cavium.com \
--cc=shreyansh.jain@nxp.com \
--cc=wenzhuo.lu@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).