From: Eric Blake <eblake@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>,
thomas.long@intel.com, snabb-devel@googlegroups.com,
qemu-devel@nongnu.org, mst@redhat.com
Cc: tech@virtualopensystems.com
Subject: Re: [Qemu-devel] [PATCH v2] vhost-user: add multi queue support
Date: Mon, 26 Jan 2015 11:51:00 -0700 [thread overview]
Message-ID: <54C68C94.9030300@redhat.com> (raw)
In-Reply-To: <20150124121851.4278.77991.stgit@s440>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
On 01/24/2015 05:22 AM, Nikolay Nikolaev wrote:
> Vhost-user will implement the multiqueueu support in a similar way to what
s/multiqueueu/multiqueue/
Also, you probably want to be consistent - is it two words (subject
line) or one word (this sentence)? I could go either way.
> vhost already has - a separate thread for each queue.
>
> To enable the multiqueue funcionality - a new command line parameter
s/funcionality/functionality/
> "queues" is introduced for the vhost-user netdev.
>
> Changes since v1:
> - use s->nc.info_str when bringing up/down the backend
This paragraph about path versioning belongs...
>
> Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
> ---
...here, after the --- separator. It is useful to reviewers, but makes
no sense in the final qemu.git repository (a year from now, we only care
about the one version that got committed, not how many tries it took to
get to that one version).
> docs/specs/vhost-user.txt | 5 +++++
> hw/virtio/vhost-user.c | 6 +++++-
> net/vhost-user.c | 39 +++++++++++++++++++++++++--------------
> qapi-schema.json | 6 +++++-
> qemu-options.hx | 5 +++--
> 5 files changed, 43 insertions(+), 18 deletions(-)
>
> diff --git a/docs/specs/vhost-user.txt b/docs/specs/vhost-user.txt
> index 650bb18..d7b208c 100644
> --- a/docs/specs/vhost-user.txt
> +++ b/docs/specs/vhost-user.txt
> @@ -127,6 +127,11 @@ in the ancillary data:
> If Master is unable to send the full message or receives a wrong reply it will
> close the connection. An optional reconnection mechanism can be implemented.
>
> +Multi queue suport
s/suport/support/
> +---------------------
Make the length of this separator match the text it is underlining (too
long, even after the typo fix)
> +++ b/qapi-schema.json
> @@ -2287,12 +2287,16 @@
> #
> # @vhostforce: #optional vhost on for non-MSIX virtio guests (default: false).
> #
> +# @queues: #optional number of queues to be created for multiqueue vhost-user
> +# (Since 2.3)
Might be worth mentioning that the default is 1.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-01-26 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 12:22 [Qemu-devel] [PATCH v2] vhost-user: add multi queue support Nikolay Nikolaev
2015-01-26 18:51 ` Eric Blake [this message]
2015-04-06 15:07 ` Michael S. Tsirkin
2015-04-08 15:18 ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev
2015-04-09 2:18 ` Ouyang, Changchun
2015-05-21 14:20 ` [Qemu-devel] [PATCH v3] " Ouyang Changchun
2015-05-21 19:03 ` Eric Blake
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=54C68C94.9030300@redhat.com \
--to=eblake@redhat.com \
--cc=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=snabb-devel@googlegroups.com \
--cc=tech@virtualopensystems.com \
--cc=thomas.long@intel.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;
as well as URLs for NNTP newsgroup(s).