From: Jinhao Fan <fanjinhao21s@ict.ac.cn>
To: qemu-devel@nongnu.org
Cc: its@irrelevant.dk, kbusch@kernel.org,
Jinhao Fan <fanjinhao21s@ict.ac.cn>
Subject: [PATCH v3 0/2] hw/nvme: Add shadow doorbell buffer support
Date: Thu, 16 Jun 2022 20:34:06 +0800 [thread overview]
Message-ID: <20220616123408.3306055-1-fanjinhao21s@ict.ac.cn> (raw)
This patch adds shadow doorbell buffer support in NVMe 1.3 to QEMU
NVMe. The Doorbell Buffer Config admin command is implemented for the
guest to enable shadow doobell buffer. When this feature is enabled, each
SQ/CQ is associated with two buffers, i.e., Shadow Doorbell buffer and
EventIdx buffer. According to the Spec, each queue's doorbell register
is only updated when the Shadow Doorbell buffer value changes from being
less than or equal to the value of the corresponding EventIdx buffer
entry to being greater than that value. Therefore, the number of MMIO's
on the doorbell registers is greatly reduced.
This patch is adapted from Huaicheng Li's patch[1] in 2018.
[1] https://patchwork.kernel.org/project/qemu-devel/patch/20180305194906.GA3630@gmail.com/
IOPS comparison with FIO:
iodepth 1 2 4 8
QEMU 25.1k 25.9k 24.5k 24.0k
+dbbuf 29.1k 60.1k 99.8k 82.5k
MMIO's per IO measured by perf-kvm:
iodepth 1 2 4 8
QEMU 2.01 1.99 1.99 1.99
+dbbuf 1.00 0.52 0.27 0.46
The tests are done on Ubuntu 22.04 with 5.15.0-33 kernel with Intel(R)
Xeon(R) Gold 6248R CPU @ 3.00GHz.
QEMU set up:
bin/x86_64-softmmu/qemu-system-x86_64 \
-name "nvme-test" \
-machine accel=kvm \
-cpu host \
-smp 4 \
-m 8G \
-daemonize \
-device virtio-scsi-pci,id=scsi0 \
-device scsi-hd,drive=hd0 \
-drive file=$OSIMGF,if=none,aio=native,cache=none,format=qcow2,id=hd0,snapshot=on \
-drive "id=nvm,if=none,file=null-co://,file.read-zeroes=on,format=raw" \
-device nvme,serial=deadbeef,drive=nvm \
-net user,hostfwd=tcp::8080-:22 \
-net nic,model=virtio
FIO configuration:
[global]
ioengine=libaio
filename=/dev/nvme0n1
thread=1
group_reporting=1
direct=1
verify=0
time_based=1
ramp_time=0
runtime=30
;size=1G
;iodepth=1
rw=randread
bs=4k
[test]
numjobs=1
Changes since v2:
- Do not ignore admin queue updates in nvme_process_db and nvme_post_cqes
- Calculate db_addr and ei_addr in hard-coded way
Changes since v1:
- Add compatibility with hosts that do not use admin queue shadow doorbell
Jinhao Fan (2):
hw/nvme: Implement shadow doorbell buffer support
hw/nvme: Add trace events for shadow doorbell buffer
hw/nvme/ctrl.c | 118 ++++++++++++++++++++++++++++++++++++++++++-
hw/nvme/nvme.h | 8 +++
hw/nvme/trace-events | 5 ++
include/block/nvme.h | 2 +
4 files changed, 132 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2022-06-16 13:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:34 Jinhao Fan [this message]
2022-06-16 12:34 ` [PATCH v3 1/2] hw/nvme: Implement shadow doorbell buffer support Jinhao Fan
2022-06-27 19:17 ` Keith Busch
2022-06-27 19:33 ` Klaus Jensen
2022-06-28 0:29 ` Jinhao Fan
2022-12-07 17:49 ` Guenter Roeck
2022-12-08 7:16 ` Klaus Jensen
2022-12-08 8:08 ` Klaus Jensen
2022-12-08 18:47 ` Guenter Roeck
2022-12-08 20:13 ` Guenter Roeck
2022-12-08 20:28 ` Keith Busch
2022-12-08 21:16 ` Guenter Roeck
2022-12-08 20:39 ` Guenter Roeck
2022-12-09 11:00 ` Guenter Roeck
2022-12-12 9:58 ` Klaus Jensen
2022-12-12 13:39 ` Guenter Roeck
2022-12-12 13:45 ` Klaus Jensen
2022-12-12 14:27 ` Guenter Roeck
2022-12-12 15:18 ` Klaus Jensen
2022-06-16 12:34 ` [PATCH v3 2/2] hw/nvme: Add trace events for shadow doorbell buffer Jinhao Fan
2022-06-17 11:54 ` [PATCH v3 0/2] hw/nvme: Add shadow doorbell buffer support Klaus Jensen
2022-06-17 12:47 ` Jinhao Fan
2022-06-17 12:56 ` Klaus Jensen
2022-06-17 13:02 ` Jinhao Fan
2022-06-17 20:35 ` Keith Busch
2022-06-27 6:00 ` Klaus Jensen
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=20220616123408.3306055-1-fanjinhao21s@ict.ac.cn \
--to=fanjinhao21s@ict.ac.cn \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.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 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.