From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: alex.bennee@linaro.org, netdev@vger.kernel.org,
qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] VSOCK benchmark and optimizations
Date: Wed, 3 Apr 2019 13:34:38 +0100 [thread overview]
Message-ID: <20190403123438.GE32425@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190401163240.xw24ezsloy5ds2hz@steredhat>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Mon, Apr 01, 2019 at 06:32:40PM +0200, Stefano Garzarella wrote:
> Hi Alex,
> I'm sending you some benchmarks and information about VSOCK CCing qemu-devel
> and linux-netdev (maybe this info could be useful for others :))
>
> One of the VSOCK advantages is the simple configuration: you don't need to set
> up IP addresses for guest/host, and it can be used with the standard POSIX
> socket API. [1]
>
> I'm currently working on it, so the "optimized" values are still work in
> progress and I'll send the patches upstream (Linux) as soon as possible.
> (I hope in 1 or 2 weeks)
>
> Optimizations:
> + reducing the number of credit update packets
> - RX side sent, on every packet received, an empty packet only to inform the
> TX side about the space in the RX buffer.
> + increase RX buffers size to 64 KB (from 4 KB)
> + merge packets to fill RX buffers
>
> As benchmark tool I used iperf3 [2] modified with VSOCK support:
>
> host -> guest [Gbps] guest -> host [Gbps]
> pkt_size before opt. optimized before opt. optimized
> 1K 0.5 1.6 1.4 1.4
This is a "large" small package size. I think 64 bytes is a common
"small" packet size and is worth benchmarking too.
> 2K 1.1 3.1 2.3 2.5
> 4K 2.0 5.6 4.2 4.4
> 8K 3.2 10.2 7.2 7.5
> 16K 6.4 14.2 9.4 11.3
> 32K 9.8 18.9 9.2 17.8
> 64K 13.8 22.9 8.8 25.0
> 128K 17.6 24.5 7.7 25.7
> 256K 19.0 24.8 8.1 25.6
> 512K 20.8 25.1 8.1 25.4
Nice improvements!
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-04-03 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 16:32 VSOCK benchmark and optimizations Stefano Garzarella
2019-04-02 4:19 ` Alex Bennée
2019-04-02 7:37 ` Stefano Garzarella
2019-04-03 12:36 ` [Qemu-devel] " Stefan Hajnoczi
2019-04-04 10:47 ` Stefano Garzarella
2019-04-03 12:34 ` Stefan Hajnoczi [this message]
2019-04-03 15:10 ` [Qemu-devel] " Stefano Garzarella
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=20190403123438.GE32425@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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