lkml.org 
[lkml]   [2008]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support
Anthony Liguori wrote:
> Matthew Wilcox wrote:
>> [Anna, can you fix your word-wrapping please? Your lines appear to be
>> infinitely long which is most unpleasant to reply to]
>>
>> On Thu, Nov 06, 2008 at 05:38:16PM +0000, Fischer, Anna wrote:
>>
>>>> Where would the VF drivers have to be associated? On the "pci_dev"
>>>> level or on a higher one?
>>>>
>>> A VF appears to the Linux OS as a standard (full, additional) PCI
>>> device. The driver is associated in the same way as for a normal PCI
>>> device. Ideally, you would use SR-IOV devices on a virtualized system,
>>> for example, using Xen. A VF can then be assigned to a guest domain as
>>> a full PCI device.
>>>
>>
>> It's not clear thats the right solution. If the VF devices are _only_
>> going to be used by the guest, then arguably, we don't want to create
>> pci_devs for them in the host. (I think it _is_ the right answer, but I
>> want to make it clear there's multiple opinions on this).
>>
>
> The VFs shouldn't be limited to being used by the guest.

Yes, VF driver running in the host is supported :-)

>
> SR-IOV is actually an incredibly painful thing. You need to have a VF
> driver in the guest, do hardware pass through, have a PV driver stub in
> the guest that's hypervisor specific (a VF is not usable on it's own),
> have a device specific backend in the VMM, and if you want to do live
> migration, have another PV driver in the guest that you can do teaming
> with. Just a mess.

Actually not so mess. VF driver can be a plain PCI device driver and
doesn't require any backend in the VMM, or hypervisor specific
knowledge, if the hardware is properly designed. In this case PF driver
controls hardware resource allocation for VFs and VF driver can work
without any communication to PF driver or VMM.

>
> What we would rather do in KVM, is have the VFs appear in the host as
> standard network devices. We would then like to back our existing PV
> driver to this VF directly bypassing the host networking stack. A key
> feature here is being able to fill the VF's receive queue with guest
> memory instead of host kernel memory so that you can get zero-copy
> receive traffic. This will perform just as well as doing passthrough
> (at least) and avoid all that ugliness of dealing with SR-IOV in the guest.

If the hardware supports both SR-IOV and IOMMU, I wouldn't suggest
people to do so, because they will get better performance by directly
assigning VF to the guest.

However, lots of low-end machines don't have SR-IOV and IOMMU support.
They may have multi queue NIC, which uses built-in L2 switch to dispense
packets to different DMA queue according to MAC address. They definitely
can benefit a lot if there is software support for the DMA queue hooking
virtio-net backend as you suggested.

>
> This eliminates all of the mess of various drivers in the guest and all
> the associated baggage of doing hardware passthrough.
>
> So IMHO, having VFs be usable in the host is absolutely critical because
> I think it's the only reasonable usage model.

Please don't worry, we have take this usage model as well as container
model into account when designing SR-IOV framework for the kernel.

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



\
 
 \ /
  Last update: 2008-11-07 17:13    [W:0.148 / U:4.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site