RE: nic enumeration

Loke, Chetan
2010-07-08T22:07:29Z

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2518 bytes --]

> -----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 <ayf@youtube.com> wrote:
> > On Thu, Jul 8, 2010 at 1:36 PM, Loke, Chetan
> <Chetan.Loke@netscout.com> 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Ç+‰·Ÿ®‰­†+%ŠËÿ±éÝ¶\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dÊ‡Ú™ë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥