aboutsummaryrefslogtreecommitdiff
path: root/hw/ipmi
diff options
context:
space:
mode:
authorLaurent Vivier <lvivier@redhat.com>2023-06-05 16:21:25 +0200
committerJason Wang <jasowang@redhat.com>2023-07-07 16:35:12 +0800
commit4271f4038372f174dbafffacca1a748d058a03ba (patch)
treec778d370b2cf213ff1da974ce032045f9522a40d /hw/ipmi
parent97c81ef4b8e203d9620fd46e7eb77004563e3675 (diff)
downloadqemu-4271f4038372f174dbafffacca1a748d058a03ba.zip
qemu-4271f4038372f174dbafffacca1a748d058a03ba.tar.gz
qemu-4271f4038372f174dbafffacca1a748d058a03ba.tar.bz2
virtio-net: correctly report maximum tx_queue_size value
Maximum value for tx_queue_size depends on the backend type. 1024 for vDPA/vhost-user, 256 for all the others. The value is returned by virtio_net_max_tx_queue_size() to set the parameter: n->net_conf.tx_queue_size = MIN(virtio_net_max_tx_queue_size(n), n->net_conf.tx_queue_size); But the parameter checking uses VIRTQUEUE_MAX_SIZE (1024). So the parameter is silently ignored and ethtool reports a different value than the one provided by the user. ... -netdev tap,... -device virtio-net,tx_queue_size=1024 # ethtool -g enp0s2 Ring parameters for enp0s2: Pre-set maximums: RX: 256 RX Mini: n/a RX Jumbo: n/a TX: 256 Current hardware settings: RX: 256 RX Mini: n/a RX Jumbo: n/a TX: 256 ... -netdev vhost-user,... -device virtio-net,tx_queue_size=2048 Invalid tx_queue_size (= 2048), must be a power of 2 between 256 and 1024 With this patch the correct maximum value is checked and displayed. For vDPA/vhost-user: Invalid tx_queue_size (= 2048), must be a power of 2 between 256 and 1024 For all the others: Invalid tx_queue_size (= 512), must be a power of 2 between 256 and 256 Fixes: 2eef278b9e63 ("virtio-net: fix tx queue size for !vhost-user") Cc: mst@redhat.com Cc: qemu-stable@nongnu.org Signed-off-by: Laurent Vivier <lvivier@redhat.com> Signed-off-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'hw/ipmi')
0 files changed, 0 insertions, 0 deletions