Re: [PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-20 Thread Or Gerlitz
Michael S. Tsirkin wrote: Yes. master okay, will get testing this later next week. Any chance you can provide some packet-per-second numbers (netperf udp stream with small packets)? Or. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to

Re: [PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-20 Thread Michael S. Tsirkin
On Thu, Aug 20, 2009 at 04:34:39PM +0300, Or Gerlitz wrote: Michael S. Tsirkin wrote: Yes. master okay, will get testing this later next week. Any chance you can provide some packet-per-second numbers (netperf udp stream with small packets)? Or. If you do, maybe you should apply the

Re: [PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-19 Thread Or Gerlitz
Michael S. Tsirkin wrote: The patches are against 2.6.31-rc4. I'd like them to go into linux-next and down the road 2.6.32 if possible. Please comment. Hi Michael, Just wanted to make sure with you how this can be tested, is 2.6.31-rc4 plus these two patches enough to form the kernel part?

Re: [PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-19 Thread Or Gerlitz
Michael S. Tsirkin wrote: No, these patches are on top of Avi's kvm.git so are they on top of some branch in Avi's kvm.git which is planned to be merged for 2.6.32? what branch should I use? Or. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to

Re: [PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-19 Thread Michael S. Tsirkin
On Wed, Aug 19, 2009 at 04:44:02PM +0300, Or Gerlitz wrote: Michael S. Tsirkin wrote: No, these patches are on top of Avi's kvm.git so are they on top of some branch in Avi's kvm.git which is planned to be merged for 2.6.32? what branch should I use? Yes. master Or. -- To unsubscribe

[PATCHv3 0/2] vhost: a kernel-level virtio server

2009-08-13 Thread Michael S. Tsirkin
This implements vhost: a kernel-level backend for virtio, The main motivation for this work is to reduce virtualization overhead for virtio by removing system calls on data path, without guest changes. For virtio-net, this removes up to 4 system calls per packet: vm exit for kick, reentry for