From: Stefano Garzarella <sgarzare@redhat.com>
To: netdev@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH RFC 0/4] vsock/virtio: optimizations to increase the throughput
Date: Thu, 4 Apr 2019 12:58:34 +0200 [thread overview]
Message-ID: <20190404105838.101559-1-sgarzare@redhat.com> (raw)
This series tries to increase the throughput of virtio-vsock with slight
changes:
- patch 1/4: reduces the number of credit update messages sent to the
transmitter
- patch 2/4: allows the host to split packets on multiple buffers,
in this way, we can remove the packet size limit to
VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE
- patch 3/4: uses VIRTIO_VSOCK_MAX_PKT_BUF_SIZE as the max packet size
allowed
- patch 4/4: increases RX buffer size to 64 KiB (affects only host->guest)
RFC:
- maybe patch 4 can be replaced with multiple queues with different
buffer sizes or using EWMA to adapt the buffer size to the traffic
- as Jason suggested in a previous thread [1] I'll evaluate to use
virtio-net as transport, but I need to understand better how to
interface with it, maybe introducing sk_buff in virtio-vsock.
Any suggestions?
Here some benchmarks step by step. I used iperf3 [2] modified with VSOCK
support:
host -> guest [Gbps]
pkt_size before opt. patch 1 patches 2+3 patch 4
64 0.060 0.102 0.102 0.096
256 0.22 0.40 0.40 0.36
512 0.42 0.82 0.85 0.74
1K 0.7 1.6 1.6 1.5
2K 1.5 3.0 3.1 2.9
4K 2.5 5.2 5.3 5.3
8K 3.9 8.4 8.6 8.8
16K 6.6 11.1 11.3 12.8
32K 9.9 15.8 15.8 18.1
64K 13.5 17.4 17.7 21.4
128K 17.9 19.0 19.0 23.6
256K 18.0 19.4 19.8 24.4
512K 18.4 19.6 20.1 25.3
guest -> host [Gbps]
pkt_size before opt. patch 1 patches 2+3
64 0.088 0.100 0.101
256 0.35 0.36 0.41
512 0.70 0.74 0.73
1K 1.1 1.3 1.3
2K 2.4 2.4 2.6
4K 4.3 4.3 4.5
8K 7.3 7.4 7.6
16K 9.2 9.6 11.1
32K 8.3 8.9 18.1
64K 8.3 8.9 25.4
128K 7.2 8.7 26.7
256K 7.7 8.4 24.9
512K 7.7 8.5 25.0
Thanks,
Stefano
[1] https://www.spinics.net/lists/netdev/msg531783.html
[2] https://github.com/stefano-garzarella/iperf/
Stefano Garzarella (4):
vsock/virtio: reduce credit update messages
vhost/vsock: split packets to send using multiple buffers
vsock/virtio: change the maximum packet size allowed
vsock/virtio: increase RX buffer size to 64 KiB
drivers/vhost/vsock.c | 35 ++++++++++++++++++++-----
include/linux/virtio_vsock.h | 3 ++-
net/vmw_vsock/virtio_transport_common.c | 18 +++++++++----
3 files changed, 44 insertions(+), 12 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-04 10:58 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 10:58 Stefano Garzarella [this message]
2019-04-04 10:58 ` [PATCH RFC 1/4] vsock/virtio: reduce credit update messages Stefano Garzarella
2019-04-04 10:58 ` Stefano Garzarella
2019-04-04 19:15 ` Stefan Hajnoczi
2019-04-04 19:15 ` Stefan Hajnoczi
2019-04-05 8:16 ` Stefano Garzarella
2019-04-08 9:25 ` Stefan Hajnoczi
2019-04-08 9:25 ` Stefan Hajnoczi
2019-04-05 8:16 ` Stefano Garzarella
2019-04-04 10:58 ` [PATCH RFC 2/4] vhost/vsock: split packets to send using multiple buffers Stefano Garzarella
2019-04-04 10:58 ` Stefano Garzarella
2019-04-05 8:13 ` Stefan Hajnoczi
2019-04-05 8:13 ` Stefan Hajnoczi
2019-04-05 9:36 ` Stefano Garzarella
2019-04-08 9:28 ` Stefan Hajnoczi
2019-04-08 9:28 ` Stefan Hajnoczi
2019-04-05 9:36 ` Stefano Garzarella
2019-04-04 10:58 ` [PATCH RFC 3/4] vsock/virtio: change the maximum packet size allowed Stefano Garzarella
2019-04-04 10:58 ` Stefano Garzarella
2019-04-05 8:24 ` Stefan Hajnoczi
2019-04-05 8:24 ` Stefan Hajnoczi
2019-04-05 10:07 ` Stefano Garzarella
2019-04-05 10:07 ` Stefano Garzarella
2019-04-08 9:37 ` Stefan Hajnoczi
2019-04-08 9:37 ` Stefan Hajnoczi
2019-04-08 14:55 ` Stefano Garzarella
2019-04-08 14:55 ` Stefano Garzarella
2019-04-08 14:57 ` Michael S. Tsirkin
2019-04-08 15:17 ` Stefano Garzarella
2019-04-08 15:17 ` Stefano Garzarella
2019-04-08 15:45 ` Stefan Hajnoczi
2019-04-08 15:45 ` Stefan Hajnoczi
2019-04-08 14:57 ` Michael S. Tsirkin
2019-04-04 10:58 ` [PATCH RFC 4/4] vsock/virtio: increase RX buffer size to 64 KiB Stefano Garzarella
2019-04-05 8:44 ` Stefan Hajnoczi
2019-04-05 8:44 ` Stefan Hajnoczi
2019-04-08 6:35 ` Jason Wang
2019-04-08 6:35 ` Jason Wang
2019-04-04 10:58 ` Stefano Garzarella
2019-04-04 14:14 ` [PATCH RFC 0/4] vsock/virtio: optimizations to increase the throughput Stefan Hajnoczi
2019-04-04 15:44 ` Stefano Garzarella
2019-04-04 15:44 ` Stefano Garzarella
2019-04-04 14:14 ` Stefan Hajnoczi
2019-04-04 15:52 ` Michael S. Tsirkin
2019-04-04 16:47 ` Stefano Garzarella
2019-04-04 16:47 ` Stefano Garzarella
2019-04-04 18:04 ` Michael S. Tsirkin
2019-04-05 7:49 ` Stefano Garzarella
2019-04-08 9:23 ` Stefan Hajnoczi
2019-04-08 9:23 ` Stefan Hajnoczi
2019-04-05 7:49 ` Stefano Garzarella
2019-04-04 18:04 ` Michael S. Tsirkin
2019-04-04 15:52 ` Michael S. Tsirkin
2019-04-08 6:43 ` Jason Wang
2019-04-08 6:43 ` Jason Wang
2019-04-08 9:44 ` Stefan Hajnoczi
2019-04-08 9:44 ` Stefan Hajnoczi
2019-04-09 8:36 ` Jason Wang
2019-04-09 8:36 ` Jason Wang
2019-04-09 9:13 ` Stefano Garzarella
2019-04-09 9:13 ` Stefano Garzarella
2019-04-04 10:58 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=20190404105838.101559-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.