From: "Doherty, Declan" <declan.doherty@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"johndale@cisco.com" <johndale@cisco.com>,
"shahafs@mellanox.com" <shahafs@mellanox.com>,
"borisp@mellanox.com" <borisp@mellanox.com>,
"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>,
"yuanhanl@mellanox.com" <yuanhanl@mellanox.com>,
"Awal, Mohammad Abdul" <mohammad.abdul.awal@intel.com>,
"dev@openvswitch.org" <dev@openvswitch.org>,
"Chandran, Sugesh" <sugesh.chandran@intel.com>,
"dball@vmware.com" <dball@vmware.com>,
"simon.horman@netronome.com" <simon.horman@netronome.com>,
"Stokes, Ian" <ian.stokes@intel.com>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>,
"fc@napatech.com" <fc@napatech.com>,
"songjiaquanjx@gmail.com" <songjiaquanjx@gmail.com>,
"pieter.jansenvanvuuren@netronome.com"
<pieter.jansenvanvuuren@netronome.com>,
"frikkie.scholtz@netronome.com" <frikkie.scholtz@netronome.com>,
"Bodireddy, Bhanuprakash" <bhanuprakash.bodireddy@intel.com>,
"Keane, Lorna" <lorna.keane@intel.com>,
"Giller, Robin" <robin.giller@intel.com>,
"Loftus, Ciara" <ciara.loftus@intel.com>,
"echaudro@redhat.com" <echaudro@redhat.com>
Subject: [dpdk-dev] tunnel endpoint hw acceleration enablement
Date: Tue, 27 Feb 2018 15:55:13 +0000 [thread overview]
Message-ID: <345C63BAECC1AD42A2EC8C63AFFC3ADCD4A3175B@irsmsx105.ger.corp.intel.com> (raw)
Invite for a DPDK community call to discuss the tunnel endpoint hw acceleration proposal in this RFC (http://dpdk.org/ml/archives/dev/2017-December/084676.html) and the related community feedback.
Proposed agenda:
- Summary of RFC proposal, treating TEPs as standalone entities which flows get added to/remove form.
- Community feedback, managing TEPs purely within the scope of rte_flow as a property of individual flows.
- Pro's/con's of each approach.
- Downstream users feedback/thought's, I'm hoping to get some participation from the OvS-DPDK community, as our proposal was shaped with the view of enabling tunnel-endpoint encap/decap with full vswitch offload.
- next steps.
Regards
Declan
.........................................................................................................................................
--> Join Skype Meeting<https://meet.intel.com/declan.doherty/T3JV10SN>
Trouble Joining? Try Skype Web App<https://meet.intel.com/declan.doherty/T3JV10SN?sl=1>
Join by phone
+1(916)356-2663 (or your local bridge access #) Choose bridge 5.<tel:+1(916)356-2663%20(or%20your%20local%20bridge%20access%20#)%20Choose%20bridge%205.> (Global) English (United States)
Find a local number<https://dial.intel.com>
Conference ID: 150042341
Forgot your dial-in PIN?<https://dial.intel.com> |Help<https://o15.officeredir.microsoft.com/r/rlidLync15?clid=1033&p1=5&p2=2009>
[!OC([1033])!]
.........................................................................................................................................
next reply other threads:[~2018-02-27 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:55 Doherty, Declan [this message]
2018-02-28 7:50 ` Thomas Monjalon
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=345C63BAECC1AD42A2EC8C63AFFC3ADCD4A3175B@irsmsx105.ger.corp.intel.com \
--to=declan.doherty@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bhanuprakash.bodireddy@intel.com \
--cc=borisp@mellanox.com \
--cc=ciara.loftus@intel.com \
--cc=dball@vmware.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=fc@napatech.com \
--cc=frikkie.scholtz@netronome.com \
--cc=ian.stokes@intel.com \
--cc=johndale@cisco.com \
--cc=lorna.keane@intel.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=pieter.jansenvanvuuren@netronome.com \
--cc=robin.giller@intel.com \
--cc=shahafs@mellanox.com \
--cc=simon.horman@netronome.com \
--cc=songjiaquanjx@gmail.com \
--cc=sugesh.chandran@intel.com \
--cc=yliu@fridaylinux.org \
--cc=yuanhanl@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).