From: jiangyiwen <jiangyiwen@huawei.com>
To: Jason Wang <jasowang@redhat.com>, <stefanha@redhat.com>
Cc: <netdev@vger.kernel.org>, <kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/5] VSOCK: support mergeable rx buffer in vhost-vsock
Date: Tue, 6 Nov 2018 10:17:45 +0800 [thread overview]
Message-ID: <5BE0F9C9.2080003@huawei.com> (raw)
In-Reply-To: <b9d535f8-ddc3-a4bc-21c9-ca21e808f0d1@redhat.com>
On 2018/11/5 17:21, Jason Wang wrote:
>
> On 2018/11/5 下午3:43, jiangyiwen wrote:
>> Now vsock only support send/receive small packet, it can't achieve
>> high performance. As previous discussed with Jason Wang, I revisit the
>> idea of vhost-net about mergeable rx buffer and implement the mergeable
>> rx buffer in vhost-vsock, it can allow big packet to be scattered in
>> into different buffers and improve performance obviously.
>>
>> I write a tool to test the vhost-vsock performance, mainly send big
>> packet(64K) included guest->Host and Host->Guest. The result as
>> follows:
>>
>> Before performance:
>> Single socket Multiple sockets(Max Bandwidth)
>> Guest->Host ~400MB/s ~480MB/s
>> Host->Guest ~1450MB/s ~1600MB/s
>>
>> After performance:
>> Single socket Multiple sockets(Max Bandwidth)
>> Guest->Host ~1700MB/s ~2900MB/s
>> Host->Guest ~1700MB/s ~2900MB/s
>>
>> From the test results, the performance is improved obviously, and guest
>> memory will not be wasted.
>
>
> Hi:
>
> Thanks for the patches and the numbers are really impressive.
>
> But instead of duplicating codes between sock and net. I was considering to use virtio-net as a transport of vsock. Then we may have all existed features likes batching, mergeable rx buffers and multiqueue. Want to consider this idea? Thoughts?
>
>
Hi Jason,
I am not very familiar with virtio-net, so I am afraid I can't give too
much effective advice. Then I have several problems:
1. If use virtio-net as a transport, guest should see a virtio-net
device instead of virtio-vsock device, right? Is vsock only as a
transport between socket and net_device? User should still use
AF_VSOCK type to create socket, right?
2. I want to know if this idea has already started, and how is
the current progress?
3. And what is stefan's idea?
Thanks,
Yiwen.
>>
>> ---
>>
>> Yiwen Jiang (5):
>> VSOCK: support fill mergeable rx buffer in guest
>> VSOCK: support fill data to mergeable rx buffer in host
>> VSOCK: support receive mergeable rx buffer in guest
>> VSOCK: modify default rx buf size to improve performance
>> VSOCK: batch sending rx buffer to increase bandwidth
>>
>> drivers/vhost/vsock.c | 135 +++++++++++++++++++++++------
>> include/linux/virtio_vsock.h | 15 +++-
>> include/uapi/linux/virtio_vsock.h | 5 ++
>> net/vmw_vsock/virtio_transport.c | 147 ++++++++++++++++++++++++++------
>> net/vmw_vsock/virtio_transport_common.c | 59 +++++++++++--
>> 5 files changed, 300 insertions(+), 61 deletions(-)
>>
>
> .
>
next prev parent reply other threads:[~2018-11-06 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 7:43 [PATCH 0/5] VSOCK: support mergeable rx buffer in vhost-vsock jiangyiwen
2018-11-05 9:21 ` Jason Wang
2018-11-06 2:17 ` jiangyiwen [this message]
2018-11-06 2:41 ` Jason Wang
2018-11-06 3:17 ` jiangyiwen
2018-11-06 3:32 ` Jason Wang
2018-11-06 5:53 ` jiangyiwen
2018-11-29 14:19 ` Stefan Hajnoczi
2018-11-30 12:52 ` Jason Wang
2018-12-03 6:08 ` jiangyiwen
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=5BE0F9C9.2080003@huawei.com \
--to=jiangyiwen@huawei.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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).