On 05/19/2017 11:10 AM, Jason Wang wrote:
On 2017年05月18日 11:03, Wei Wang wrote:
On 05/17/2017 02:22 PM, Jason Wang wrote:
We can analyze from the whole data path - from VM1's network stack to
send packets -> VM2's
network stack to receive packets. The number of copies are actually
the same for both.
On 2017年05月17日 14:16, Jason Wang wrote:
On 2017年05月16日 15:12, Wei Wang wrote:
OK. It may take some time to clean up the driver code before post
it out. You can first
Care to post the driver codes too?
have a check of the draft at the repo here:
Interesting, looks like there's one copy on tx side. We used to
have zerocopy support for tun for VM2VM traffic. Could you please
try to compare it with your vhost-pci-net by:
That's why I'm asking you to compare the performance. The only reason
for vhost-pci is performance. You should prove it.
vhost-pci: 1-copy happen in VM1's driver xmit(), which copes packets
from its network stack to VM2's
RX ring buffer. (we call it "zerocopy" because there is no
intermediate copy between VMs)
zerocopy enabled vhost-net: 1-copy happen in tun's recvmsg, which
copies packets from VM1's TX ring
buffer to VM2's RX ring buffer.
Actually, there's a major difference here. You do copy in guest which
consumes time slice of vcpu thread on host. Vhost_net do this in its
own thread. So I feel vhost_net is even faster here, maybe I was wrong.
The code path using vhost_net is much longer - the Ping test shows that
the zcopy based vhost_net reports around 0.237ms,
while using vhost-pci it reports around 0.06 ms.
For some environment issue, I can report the throughput number later.
That being said, we compared to vhost-user, instead of vhost_net,
because vhost-user is the one
that is used in NFV, which we think is a major use case for vhost-pci.
If this is true, why not draft a pmd driver instead of a kernel one?
Yes, that's right. There are actually two directions of the vhost-pci
driver implementation - kernel driver
and dpdk pmd. The QEMU side device patches are first posted out for
discussion, because when the device
part is ready, we will be able to have the related team work on the pmd
driver as well. As usual, the pmd
driver would give a much better throughput.
So, I think at this stage we should focus on the device part review, and
use the kernel driver to prove that
the device part design and implementation is reasonable and functional.
And do you use virtio-net kernel driver to compare the performance? If
yes, has OVS dpdk optimized for kernel driver (I think not)?
We used the legacy OVS+DPDK.
Another thing with the existing OVS+DPDK usage is its centralization
property. With vhost-pci, we will be able to
de-centralize the usage.
What's more important, if vhost-pci is faster, I think its kernel
driver should be also faster than virtio-net, no?
Sorry about the confusion. We are actually not trying to use vhost-pci
to replace virtio-net. Rather, vhost-pci
can be viewed as another type of backend for virtio-net to be used in
NFV (the communication channel is