Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
909 Views

ixgbe: 82599: how PF driver ensures that MAC address given to each VF is unique

Hello,

I am trying to use ixgbe driver for Inel 82599 10G dual port card.

I observed the PF driver assigning randomly generated MAC addresses (generated by random_eth_addr()) to VFs.

How does PF driver ensures that MAC address given to each VF is unique?

Thanks in advance.

Regards,

Veerasena.

0 Kudos
1 Reply
GREGORY_R_Intel
Employee
53 Views

The randomly generated ethernet addresses are not guaranteed to be unique. They usually are but there is no guarantee. Mostly they serve as placeholders for testing and development. For real world usage I recommend that you use the latest iproute2 package's "ip link set" commands to set the Virtual Function devices' MAC addresses administratively. You'll also need to use a 2.6.34 or later Linux kernel. Or if you'd like to you can use Xen 4.0.1 with the upstream stable 2.6.32.x PVOPs kernel. You can then download and install the latest ixgbe driver from Sourceforge which is Rev 2.0.84.11. That also supports the iproute2 "ip link set" commands.

Here's an example from my own Xen 4.0.1 development machine. To set the MAC addresses for 4 VF's for Physical Function interface eth3:

/usr/sbin/ip link set eth3 vf 0 mac 00:01:02:BA:BB:00

 

/usr/sbin/ip link set eth3 vf 1 mac 00:01:02:BA:BB:01

 

/usr/sbin/ip link set eth3 vf 2 mac 00:01:02:BA:BB:02

 

/usr/sbin/ip link set eth3 vf 3 mac 00:01:02:BA:BB:03

If you run "ipi link show eth3" after setting the VF MAC addresses you get the following output:

8: eth3: mtu 1500 qdisc noop state DOWN qlen 1000

 

link/ether 00:1b:21:3c:a3:1c brd ff:ff:ff:ff:ff:ff

 

vf 0 MAC 00:01:02:ba:bb:00

 

vf 1 MAC 00:01:02:ba:bb:01

 

vf 2 MAC 00:01:02:ba:bb:02

 

vf 3 MAC 00:01:02:ba:bb:03

Using these methods you can guarantee that you are assigning a unique MAC address. This is the best known method for avoiding accidental MAC address collisions.

Edited to make it clear that if you use the upstream Xen stable-2.6.32.x PVOPs kernel you cannot use the in-kernel version of ixgbe for SR-IOV. In-kernel support for SR-IOV on the ixgbe driver did not get in place until 2.6.34.

Reply