From: Thomas Monjalon <thomas@monjalon.net>
To: "Doherty, Declan" <declan.doherty@intel.com>
Cc: 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.co
Subject: Re: tunnel endpoint hw acceleration enablement
Date: Wed, 28 Feb 2018 08:50:11 +0100 [thread overview]
Message-ID: <2220120.ukU0OTdcqg@xps> (raw)
In-Reply-To: <345C63BAECC1AD42A2EC8C63AFFC3ADCD4A3175B@irsmsx105.ger.corp.intel.com>
Hi Declan,
27/02/2018 16:55, Doherty, Declan:
> 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.
The email does not show the date and time of your invitation.
prev parent reply other threads:[~2018-02-28 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:55 tunnel endpoint hw acceleration enablement Doherty, Declan
2018-02-28 7:50 ` 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=2220120.ukU0OTdcqg@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=bhanuprakash.bodireddy@intel.co \
--cc=borisp@mellanox.com \
--cc=dball@vmware.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=fc@napatech.com \
--cc=frikkie.scholtz@netronome.com \
--cc=ian.stokes@intel.com \
--cc=johndale@cisco.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=pieter.jansenvanvuuren@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.