[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4916DE5E.6070805@redhat.com>
Date: Sun, 09 Nov 2008 14:58:06 +0200
From: Avi Kivity <avi@...hat.com>
To: Greg KH <greg@...ah.com>
CC: Anthony Liguori <anthony@...emonkey.ws>,
Matthew Wilcox <matthew@....cx>, H L <swdevyid@...oo.com>,
Yu Zhao <yu.zhao@...el.com>, randy.dunlap@...cle.com,
grundler@...isc-linux.org, achiang@...com,
linux-pci@...r.kernel.org, rdreier@...co.com,
linux-kernel@...r.kernel.org, jbarnes@...tuousgeek.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
mingo@...e.hu, Chris Wright <chrisw@...s-sol.org>
Subject: Re: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support
Greg KH wrote:
>> We've been talking about avoiding hardware passthrough entirely and
>> just backing a virtio-net backend driver by a dedicated VF in the
>> host. That avoids a huge amount of guest-facing complexity, let's
>> migration Just Work, and should give the same level of performance.
>>
>
> Does that involve this patch set? Or a different type of interface.
>
So long as the VF is exposed as a standalone PCI device, it's the same
interface. In fact you can take a random PCI card and expose it to a
guest this way; it doesn't have to be SR-IOV. Of course, with a
standard PCI card you won't get much sharing (a quad port NIC will be
good for four guests).
We'll need other changes in the network stack, but these are orthogonal
to SR-IOV.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists