Hey Kevin, This is basically because of udevd calling modprobe when the new VFs are created. The code in the ixgbe driver that causes the VFs to be created would be the function call "pci_enable_sriov()". This brings about a chain of events resulting in the ixgbevf getting loaded. I assume you want to assign the VFs to VMs rather than have ixgbevf load and take control of the VFs. So, you will have to black list the ixgbevf driver in your host operating system. For more information on the udev, udevd and modprobe check out (section 7.4.2.4) : http://www.linuxfromscratch.org/lfs/view/6.4/chapter07/udev.html - Biju On Mon, Mar 23, 2015 at 11:15 AM, Kevin Wilson <wkevils@xxxxxxxxx> wrote: > Hi, > I have an x86_64 machine (F21) on which ixgbevf is not loaded. > I notices that when running > modprobe ixgbevf max_vfs = 10 (or any other number), this triggers > loading of ixgbevf driver. > I will appreciate if someone can exaplain the implementation details > of how does this happen. > I could not find what in the ixgbe driver code triggers this action > > Regards, > Kevni > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
