From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Xu" <peterx@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
pkrempa@redhat.com, "John Snow" <jsnow@redhat.com>
Subject: [PATCH v2 00/13] virtio-scsi: add iothread-vq-mapping parameter
Date: Tue, 11 Mar 2025 18:11:32 +0800 [thread overview]
Message-ID: <20250311101145.1037388-1-stefanha@redhat.com> (raw)
v2:
- Only expose cmd vqs via iothread-vq-mapping [Kevin, Peter]
Implement --device virtio-scsi-pci,iothread-vq-mapping= support so that
virtqueues can be assigned to different IOThreads. This improves SMP guest
scalability where I/O-intensive applications can become bottlenecked on a
single IOThread.
The following benchmark results show the effect of iothread-vq-mapping. fio
randread 4k iodepth=64 results from a 4 vCPU guest with an Intel P4800X SSD:
iothreads IOPS
------------------------------
1 189576
2 312698
4 346744
The virtio-scsi device model and core SCSI emulation currently assume that
requests are processed in a single AioContext. This patch series goes about
modifying this as follows:
scsi-disk: drop unused SCSIDiskState->bh field
dma: use current AioContext for dma_blk_io()
Make dma-helpers.c support the QEMU multi-queue block layer by using
qemu_get_current_aio_context().
scsi: track per-SCSIRequest AioContext
scsi: introduce requests_lock
Make the core SCSI emulation code support processing requests in multiple
AioContexts by protecting the per-SCSIDevice requests list.
virtio-scsi: introduce event and ctrl virtqueue locks
virtio-scsi: protect events_dropped field
virtio-scsi: perform TMFs in appropriate AioContexts
Make the virtio-scsi emulation code support processing requests in multiple
AioContexts. The event and ctrl virtqueues can interact with multiple
AioContexts. Especially the SCSI Task Management Functions (TMFs) handled by
the ctrl virtqueue need to be made thread-safe.
virtio-blk: extract cleanup_iothread_vq_mapping() function
virtio-blk: tidy up iothread_vq_mapping functions
virtio: extract iothread-vq-mapping.h API
virtio-scsi: add iothread-vq-mapping parameter
Port over the iothread-vq-mapping qdev property from virtio-blk to virtio-scsi.
virtio-scsi: handle ctrl virtqueue in main loop
Simplify TMF handling now that there is no longer a single AioContext where all
requests are processed.
virtio-scsi: only expose cmd vqs via iothread-vq-mapping
Make the user interface more intuitive.
Stefan Hajnoczi (13):
scsi-disk: drop unused SCSIDiskState->bh field
dma: use current AioContext for dma_blk_io()
scsi: track per-SCSIRequest AioContext
scsi: introduce requests_lock
virtio-scsi: introduce event and ctrl virtqueue locks
virtio-scsi: protect events_dropped field
virtio-scsi: perform TMFs in appropriate AioContexts
virtio-blk: extract cleanup_iothread_vq_mapping() function
virtio-blk: tidy up iothread_vq_mapping functions
virtio: extract iothread-vq-mapping.h API
virtio-scsi: add iothread-vq-mapping parameter
virtio-scsi: handle ctrl virtqueue in main loop
virtio-scsi: only expose cmd vqs via iothread-vq-mapping
include/hw/scsi/scsi.h | 8 +-
include/hw/virtio/iothread-vq-mapping.h | 45 ++
include/hw/virtio/virtio-scsi.h | 15 +-
include/system/dma.h | 3 +-
hw/block/virtio-blk.c | 132 +-----
hw/ide/core.c | 3 +-
hw/ide/macio.c | 3 +-
hw/scsi/scsi-bus.c | 121 ++++--
hw/scsi/scsi-disk.c | 24 +-
hw/scsi/virtio-scsi-dataplane.c | 103 +++--
hw/scsi/virtio-scsi.c | 542 ++++++++++++++----------
hw/virtio/iothread-vq-mapping.c | 131 ++++++
system/dma-helpers.c | 8 +-
hw/virtio/meson.build | 1 +
14 files changed, 683 insertions(+), 456 deletions(-)
create mode 100644 include/hw/virtio/iothread-vq-mapping.h
create mode 100644 hw/virtio/iothread-vq-mapping.c
--
2.48.1
next reply other threads:[~2025-03-11 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 10:11 Stefan Hajnoczi [this message]
2025-03-11 10:11 ` [PATCH v2 01/13] scsi-disk: drop unused SCSIDiskState->bh field Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 02/13] dma: use current AioContext for dma_blk_io() Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 03/13] scsi: track per-SCSIRequest AioContext Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 04/13] scsi: introduce requests_lock Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 05/13] virtio-scsi: introduce event and ctrl virtqueue locks Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 06/13] virtio-scsi: protect events_dropped field Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 07/13] virtio-scsi: perform TMFs in appropriate AioContexts Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 08/13] virtio-blk: extract cleanup_iothread_vq_mapping() function Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 09/13] virtio-blk: tidy up iothread_vq_mapping functions Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 10/13] virtio: extract iothread-vq-mapping.h API Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 11/13] virtio-scsi: add iothread-vq-mapping parameter Stefan Hajnoczi
2025-03-11 12:06 ` Kevin Wolf
2025-03-11 10:11 ` [PATCH v2 12/13] virtio-scsi: handle ctrl virtqueue in main loop Stefan Hajnoczi
2025-03-11 10:11 ` [PATCH v2 13/13] virtio-scsi: only expose cmd vqs via iothread-vq-mapping Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250311101145.1037388-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=david@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).