[removed cc ksummit-2012-discuss] On Wed, Aug 29, 2012 at 3:54 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > On Wed, Aug 29, 2012 at 3:44 PM, Jon Mason <jdmason@xxxxxxxx> wrote: >>> Hi Bjorn, >>> One of my team member reported another corner case for SR-IOV. There's >>> are two NIC cards in the system driven by the same driver, but one supports >>> SR-IOV and the other doesn't. It runs into trouble if "max_vfs" parameter is >>> set for the NIC driver. >>> --Gerry >> >> I believe it was decided that a per-pf sysfs interface would be used >> to replace the current module parameter that specifies the number of >> vf's. This should enable different numbers of vf's for each physical >> device. The driver interface that was discussed would introduce new >> function pointers for handlers to setup/teardown the vf's. I believe >> this will solve your problem once it has been implemented. > > now we have ixgbe.max_vfs=63 > > so if change to per pci device (PF), > > how about having the driver built-in? > what kind of kernel parameters will be passed? I don't think we really discussed things at this level, and I personally don't know enough about the current SR-IOV support to even know what the possible strategies are. I think it's really up to the person doing the implementation to figure out what makes sense given the constraints of the SR-IOV specs and the current Linux support. Bjorn -- 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
