qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: jiangyiwen@huawei.com
Cc: Michael Tsirkin <mst@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	netdev@vger.kernel.org, qemu devel list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] VSOCK performance
Date: Tue, 29 Jan 2019 12:39:32 +0100	[thread overview]
Message-ID: <CAGxU2F6_Raw8gAW-ug1EKGKhpCnhgdbv6VQKo7E_L4zMRSEs0w@mail.gmail.com> (raw)

Hi Yiwen,
I'm currently interested on how to improve the VSOCK performance and I
read your discussions with Jason, Michael, and Stefan on both
linux-netdev and qemu-devel mailing lists.

Are you still working on it?

Reading the discussions I understood that batching can help us a lot
to increase the VSOCK performance (especially for guest->host
direction).

As a first step, I added VSOCK support to iperf3 [1] in order to
measure the current performance of VSOCK (without any modification):

              Single socket
Guest->Host        ~950MB/s
Host->Guest       ~2700MB/s

They are slightly different from your results but I think that depends
on the hardware.
My current setup is the following:
HW: Lenovo T480s (i7-8650U, DDR4 2133 Mhz)
OS (guest/host): Fedora 29 (Linux 4.20.4-200.fc29.x86_64)
Guest app: iperf3 --vsock -s
Host app:  iperf3 --vsock -c $GUEST_CID -l 64K


Just to double check these values, can you share with me the tool that you used?


Thanks,
Stefano

#1 https://github.com/esnet/iperf/pull/840

-- 
Stefano Garzarella
Software Engineer @ Red Hat

                 reply	other threads:[~2019-01-29 11:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGxU2F6_Raw8gAW-ug1EKGKhpCnhgdbv6VQKo7E_L4zMRSEs0w@mail.gmail.com \
    --to=sgarzare@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jiangyiwen@huawei.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).