From: Alberto Faria <afaria@redhat.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Alberto Faria" <afaria@redhat.com>
Subject: [PATCH 0/2] virtio-blk: Add support for FUA write requests
Date: Wed, 21 Oct 2026 07:22:55 +0100 [thread overview]
Message-ID: <20261021062257.735757-1-afaria@redhat.com> (raw)
virtio-blk FUA write support has been introduced to the virtio spec [1], and a
kernel patch is under review [2]. This patch enables FUA on the virtio-blk
device, so guests can submit FUA writes instead of the slower alternative of a
regular write followed by a flush.
A simple randwrite fio workload on a RAM disk (bs=4k, iodepth=1, direct=1,
sync=1) shows a throughput improvement of 17.1k IOPS to 27.7k IOPS (+62%).
[1] https://lore.kernel.org/virtio-comment/20251112055113.62207-1-afaria@redhat.com/
[2] https://lore.kernel.org/linux-block/20261021055235.648957-1-afaria@redhat.com/
Alberto Faria (2):
include: Add virtio-blk request flag FUA definitions
virtio-blk: Add support for FUA write requests
hw/block/virtio-blk.c | 27 +++++++++++++++++++++
hw/core/machine.c | 1 +
hw/virtio/virtio-qmp.c | 4 +++
include/hw/virtio/virtio-blk.h | 1 +
include/standard-headers/linux/virtio_blk.h | 13 ++++++++--
5 files changed, 44 insertions(+), 2 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-21 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:22 Alberto Faria [this message]
2026-10-21 6:22 ` [PATCH 1/2] include: Add virtio-blk request flag FUA definitions Alberto Faria
2026-10-21 7:59 ` Cornelia Huck
2026-10-21 12:22 ` Kevin Wolf
2026-10-21 12:37 ` Cornelia Huck
2026-10-21 6:22 ` [PATCH 2/2] virtio-blk: Add support for FUA write requests Alberto Faria
2026-10-28 19:55 ` 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=20261021062257.735757-1-afaria@redhat.com \
--to=afaria@redhat.com \
--cc=cohuck@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhao1.liu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.