[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4A8BAC750200005A00052A83@sinclair.provo.novell.com>
Date: Wed, 19 Aug 2009 05:40:37 -0600
From: "Gregory Haskins" <ghaskins@...ell.com>
To: "Avi Kivity" <avi@...hat.com>
Cc: "Anthony Liguori" <anthony@...emonkey.ws>,
"Ingo Molnar" <mingo@...e.hu>,
"Gregory Haskins" <gregory.haskins@...il.com>,
<alacrityvm-devel@...ts.sourceforge.net>,
"Michael S. Tsirkin" <mst@...hat.com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model for
vbus_driver objects
>>> On 8/19/2009 at 3:13 AM, in message <4A8BA635.9010902@...hat.com>, Avi Kivity
<avi@...hat.com> wrote:
> On 08/19/2009 09:40 AM, Gregory Haskins wrote:
>>
>>
>>>> So if I whip up a virtio-net backend for vbus with a PCI compliant
>>>> connector, you are happy?
>>>>
>>>>
>>> This doesn't improve virtio-net in any way.
>>>
>> Any why not? (Did you notice I said "PCI compliant", i.e. over virtio-pci)
>>
>
> Because virtio-net will have gained nothing that it didn't have before.
??
*) ABI is virtio-pci compatible, as you like
*) fast-path is in-kernel, as we all like
*) model is in vbus so it would work in all environments that vbus supports.
>
>
>
>
>>> virtio already supports this model; see lguest and s390. Transporting
>>> virtio over vbus and vbus over something else doesn't gain anything over
>>> directly transporting virtio over that something else.
>>>
>> This is not what I am advocating.
>>
>>
>
> What are you advocating? As far as I can tell your virtio-vbus
> connector plus the vbus-kvm connector is just that.
I wouldn't classify it anything like that, no. Its just virtio over vbus.
-Greg
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists