[PATCH] virtio-net: set the max of queue size to 4096

From: liuhaiwei the limit of maximum of rx_queue_size and tx_queue to 1024 is so small as to affect our network performance when using the virtio-net and vhost , we cannot set the maximum size beyond 1k. why not enlarge the maximum size (such as 4096) when using the vhost backend? Signed-off

[PATCH] virtio-net: set the max of queue size to 4096 according to the virtio specs, The maximum Queue Size value is 32768 : https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x

the limit of maximum of rx_queue_size and tx_queue to 1024 is so small as to affect our network performance when using the virtio-net and vhost , we cannot set the maximum size beyond 1k. why not enlarge the maximum size (such as 4096) when using the vhost backend? Signed-off-by: liuhaiwei

[PATCH 3/3] virtio-net: set the max of queue size to 4096

Signed-off-by: liuhaiwei --- hw/net/virtio-net.c | 8 hw/virtio/virtio.c | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c index d63ef24e6a..df16995146 100644 --- a/hw/net/virtio-net.c +++ b/hw/net/virtio-net.c @@ -3479,23

[PATCH 1/3] virtio-net: fix max vring buf size when set ring num

Signed-off-by: liuhaiwei --- hw/virtio/virtio.c | 10 +++--- include/hw/virtio/virtio.h | 1 + 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c index 5d607aeaa0..d93c20d747 100644 --- a/hw/virtio/virtio.c +++ b/hw/virtio/virtio.c

[PATCH 2/3] virtio-net: update the default and max of rx/tx_queue_size

Set the max of tx_queue_size to 4096 even if the backends are not vhost-user. Set the default of rx/tx_queue_size to 2048 if the backends are vhost-user, otherwise to 4096. Signed-off-by: liuhaiwei --- hw/net/virtio-net.c | 40 ++-- 1 file changed, 30

[PATCH] bugfix:migrate with block-dirty-bitmap (disk size is big enough) can't be finished

From: liuhaiwei bug description as https://gitlab.com/qemu-project/qemu/-/issues/1203 Usually,we use the precopy or postcopy mode to migrate block dirty bitmap. but if block-dirty-bitmap size more than threshold size,we cannot entry the migration_completion in migration_iteration_run function

[PATCH] migrate block dirty bitmap: Fix the block dirty bitmap can't to migration_completion when pending size larger than threshold size

From: liuhaiwei 1、dirty bitmap size big enough (such as 8MB) when block size 1T ; 2、we set the migrate speed or the bandwith is small enough(such as 4MB/s) so we set the fake pending size when pending size > threshold size Signed-off-by: liuhaiwei Signed-off-by: liuhaiwei --- migration/bl

[PATCH] Use QMP command object-add instead of object_add for memory hotplugin

From: liuhaiwei Signed-off-by: liuhaiwei --- docs/memory-hotplug.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/memory-hotplug.txt b/docs/memory-hotplug.txt index 6aa5e17e26..85ed4d8f3d 100644 --- a/docs/memory-hotplug.txt +++ b/docs/memory-hotplug.txt

[PATCH] migrate block dirty bitmap: Fix the block dirty bitmap can't to migration_completion when pending size larger than threshold size : 1、dirty bitmap size big enough (such as 8MB) when block si

From: liuhaiwei so we set the fake pending size when pending size > threshold size Signed-off-by: liuhaiwei Signed-off-by: liuhaiwei --- migration/block-dirty-bitmap.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/migration/block-dirty-bitmap.c b/migration/bl