From: jiangyiwen <jiangyiwen@huawei.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>, <netdev@vger.kernel.org>,
<kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH v2 0/5] VSOCK: support mergeable rx buffer in vhost-vsock
Date: Fri, 14 Dec 2018 17:39:29 +0800 [thread overview]
Message-ID: <5C137A51.20505@huawei.com> (raw)
In-Reply-To: <20181213163409.GP23318@stefanha-x1.localdomain>
On 2018/12/14 0:34, Stefan Hajnoczi wrote:
> On Wed, Dec 12, 2018 at 05:25:50PM +0800, 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.
>
> Sorry, I've been a bad maintainer. I was focussed on other projects and
> my email backlog is huge.
>
> I like the idea of trying out optimizations on virtio-vsock, seeing if
> code can be shared with virtio-net, and maybe later switching to a
> virtio-net transport for vsock (if it turns out enough code can be
> shared).
>
> Another optimization that could be interesting:
>
> Userspace processes reading from a socket sleep in
> vsock_stream_recvmsg(). I wonder if we can bypass struct
> virtio_vsock_pkt and copying the payload into pkt->buf in this case.
> (This doesn't improve poll(2)/select(2) though!)
>
> Imagine a userspace process waiting for data on a socket. When the
> virtqueue becomes ready, we can read in struct virtio_vsock_hdr and find
> the socket for that connection. Then we could copy the payload directly
> to userspace instead of creating a virtio_vsock_pkt and copying to
> pkt->buf first.
>
Great, I also consider the optimization point later.
Then, I will send the next version based on your suggestions.
Thanks,
Yiwen.
next prev parent reply other threads:[~2018-12-14 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 9:25 [PATCH v2 0/5] VSOCK: support mergeable rx buffer in vhost-vsock jiangyiwen
2018-12-12 15:09 ` Michael S. Tsirkin
2018-12-12 15:09 ` Michael S. Tsirkin
2018-12-13 2:14 ` jiangyiwen
2018-12-13 2:14 ` jiangyiwen
2018-12-14 10:24 ` jiangyiwen
2018-12-14 13:22 ` Michael S. Tsirkin
2018-12-14 13:22 ` Michael S. Tsirkin
2018-12-14 10:24 ` jiangyiwen
2018-12-13 16:34 ` Stefan Hajnoczi
2018-12-13 16:34 ` Stefan Hajnoczi
2018-12-14 9:39 ` jiangyiwen
2018-12-14 9:39 ` jiangyiwen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 9:25 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=5C137A51.20505@huawei.com \
--to=jiangyiwen@huawei.com \
--cc=jasowang@redhat.com \
--cc=kvm@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.