From: Hajime Tazaki <thehajime@gmail.com>
To: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-wireless@vger.kernel.org,
netdev-conference@lists.netfilter.org
Subject: [ANNOUNCE] Netdev 1.2 weekly updates (24th August, 2016)
Date: Thu, 25 Aug 2016 00:37:09 +0900 [thread overview]
Message-ID: <87eg5euqje.wl-thehajime@gmail.com> (raw)
Hello folks,
Here is an weekly update of Netdev 1.2 Tokyo.
The early bird registration is still available. Please
don't miss the discount ticket - and your early registration
will be definitely helpful to prepare the conference.
http://netdevconf.org/1.2/registration.html
The session proposal submission is now closed. Thanks to
everyone who submitted a proposal. We have a lot of very
exciting talks, workshops and tutorials that the tech
committee is finalizing. We will be announcing them as they
get accepted. Please watch the website and twitter feed. We
are also going to be notifying you via email but less
frequently. We look forward to see you all in Tokyo.
== New accepted sessions ==
Full list of accepted sessions is available here.
http://netdevconf.org/1.2/accepted-sessions.html
* Workshop
- IPsec workshop Workshop
by Steffen Klassert
- Network Performance Workshop
by Jesper Dangaard Brouer
* Talk
- Scaling with multiple network namespaces in a single
application
by PJ Waskiewicz
- What is an L3 Master Device?
by David Ahern
- TLS Offload to Network Devices
by Boris Pismenny
- The adventures of a Suricate in eBPF land
by Eric Leblond
- Accelerating Linux IP Virtual Server with OpenNPU
by Gilad Ben-Yossef
* Tutorial
- Microservice Networking Leveraging VRF on the Host
by David Ahern
Our sponsors:
- Platinum
Verizon, Facebook, Cumulus Networks
- Gold
Mojatatu Networks, VMWare, Google, NTT
- Silver
NetApp, IIJ, Netronome, SolarFlare, Mellanox
- Bronze
Zen Load Balancer (new)
Twitter: https://twitter.com/netdev01
Web: http://netdevconf.org/1.2/
-- Hajime
reply other threads:[~2016-08-24 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87eg5euqje.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev-conference@lists.netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).