[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100721.113906.102700682.davem@davemloft.net>
Date: Wed, 21 Jul 2010 11:39:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: leedom@...lsio.com
Cc: shemminger@...tta.com, andy@...yhouse.net, harald@...hat.com,
bhutchings@...arflare.com, sassmann@...hat.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
gospo@...hat.com, gregory.v.rose@...el.com,
alexander.h.duyck@...el.com
Subject: Re: [PATCH net-next] sysfs: add entry to indicate network
interfaces with random MAC address
From: Casey Leedom <leedom@...lsio.com>
Date: Wed, 21 Jul 2010 11:29:47 -0700
> Another option might be to have a new Net Device Operations call to ask the
> adapter for a Unique Key. This could be formed for most devices via a tuple of
> the {PCI Vendor ID, PCI Device ID, Adapter Serial Number, Port Number, [and if
> applicable] Adapter Function ID}. Of course this could be a fairly long string
> ... :-)
If a unique key were available, it could be used to generate a persistent
MAC address.
And this sort of means that these drivers could use bits of the
device's geographic ID the construct persistent MAC addresses, but
only if done in a MAC namespace that could be guarenteed unique on the
local system.
--
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