From: Klaus Jensen <its@irrelevant.dk>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Jinhao Fan <fanjinhao21s@ict.ac.cn>,
qemu-devel@nongnu.org, kbusch@kernel.org
Subject: Re: [PATCH 0/3] iothread and irqfd support
Date: Wed, 12 Oct 2022 16:39:44 +0200 [thread overview]
Message-ID: <Y0bRsLWaSaUnPFqM@cormorant.local> (raw)
In-Reply-To: <CAJSP0QViGDCNrdPNPnT87go=ofCxTE7cWMGHFnOH5v+8rw8BGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On Okt 12 10:28, Stefan Hajnoczi wrote:
> On Fri, 26 Aug 2022 at 07:18, Jinhao Fan <fanjinhao21s@ict.ac.cn> wrote:
> >
> > This patch series adds support for using a seperate iothread for NVMe
> > IO emulation, which brings the potential of applying polling. The
> > first two patches implements support for irqfd, which solves thread
> > safety problems for interrupt emulation outside the main loop thread.
> >
> > Jinhao Fan (3):
> > hw/nvme: support irq(de)assertion with eventfd
> > hw/nvme: use KVM irqfd when available
> > hw/nvme: add iothread support
>
> Hi,
> What is the status of this series?
>
I have been meaning to pick it up, but I got side-tracked. The polling
performance drop needs to be address as we discussed offline.
But the v4 looks pretty good and I can pick that up without the polling
support for now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-12 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:18 [PATCH 0/3] iothread and irqfd support Jinhao Fan
2022-08-26 11:18 ` [PATCH 1/3] hw/nvme: support irq(de)assertion with eventfd Jinhao Fan
2022-08-26 11:18 ` [PATCH 2/3] hw/nvme: use KVM irqfd when available Jinhao Fan
2022-08-26 11:18 ` [PATCH 3/3] hw/nvme: add iothread support Jinhao Fan
2022-08-26 15:10 ` Jinhao Fan
2022-10-12 14:28 ` [PATCH 0/3] iothread and irqfd support Stefan Hajnoczi
2022-10-12 14:39 ` Klaus Jensen [this message]
2022-10-12 15:35 ` Jinhao Fan
2022-10-12 15:53 ` Stefan Hajnoczi
2022-10-14 4:49 ` Jinhao Fan
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=Y0bRsLWaSaUnPFqM@cormorant.local \
--to=its@irrelevant.dk \
--cc=fanjinhao21s@ict.ac.cn \
--cc=kbusch@kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).