>> > This series incorporates all of v1 plus the following changes based
>on
>> > feedback to date:
>> >
>>
>> Are you positioning this as an alternative to virtio?  If so, be
aware
>> that virtio is (a) mostly done (b) very well done.
>>
>> Can you describe what you are trying to achieve that virtio doesn't
>do?
>
>As far as I can tell, Gregory in angling to take over the virtio work
8)
>
>Given how little cycles I've been able to spare recently, I think it's
a
>good idea.

It is a good idea if the current implementatin is enhanced instead of
being replaced.
I also like to move in small steps each time:
 - Implement a simple virtio backend for KVM. I just made it work, 
   using userspace only part.
 - Make it stable and support all sort of options (config mac,
multicast, gso,..)
 - Improve performance by having the backend in-kernel.
 - Once we have a clear view of a good implementation, we can generalize
it by
   a layer similat to IOQ or lguest_dma. IMHO lguest is well written
(and documented, 
   cheers Rusty) and we should take/generalize as much code as possible
instead of 
   rewriting it. 

So bottom line, what we like to see in KVM is very similar to lguest's
bus/dma.
Maybe those can be generelized in a similar way to virtio, while keeping
the code
itslef and code style identical.

btw: Rusty, I tried to apply the new-io-lguest* patches and they failed
to apply cleanly.
What base repo do you use for that?

>
>I'm not particularly attached to the current virtio implementation,
>although I think the interface is getting pretty close.  I'd love to
see
>Gregory take over the implementation part...

If the above is followed, any enhancement will be appriciated.


>
>Rusty.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to