From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Small Date: Thu, 07 Oct 2010 14:27:00 +0000 Subject: Re: [PATCH] Use firmware provided index to register a network interface Message-Id: <4CADD8B4.10102@seoss.co.uk> List-Id: References: <20100922183137.GA7607@auslistsprd01.us.dell.com> <20100922192228.GB29899@kroah.com> <20100923152730.GA1261@kroah.com> <20100923163336.GA15603@kroah.com> <20101007141433.GA2641@libnet-test.oslab.blr.amer.dell.com> In-Reply-To: <20101007141433.GA2641@libnet-test.oslab.blr.amer.dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 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.