From: Jamal Hadi Salim <jhs@mojatatu.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
info@netdevconf.org, linux-wireless@vger.kernel.org,
tech-committee@netdevconf.org, David Miller <davem@davemloft.net>,
Stephen Jaworski <jaws@mojatatu.com>,
lwn@lwn.net, people@netdevconf.org,
Brenda Butler <bjb@mojatatu.com>
Subject: ANNOUNCE: Netdev 2.1 update Feb 20
Date: Mon, 20 Feb 2017 08:18:15 -0500 [thread overview]
Message-ID: <7ac4b86b-5346-e709-6c45-39271a902ef0@mojatatu.com> (raw)
A few announcements:
-Registration is open. Register early so we can plan better.
https://onlineregistrations.ca/netdev21/
hotel (If you can get the hotel cheaper online than conference
rates please send us email, dont book ):
http://www.netdevconf.org/2.1/hotel.html
- We are pleased to announce our first Gold sponsor! We welcome back
Redhat as sponsors and thank them for their commitment to the netdev
community!
- We are pleased to announce our first Platinum sponsor: Cumulus
Networks. Cumulus has always been there for the netdev Community from
our very first conference. Thank you Cumulus!
- Our hard working tech committee has accepted another proposal. This
time veteran netdever Stephen Hemminger digs into the semantics of
names. Names have consequences he says.
Title: What's in a name?
---
Network device names have existed from the earliest days of Unix
networking and their usage has evolved. This talk is a look at some of
the issues with network device names. kernel developers often think the
problem is a userspace issue and nothing can be done but the names are
a key part of the existing ABI.
In the talk, I will cover how the choice of naming policy interacts
with applications and cloud environments, what current expectations
are, and how this interacts with cloud infrastructure. There is no
solution but there are several things that can be done to improve
the user experience. Will also give examples including Amazon, Azure,
Google Compute as well as other non-Linux environments.
-----
Please note that The Call for Proposals is still open, submit early
to avoid the hazards of last minute traffic. Refer to:
http://netdevconf.org/2.1/submit-proposal.html
cheers,
jamal
reply other threads:[~2017-02-20 13:18 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=7ac4b86b-5346-e709-6c45-39271a902ef0@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=bjb@mojatatu.com \
--cc=davem@davemloft.net \
--cc=info@netdevconf.org \
--cc=jaws@mojatatu.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=people@netdevconf.org \
--cc=tech-committee@netdevconf.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