From: Tim Small <tim@seoss.co.uk>
To: Narendra_K@Dell.com
Cc: greg@kroah.com, netdev@vger.kernel.org,
linux-hotplug@vger.kernel.org, linux-pci@vger.kernel.org,
Matt_Domsch@Dell.com, Charles_Rose@Dell.com,
Jordan_Hargrave@Dell.com, Vijay_Nijhawan@Dell.com
Subject: Re: [PATCH] Use firmware provided index to register a network interface
Date: Thu, 07 Oct 2010 14:27:00 +0000 [thread overview]
Message-ID: <4CADD8B4.10102@seoss.co.uk> (raw)
In-Reply-To: <20101007141433.GA2641@libnet-test.oslab.blr.amer.dell.com>
On 07/10/10 15:14, Narendra_K@Dell.com wrote:
> Yes, firmware and BIOS tables can be buggy. How about a command line
> parameter 'no_netfwindex', passing which firmware index will not be
> used to derive ethN names ? That would handle the scenario of buggy
> firmware and names will be derived in the now existing way.
>
> I will submit a patch shortly implementing this.
>
What was the reason for not doing this in user space again? You stated
that you got races when doing renames like eth0 -> eth2, but the
solution looked like renaming into a different name space such as eth0
-> ethlom2 etc. so that it wouldn't race with the names handed out by
the kernel?
Tim.
WARNING: multiple messages have this Message-ID (diff)
From: Tim Small <tim@seoss.co.uk>
To: Narendra_K@Dell.com
Cc: greg@kroah.com, netdev@vger.kernel.org,
linux-hotplug@vger.kernel.org, linux-pci@vger.kernel.org,
Matt_Domsch@Dell.com, Charles_Rose@Dell.com,
Jordan_Hargrave@Dell.com, Vijay_Nijhawan@Dell.com
Subject: Re: [PATCH] Use firmware provided index to register a network interface
Date: Thu, 07 Oct 2010 15:27:00 +0100 [thread overview]
Message-ID: <4CADD8B4.10102@seoss.co.uk> (raw)
In-Reply-To: <20101007141433.GA2641@libnet-test.oslab.blr.amer.dell.com>
On 07/10/10 15:14, Narendra_K@Dell.com wrote:
> Yes, firmware and BIOS tables can be buggy. How about a command line
> parameter 'no_netfwindex', passing which firmware index will not be
> used to derive ethN names ? That would handle the scenario of buggy
> firmware and names will be derived in the now existing way.
>
> I will submit a patch shortly implementing this.
>
What was the reason for not doing this in user space again? You stated
that you got races when doing renames like eth0 -> eth2, but the
solution looked like renaming into a different name space such as eth0
-> ethlom2 etc. so that it wouldn't race with the names handed out by
the kernel?
Tim.
next prev parent reply other threads:[~2010-10-07 14:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 18:31 [PATCH] Use firmware provided index to register a network interface Narendra K
2010-09-22 18:31 ` Narendra K
2010-09-22 19:22 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-22 19:22 ` [PATCH] Use firmware provided index to register a network interface Greg KH
2010-09-23 15:10 ` Narendra_K
2010-09-23 15:22 ` Narendra_K
2010-09-23 15:27 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 15:27 ` [PATCH] Use firmware provided index to register a network interface Greg KH
2010-09-23 15:50 ` Narendra_K
2010-09-23 15:51 ` Narendra_K
2010-09-23 16:33 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 16:33 ` [PATCH] Use firmware provided index to register a network interface Greg KH
2010-10-07 14:14 ` Narendra_K
2010-10-07 14:26 ` [PATCH] Use firmware provided index to register a network Narendra_K
2010-10-07 14:27 ` Tim Small [this message]
2010-10-07 14:27 ` [PATCH] Use firmware provided index to register a network interface Tim Small
2010-10-07 14:31 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-10-07 14:31 ` [PATCH] Use firmware provided index to register a network interface Greg KH
2010-09-22 22:07 ` Tim Small
2010-09-22 22:07 ` Tim Small
2010-09-22 22:16 ` [PATCH] Use firmware provided index to register a network Stephen Hemminger
2010-09-22 22:16 ` [PATCH] Use firmware provided index to register a network interface Stephen Hemminger
2010-09-23 6:34 ` Tim Small
2010-09-23 6:34 ` Tim Small
2010-09-23 15:13 ` Narendra_K
2010-09-23 15:25 ` Narendra_K
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=4CADD8B4.10102@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Vijay_Nijhawan@Dell.com \
--cc=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@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 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.