All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinhao Fan <fanjinhao21s@ict.ac.cn>
To: Klaus Jensen <its@irrelevant.dk>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, kbusch@kernel.org
Subject: Re: [PATCH 0/3] iothread and irqfd support
Date: Wed, 12 Oct 2022 23:35:05 +0800	[thread overview]
Message-ID: <ce082eb5-e362-87f7-c4fc-bc786515017c@ict.ac.cn> (raw)
In-Reply-To: <Y0bRsLWaSaUnPFqM@cormorant.local>

On 10/12/2022 10:39 PM, Klaus Jensen wrote:
> 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.

I've been using the v4 without polling for my daily work. It worked 
pretty well for my test workloads.

I'm not sure what needs to be done for the polling problem. I can try to 
add a completion batching mechanism with BH, similar to virtio-blk. Do 
you think this is the right direction?



  reply	other threads:[~2022-10-12 15:37 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
2022-10-12 15:35     ` Jinhao Fan [this message]
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=ce082eb5-e362-87f7-c4fc-bc786515017c@ict.ac.cn \
    --to=fanjinhao21s@ict.ac.cn \
    --cc=its@irrelevant.dk \
    --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 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.