Virtual functions numbering (SRIOV) - why odd numbers are not used ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,
I had noticed that whenever I create virtual function on Nic devices,
the numbering scheme is the same:
the the last digit of first VF is .0, of the second one is .2, the
third is .4, and so on; and no odd number are used.

For example, with Intel IXGBE nic, we have:


echo 4 > /sys/bus/pci/devices/0000:06:00.0/sriov_numvfs

lspci | grep "Virtual Function"
06:10.0 Ethernet controller: Intel Corporation 82599 Ethernet
Controller Virtual Function (rev 01)
06:10.2 Ethernet controller: Intel Corporation 82599 Ethernet
Controller Virtual Function (rev 01)
06:10.4 Ethernet controller: Intel Corporation 82599 Ethernet
Controller Virtual Function (rev 01)
06:10.6 Ethernet controller: Intel Corporation 82599 Ethernet
Controller Virtual Function (rev 01)

Does anybody know what is the reason that odd numbers are not used ?
are they kept for something else ?
For example, why don't we get : 06:10.0,06:10.1,06:10.2,06:10.3 in this case ?

Regards,
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux