From: Ben Hutchings <bhutchings@solarflare.com>
To: Bill Nottingham <notting@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
narendra_k@dell.com, jcm@redhat.com
Subject: Re: extended netdevice naming proposal
Date: Thu, 18 Nov 2010 02:29:57 +0000 [thread overview]
Message-ID: <1290047397.3818.3.camel@localhost> (raw)
In-Reply-To: <20101118021039.GA18707@nostromo.devel.redhat.com>
On Wed, 2010-11-17 at 21:10 -0500, Bill Nottingham wrote:
> Matt Domsch (Matt_Domsch@dell.com) said:
> > (location)(slot)#(port)/(instance).(vlan)
>
> AIUI, the kernel explicitly rejects '/' in the name (for fairly obvious
> sysfs reasons.) So you'd at least need a different delimiter. There may
> also be potential confusion with pci01#03:02.0001 with someone thinking
> that's bus/dev/fn, if we're being really petty.
':' is also reserved for alias interfaces, the old way of assigning
multiple IP addresses.
I would say '-' is a good separator, but that might result in ambiguity
in IRQ names.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-18 2:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 22:06 extended netdevice naming proposal Matt Domsch
2010-11-17 22:06 ` Matt Domsch
2010-11-18 0:39 ` Ben Hutchings
2010-11-18 2:10 ` Bill Nottingham
2010-11-18 2:10 ` Bill Nottingham
2010-11-18 2:29 ` Ben Hutchings [this message]
2010-11-18 18:51 ` Matt Domsch
2010-11-18 18:51 ` Matt Domsch
2010-11-18 19:00 ` Ben Hutchings
2010-11-18 18:34 ` Rick Jones
2010-11-18 18:34 ` Rick Jones
2010-11-18 18:52 ` Matt Domsch
2010-11-18 18:52 ` Matt Domsch
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=1290047397.3818.3.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=Matt_Domsch@dell.com \
--cc=jcm@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=narendra_k@dell.com \
--cc=netdev@vger.kernel.org \
--cc=notting@redhat.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.