From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"'announce@dpdk.org'" <announce@dpdk.org>
Subject: Re: [dpdk-announce] CFP for DPDK Summit Userspace
Date: Wed, 11 Jul 2018 13:34:28 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB771B739@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB76EAB3E@IRSMSX108.ger.corp.intel.com>
A quick reminder that the CFP for this closes on July 27th, which is two weeks on Friday. If you're planning to submit a proposal you can do so at: https://goo.gl/forms/Jh70MIA7QJE2nSBb2
Registration for the event is also open now. You can register at: https://www.regonline.com/DPDKDublin
> -----Original Message-----
> From: announce [mailto:announce-bounces@dpdk.org] On Behalf Of
> O'Driscoll, Tim
> Sent: Wednesday, June 6, 2018 4:46 PM
> To: 'announce@dpdk.org' <announce@dpdk.org>
> Subject: [dpdk-announce] CFP for DPDK Summit Userspace
>
> The CFP for DPDK Summit Userspace (September 5th & 6th in Dublin) is
> available now at: https://goo.gl/forms/Jh70MIA7QJE2nSBb2.
>
> The deadline for submissions is Friday July 27th. Submissions should
> focus on the key technical challenges facing the project. Suggested
> topics include:
> * New APIs, libraries and features
> * DPDK changes required to facilitate hardware acceleration
> * Technical challenges facing the DPDK community, including parts of the
> code that need to be refactored
> * Improvements to interworking with the Linux kernel
> * Improvements to performance, usability and packaging
> * Virtualization and container networking
> * Innovative networking technologies such as P4, and their impact on
> DPDK
>
> A link for registration for the event will be provided shortly.
>
next prev parent reply other threads:[~2018-07-11 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 15:45 O'Driscoll, Tim
2018-06-07 8:07 ` O'Driscoll, Tim
2018-07-11 13:34 ` O'Driscoll, Tim [this message]
[not found] ` <26FA93C7ED1EAA44AB77D62FBE1D27BAB7725E7F@IRSMSX107.ger.corp.intel.com>
2018-08-22 15:30 ` O'Driscoll, Tim
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=26FA93C7ED1EAA44AB77D62FBE1D27BAB771B739@IRSMSX107.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=announce@dpdk.org \
/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).