qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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] vhost-user: multiqueue support
Date: Mon, 08 Dec 2014 08:58:21 -0700	[thread overview]
Message-ID: <5485CA9D.60107@redhat.com> (raw)
In-Reply-To: <20141206165241.4064.61867.stgit@i3820>

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On 12/06/2014 09:52 AM, Nikolay Nikolaev wrote:
> Vhost-user will implement the multiqueueu support in a similar way to what
> vhost already has - a separate thread for each queue.
> 
> To enable multiquue funcionality - a new command line parameter
> "queues" is introduced for the vhost-user netdev.
> 
> Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
> ---

> @@ -2208,12 +2208,15 @@
>  #
>  # @vhostforce: #optional vhost on for non-MSIX virtio guests (default: false).
>  #
> +# @queues: #optional number of queues to be created for multiqueue vhost-user

Missing a '(since 2.3)' designation.  What is the default when it is
omitted?

-- 
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: 539 bytes --]

  parent reply	other threads:[~2014-12-08 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06 16:52 [Qemu-devel] [PATCH] vhost-user: multiqueue support Nikolay Nikolaev
2014-12-08  9:04 ` Olivier MATZ
2014-12-08  9:41   ` Michael S. Tsirkin
2014-12-08 15:58 ` Eric Blake [this message]
2015-01-21 14:25 ` Michael S. Tsirkin
2015-01-22  8:14   ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev

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=5485CA9D.60107@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).