[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] value of VIRTQUEUE_MAX_SIZE
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] value of VIRTQUEUE_MAX_SIZE |
Date: |
Thu, 5 Feb 2015 14:00:29 +0000 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
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?
Stefan
pgpkTO_McatLM.pgp
Description: PGP signature
- Re: [Qemu-devel] value of VIRTQUEUE_MAX_SIZE,
Stefan Hajnoczi <=