Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758661Ab0GHWH3 (ORCPT ); Thu, 8 Jul 2010 18:07:29 -0400 Received: from exprod6og115.obsmtp.com ([64.18.1.35]:35343 "HELO exprod6og115.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755983Ab0GHWH2 (ORCPT ); Thu, 8 Jul 2010 18:07:28 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: RE: nic enumeration Date: Thu, 8 Jul 2010 18:07:24 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: nic enumeration Thread-Index: Acse5HJkaTf/he5oTpSCNzgReQlGAgAAgRog References: <20100708012120.GB11419@auslistsprd01.us.dell.com> From: "Loke, Chetan" To: "Kay Sievers" , "Andrew Fong" Cc: "Matt Domsch" , "Michael Di Domenico" , , X-OriginalArrivalTime: 08 Jul 2010 22:07:25.0506 (UTC) FILETIME=[F282C220:01CB1EE9] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha.home.local id o68M7YV6031949 Content-Length: 2518 Lines: 52 > -----Original Message----- > From: Kay Sievers [mailto:kay.sievers@vrfy.org] > Sent: July 08, 2010 5:28 PM > To: Andrew Fong > Cc: Loke, Chetan; Matt Domsch; Michael Di Domenico; linux- > net@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: nic enumeration > > On Thu, Jul 8, 2010 at 22:47, Andrew Fong wrote: > > On Thu, Jul 8, 2010 at 1:36 PM, Loke, Chetan > wrote: > >>> -----Original Message----- > >>> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel- > >>> owner@vger.kernel.org] On Behalf Of Matt Domsch > >>> Sent: July 07, 2010 9:21 PM > >>> > >>> http://lwn.net/Articles/356900/ > >>> > >>> And on a system where you can use udev rules, the > >>> 70-persistent-net.rules file can be used to make them constant, by > >>> using the MAC address to force the names to be what you want. > >> > >> Ok, but can we achieve the renaming w/o a reboot? > > > > You probably can restart the udev subsystem. > > No, udev has not really a concept of being restarted, it will not do > anything. You can only synthesize events, so it looks like the device > is just plugged in. For that, you need to make sure the interface is > not busy, otherwise renaming will fail in interesting ways, especially > if names need to be swapped between several devices. > I'm not a udev guru so I don't know how will renaming a simple net_device->name work? What about the msi-x queues created by the driver? May be I missed it but I don't see a single driver tearing apart everything and restarting unless a NETDEV_RENAME somehow automagically reloads the driver. I know it's silly for the driver to tear apart the whole world. But then why allow renaming in the first place, correct? > Live renaming of interfaces is something you really need to know what > you are doing, especially on remote machines. > I agree, I wanted someone to say 'try the symlink attrib'. I really need to create a 'symlink' or a reference to the newly added 'ethX' interface. I have to support 75+ VMs(each w/ 5+ vNICs) and I can't [re]name the newly added vNIC and then reboot. Rebooting 75+ VMs is non-practical. Adding a new vNIC is as simple as point-and-click and the guest sees the new vNIC. The VM doesn't need to reboot. How do I achieve this 'symlinking' effect minus the reboot? > Kay Regards Chetan Loke ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?