Vhost thread provide both tx and rx ability for virtio-net. In the forwarding scenarios, tx and rx share the vhost thread, and throughput is limited by single thread. So I did a patch for provide vhost thread per virtqueue, not per vhost_net. Of course, multi-queue virtio-net is final solution, but it require new version of virtio-net working in guest. If you have to work with suse10,11, redhat 5.x as guest, and want to improve the forward throughput, using vhost thread per queue seems to be the only solution. I did the test with kernel 3.0.27 and qemu-1.4.0, guest is suse11-sp2, and then two vhost thread provide double tx/rx forwarding performance than signal vhost thread. The virtqueue of vhost_blk is 1, so it still use one vhost thread without change. Is there something wrong in this solution? If not, I would list patch later. Best regards King -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
