[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091016154137.GB9862@ldl.fc.hp.com>
Date: Fri, 16 Oct 2009 09:41:37 -0600
From: dann frazier <dannf@...nf.org>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Narendra_K@...l.com, netdev@...r.kernel.org,
linux-hotplug@...r.kernel.org, Matt_Domsch@...l.com,
Jordan_Hargrave@...l.com, Charles_Rose@...l.com
Subject: Re: PATCH: Network Device Naming mechanism and policy
On Fri, Oct 16, 2009 at 04:33:13PM +0100, Ben Hutchings wrote:
> On Fri, 2009-10-16 at 09:20 -0600, dann frazier wrote:
> > On Fri, Oct 16, 2009 at 07:32:50PM +0530, Narendra_K@...l.com wrote:
> [...]
> > > And how would the regular file look like in terms of holding ifindex of
> > > the interface, which can be passed to libnetdevname.
> >
> > I can't think of anything we need to store in the regular file. If we
> > have the kernel name for the device, we can look up the ifindex in
> > /sys. Correct me if I'm wrong, but storing it ourselves seems
> > redundant.
>
> But the name of a netdev can change whereas its ifindex never does.
> Identifying netdevs by name would require additional work to update the
> links when a netdev is renamed and would still be prone to race
> conditions. This is why Narendra and Matt were proposing to store the
> ifindex in the node all along...
ah, yes - I see that now - the ability to rename an interface is what
prevents this from working. Thanks for the explanation.
--
dann frazier
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists