All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	ming.lei@canonical.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] value of VIRTQUEUE_MAX_SIZE
Date: Thu, 05 Feb 2015 15:29:17 +0100	[thread overview]
Message-ID: <54D37E3D.7060208@kamp.de> (raw)
In-Reply-To: <20150205140029.GF19277@stefanha-thinkpad.redhat.com>

Am 05.02.2015 um 15:00 schrieb Stefan Hajnoczi:
> On Fri, Jan 30, 2015 at 10:08:02PM +0100, Peter Lieven wrote:
>> Just wondering if VIRTQUEUE_MAX_SIZE in include/hw/virtio/virtio.h should not be equal to IOV_MAX instead of the hardcoded 1024?
> The vring queue size is guest-visible to some extent (e.g. vring memory
> layout).  Tying it to a constant that is defined by the host operating
> system could lead to problems (e.g. live migration between different
> hosts).
>
> Anyway, all of the virtio devices have a queue size that is less than or
> equal to VIRTQUEUE_MAX_SIZE (and there is an assertion to check this in
> virtio_add_queue()).
>
> Guests are supposed to honor the vring queue size, although indirect
> descriptors seem to be able to use up to VIRTQUEUE_MAX_SIZE according to
> my understanding of QEMU's virtio.c code.
>
> Why would you like to use IOV_MAX?

The idea was that IOV_MAX is the limit in case of at least virtio-blk. The host
will not support more than IOV_MAX iovecs passed to a block request.

Peter

  reply	other threads:[~2015-02-05 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 21:08 [Qemu-devel] value of VIRTQUEUE_MAX_SIZE Peter Lieven
2015-02-05 14:00 ` Stefan Hajnoczi
2015-02-05 14:29   ` Peter Lieven [this message]
2015-02-06 10:42     ` Stefan Hajnoczi
2015-02-06 10:45       ` Peter Lieven
2015-02-06 13:22         ` 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=54D37E3D.7060208@kamp.de \
    --to=pl@kamp.de \
    --cc=kwolf@redhat.com \
    --cc=ming.lei@canonical.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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 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.