From: Matt Domsch <Matt_Domsch@Dell•com>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: Narendra_K@Dell•com, netdev@vger•kernel.org,
Charles_Rose@Dell•com, Jordan_Hargrave@Dell•com,
linux-pci@vger•kernel.org, linux-hotplug@vger•kernel.org
Subject: Re: [PATCH] Add firmware label support to iproute2
Date: Thu, 26 Aug 2010 11:38:55 -0500 [thread overview]
Message-ID: <20100826163855.GA6774@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <20100826150116.GB21770@auslistsprd01.us.dell.com>
On Thu, Aug 26, 2010 at 10:01:16AM -0500, Matt Domsch wrote:
> On Wed, Aug 25, 2010 at 05:16:46PM -0700, Stephen Hemminger wrote:
> > On Wed, 25 Aug 2010 17:03:23 -0500
> On Wed, Aug 25, 2010 at 05:16:46PM -0700, Stephen Hemminger wrote:
> > Is it really a good idea to have to change every utility that could
> > alter network devices? There is iproute2, iputils, tcpdump, wireshark,
> > quagga, snmp, ... Many of the utilities come from a BSD world,
> > and will be less likely to accept some Linux specific wart.
>
> I agree, I don't want to have to change all those userspace apps
> either. We've started creating patches and are willing to do so if it
> will yield the result we want though.
>
> > I have lost faith in this library wrapper support everywhere method.
> > Let's just keep the firmware stuff in udev. If the user wants to
> > have a policy that renames device from eth0 to "Embedded BIOS LAN1" then
> > do it in udev. Or if you want to keep the ethX naming convention
> > and stuff the firmware label into ifAlias or other sysfs field
> > so it can be displayed that will be not a big issue.
>
> 1) we remain constrained to IFNAMSIZ named arguments. There is no
> such constraint on BIOS-provided names. Dell BIOS presently uses
> 'Embedded NIC 1' which (fortunately) is 14 chars. We're cutting it
> awfully close already. I can't dictate to non-Dell BIOS vendors
> what to use as their strings, or how long to make them.
vlan usage requires 5 characters from IFNAMSIZ (eth0.4095). So my
example with 'Embedded NIC 1' plus a vlan doesn't fit.
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
prev parent reply other threads:[~2010-08-26 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 17:35 [PATCH] Add firmware label support to iproute2 Narendra K
2010-08-12 18:10 ` Stephen Hemminger
2010-08-12 18:12 ` Stephen Hemminger
2010-08-13 12:36 ` Narendra_K
2010-08-18 21:41 ` Stephen Hemminger
2010-08-19 21:33 ` Matt Domsch
2010-08-19 21:53 ` Stephen Hemminger
2010-08-19 22:18 ` Matt Domsch
2010-08-25 22:03 ` Matt Domsch
2010-08-25 22:16 ` Greg KH
2010-08-26 14:10 ` Matt Domsch
2010-08-26 0:16 ` Stephen Hemminger
2010-08-26 15:01 ` Matt Domsch
2010-08-26 15:17 ` Loke, Chetan
2010-08-26 15:21 ` Stephen Hemminger
2010-08-26 15:38 ` Loke, Chetan
2010-08-27 7:54 ` Kay Sievers
2010-08-26 16:38 ` Matt Domsch [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=20100826163855.GA6774@auslistsprd01.us.dell.com \
--to=matt_domsch@dell$(echo .)com \
--cc=Charles_Rose@Dell$(echo .)com \
--cc=Jordan_Hargrave@Dell$(echo .)com \
--cc=Narendra_K@Dell$(echo .)com \
--cc=linux-hotplug@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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