From: Klaus Jensen <its@irrelevant.dk>
To: Jinhao Fan <fanjinhao21s@ict.ac.cn>
Cc: qemu-devel@nongnu.org, kbusch@kernel.org
Subject: Re: [PATCH] hw/nvme: Add iothread support
Date: Fri, 26 Aug 2022 09:11:23 +0200 [thread overview]
Message-ID: <YwhyG3JktHitinMW@apples> (raw)
In-Reply-To: <20220720090053.309229-1-fanjinhao21s@ict.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Jul 20 17:00, Jinhao Fan wrote:
> Add an option "iothread=x" to do emulation in a seperate iothread.
> This improves the performance because QEMU's main loop is responsible
> for a lot of other work while iothread is dedicated to NVMe emulation.
> Moreover, emulating in iothread brings the potential of polling on
> SQ/CQ doorbells, which I will bring up in a following patch.
>
> Iothread can be enabled by:
> -object iothread,id=nvme0 \
> -device nvme,iothread=nvme0 \
>
> Performance comparisons (KIOPS):
>
> QD 1 4 16 64
> QEMU 41 136 242 338
> iothread 53 155 245 309
>
> Signed-off-by: Jinhao Fan <fanjinhao21s@ict.ac.cn>
> ---
> hw/nvme/ctrl.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++----
> hw/nvme/ns.c | 19 +++++++++---
> hw/nvme/nvme.h | 6 +++-
> 3 files changed, 95 insertions(+), 10 deletions(-)
>
Jinhao,
Are you gonna respin this based on the irqfd patches? I suggest you just
add this work on top and post a series that is irqfd+iothread. Then, if
we find the irqfd ready for merge, we can pick that up for the next
release cycle early and continue on iothread work.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-26 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 9:00 [PATCH] hw/nvme: Add iothread support Jinhao Fan
2022-07-26 8:55 ` Jinhao Fan
2022-07-26 14:45 ` Keith Busch
2022-07-26 15:32 ` Jinhao Fan
2022-07-26 18:07 ` Keith Busch
2022-07-27 2:56 ` Jinhao Fan
2022-07-27 6:29 ` Jinhao Fan
2022-07-27 7:03 ` Klaus Jensen
2022-08-26 7:11 ` Klaus Jensen [this message]
2022-08-26 8:15 ` Jinhao Fan
2022-08-26 8:41 ` 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=YwhyG3JktHitinMW@apples \
--to=its@irrelevant.dk \
--cc=fanjinhao21s@ict.ac.cn \
--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.