RE: [PATCH 19/25] mlx4: Randomizing mac addresses for slaves
From: Liran Liss <hidden>
Date: 2009-11-05 13:38:18
Also in:
linux-rdma
This approach seems to be common practice now (e.g., drivers/net/igb/igb_main.c:1332). In any case, the user can change the randomized mac. --Liran -----Original Message----- From: Or Gerlitz [mailto:or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] Sent: Wednesday, November 04, 2009 11:33 PM To: Roland Dreier Cc: Yevgeny Petrilin; linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; netdev-u79uwXL29TaqPxH82wqD4g@public.gmane.orgg; Liran Liss; Tziporet Koren Subject: Re: [PATCH 19/25] mlx4: Randomizing mac addresses for slaves On Wed, Nov 4, 2009 at 10:04 PM, Roland Dreier [off-list ref] wrote:
quoted
+#define MLX4_MAC_HEAD 0x2c9000000ULL
Is this a good idea? You're basically choosing 24 random bits within your OUI... seems the chance of collision with another MAC used on the same network is high enough that it could easily happen in practice on a moderately big network.
yes, this has been brought by Stephen and others on this last back on September 11th, this year @ http://marc.info/?l=linux-netdev&m=125263488409128
Can you pick a reserved range or something?
Using different OUI for the VF device wouldn't help either I think, since the #VF becomes fairly big even on a modest side cluster with (say) a VM consuming VF per 1-2 cores. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html