From: Stefan Hajnoczi <stefanha@redhat.com>
To: jiangyiwen <jiangyiwen@huawei.com>
Cc: netdev@vger.kernel.org, Jorgen Hansen <jhansen@vmware.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC] VSOCK: About Virtio-vsock support "Multiqueue" feature ?
Date: Thu, 29 Nov 2018 14:06:47 +0000 [thread overview]
Message-ID: <20181129140647.GB17554@stefanha-x1.localdomain> (raw)
In-Reply-To: <5BBB0203.1010400@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
On Mon, Oct 08, 2018 at 03:06:43PM +0800, jiangyiwen wrote:
> Hi Stefan & All:
>
> Now virtio-vsock only supports two vqs(tx and rx), that means
> if multiple sockets in the guest will use the same vq to transmit
> the message and get the response. In this way, the bandwidth will
> be limited to ~700MB/s. So if there are multiple applications in
> the guest, we should support "Multiqueue" feature for Virtio-vsock.
>
> I want to know whether we already have plans to support multiqueue
> or already have simple demo that can be used. If not, I will try
> to implement this feature.
Multiqueue is certainly interesting. It would be interesting to see
if/how it affects common net/vmw_vsock/ code. Hopefully nothing much
will change there but I haven't checked if any common locking would
prevent multiqueue from working efficiently.
Stefan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2018-11-29 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 7:06 [RFC] VSOCK: About Virtio-vsock support "Multiqueue" feature ? jiangyiwen
2018-11-29 14:06 ` Stefan Hajnoczi [this message]
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=20181129140647.GB17554@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=jhansen@vmware.com \
--cc=jiangyiwen@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).