when to relize the Paravirtualized networking ?

when to relize the Paravirtualized networking ?

[vast yellow]

[-- Attachment #1.1: Type: text/plain, Size: 171 bytes --]

Anyone know when to release include the following features
Paravirtualized networking
Paravirtualized block device KVM Tap network is slower than Xen. Can we
optimize it?

[-- Attachment #1.2: Type: text/html, Size: 267 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: when to relize the Paravirtualized networking ?

[Dor Laor]

[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]

vast yellow wrote:
>
> Anyone know when to release include the following features
>
> # Paravirtualized networking
I have such a code in a separate git repository. It is not yet 
production ready.
The next release is a rebase of Rusty code for virtio and some KVM/Qemu 
backend.
It probably be ready in few weeks.
> # Paravirtualized block device
The effort is not big since Rusty has paved most of the way.
Some qemu block handling needs to be done. Again it can happen in 1-2 
months.
> KVM Tap network is slower than Xen. Can we optimize it?
>  
Are you talking about PV driver or fully virtualized nic?
Dor.

[-- Attachment #1.2: Type: text/html, Size: 1353 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: when to relize the Paravirtualized networking ?

[vast yellow]

[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]

Do you know the difference in code to improve the tap network between the
release kvm-44 and the release kvm45?
which modify can improve the tap network performace?How is the work flow of
tap network in kvm?
Why the qemu process use 100% cpu in host?


2007/10/3, Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>
> vast yellow wrote:
>
> Anyone know when to release include the following features
> Paravirtualized networking
>
> I have such a code in a separate git repository. It is not yet production
> ready.
> The next release is a rebase of Rusty code for virtio and some KVM/Qemu
> backend.
> It probably be ready in few weeks.
>
> Paravirtualized block device
>
> The effort is not big since Rusty has paved most of the way.
> Some qemu block handling needs to be done. Again it can happen in 1-2
> months.
>
> KVM Tap network is slower than Xen. Can we optimize it?
>
>
> Are you talking about PV driver or fully virtualized nic?
> Dor.
>
>

[-- Attachment #1.2: Type: text/html, Size: 1519 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: when to relize the Paravirtualized networking ?

[Dor Laor]

[-- Attachment #1.1: Type: text/plain, Size: 1380 bytes --]

vast yellow wrote:
> Do you know the difference in code to improve the tap network between 
> the release kvm-44 and the release kvm45?
> which modify can improve the tap network performace?How is the work 
> flow of tap network in kvm?
The change is to trigger a signal to qemu when data is ready on the tap fd.
It will mainly improve latency. The change is not kvm specific and 
applicable to qemu too
> Why the qemu process use 100% cpu in host?
>
This might be a bug. What is the guest doing? Can you run the kvm_stat 
script?
>  
> 2007/10/3, Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <mailto:dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>>:
>
>     vast yellow wrote:
>>
>>     Anyone know when to release include the following features
>>
>>   # Paravirtualized networking
>     I have such a code in a separate git repository. It is not yet
>     production ready.
>     The next release is a rebase of Rusty code for virtio and some
>     KVM/Qemu backend.
>     It probably be ready in few weeks.
>>   # Paravirtualized block device
>     The effort is not big since Rusty has paved most of the way.
>     Some qemu block handling needs to be done. Again it can happen in
>     1-2 months.
>>     KVM Tap network is slower than Xen. Can we optimize it?
>>      
>     Are you talking about PV driver or fully virtualized nic?
>     Dor.
>      
>
>


[-- Attachment #1.2: Type: text/html, Size: 2579 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel