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>:
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.