On Tue, 2014-11-18 at 18:12 -0700, Bjorn Helgaas wrote: > > Can you help me understand this? > > We have previously called sriov_init() on the PF. There, we sized the VF > BARs, which are in the PF's SR-IOV Capability (SR-IOV spec sec 3.3.14). > The size we discover is the amount of space required by a single VF, so > sriov_init() adjusts PF->resource[PCI_IOV_RESOURCES + i] by multiplying > that size by PCI_SRIOV_TOTAL_VF, so this PF resource is now big enough to > hold the VF BAR[i] areas for all the possible VFs. So I'll let Richard (Wei) answer on the details but I'll just chime in about the "big picture". This isn't about changing the spacing between VFs which is handled by the system page size. This is about the way we create MMIO windows from the CPU to the VF BARs. Basically, we have a (limited) set of 64-bit windows we can create that are divided in equal sized segments (256 of them), each segment assigned in HW to one of our Partitionable Endpoints (aka domain). So even if we only ever create 16 VFs for a device, we need to use an entire of these windows, which will use 256*VF_size and thus allocate that much space. Also the window has to be naturally aligned. We can then assign the VF BAR to a spot inside that window that corresponds to the range of PEs that we have assigned to that device (which typically isn't going to be the beginning of the window). Cheers, Ben. -- 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
