diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2025-03-11 21:26:14 +0800 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2025-03-13 17:57:23 +0100 |
| commit | 2e8e18c2e46307a355e547129b5a7a7000a0cf0d (patch) | |
| tree | 1a8bd7a36fb921fc9c7b1f7422296bdbdaef5167 /scripts/qcow2-to-stdout.py | |
| parent | b50629c335804e193b51936867d6cb7ea3735d72 (diff) | |
| download | focaccia-qemu-2e8e18c2e46307a355e547129b5a7a7000a0cf0d.tar.gz focaccia-qemu-2e8e18c2e46307a355e547129b5a7a7000a0cf0d.zip | |
virtio-scsi: add iothread-vq-mapping parameter
Allow virtio-scsi virtqueues to be assigned to different IOThreads. This makes it possible to take advantage of host multi-queue block layer scalability by assigning virtqueues that have affinity with vCPUs to different IOThreads that have affinity with host CPUs. The same feature was introduced for virtio-blk in the past: https://developers.redhat.com/articles/2024/09/05/scaling-virtio-blk-disk-io-iothread-virtqueue-mapping Here are fio randread 4k iodepth=64 results from a 4 vCPU guest with an Intel P4800X SSD: iothreads IOPS ------------------------------ 1 189576 2 312698 4 346744 Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Message-ID: <20250311132616.1049687-12-stefanha@redhat.com> Tested-by: Peter Krempa <pkrempa@redhat.com> [kwolf: Updated 051 output, virtio-scsi can now use any iothread] Reviewed-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'scripts/qcow2-to-stdout.py')
0 files changed, 0 insertions, 0 deletions