diff options
| author | Stefan Hajnoczi | 2019-06-24 11:13:04 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin | 2019-07-25 10:17:34 +0200 |
| commit | df98d7ccc2e9e3e5080cce30a6d9c09dd827dc15 (patch) | |
| tree | 1c5bbe58759b3af462d764282a5058094745ccc0 /fsdev | |
| parent | Update version for v4.1.0-rc2 release (diff) | |
| download | qemu-df98d7ccc2e9e3e5080cce30a6d9c09dd827dc15.tar.gz qemu-df98d7ccc2e9e3e5080cce30a6d9c09dd827dc15.tar.xz qemu-df98d7ccc2e9e3e5080cce30a6d9c09dd827dc15.zip | |
docs: clarify multiqueue vs multiple virtqueues
The vhost-user specification does not explain when
VHOST_USER_PROTOCOL_F_MQ must be implemented. This may lead
implementors of vhost-user masters to believe that this protocol feature
is required for any device that has multiple virtqueues. That would be
a mistake since existing vhost-user slaves offer multiple virtqueues but
do not advertise VHOST_USER_PROTOCOL_F_MQ.
For example, a vhost-net device with one rx/tx queue pair is not
multiqueue. The slave does not need to advertise
VHOST_USER_PROTOCOL_F_MQ. Therefore the master must assume it has these
virtqueues and cannot rely on askingt the slave how many virtqueues
exist.
Extend the specification to explain the different between true
multiqueue and regular devices with a fixed virtqueue layout.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20190624091304.666-1-stefanha@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Diffstat (limited to 'fsdev')
0 files changed, 0 insertions, 0 deletions