From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Karl Rister <krister@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/6] block: Add VFIO based NVMe driver
Date: Thu, 23 Feb 2017 18:01:28 +0800 [thread overview]
Message-ID: <20170223100128.GA14175@lemon.lan> (raw)
In-Reply-To: <21422231-2868-49fa-2b3b-363054b09797@redhat.com>
On Thu, 02/23 10:43, Paolo Bonzini wrote:
>
>
> On 23/02/2017 10:18, Fam Zheng wrote:
> > + for (i = 0; i < s->nr_queues; ++i) {
> > + s->queues[i]->free_req_queue_bh =
> > + aio_bh_new(new_context, nvme_free_req_queue_cb, s->queues[i]);
> > + }
>
> aio_bh_new has the issue that you can complete two requests in one
> nvme_process_completion call, but you would only invoke the bottom half
> once. Because this is a rare event, I think it's enough to use
> aio_bh_schedule_oneshot instead of aio_bh_new.
Yes, that should work.
>
> > +static coroutine_fn int nvme_cmd_unmap_qiov(BlockDriverState *bs,
> > + QEMUIOVector *qiov)
> > +{
> > + int r = 0;
> > + BDRVNVMeState *s = bs->opaque;
> > +
> > + if (!s->inflight && !qemu_co_queue_empty(&s->dma_flush_queue)) {
> > + r = nvme_vfio_dma_reset_temporary(s->vfio);
> > + qemu_co_queue_next(&s->dma_flush_queue);
> > + }
> > + return r;
> > +}
>
> Should this be qemu_co_queue_restart_all instead?
You are right, will fix!
Fam
next prev parent reply other threads:[~2017-02-23 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 9:18 [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 1/6] nvme: Move NVMe definitions to a separate header Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 2/6] stubs: Add stubs for ram block notifier API Fam Zheng
2017-02-23 9:49 ` Paolo Bonzini
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 3/6] block: Add VFIO based NVMe driver Fam Zheng
2017-02-23 9:43 ` Paolo Bonzini
2017-02-23 10:01 ` Fam Zheng [this message]
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 4/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 5/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 6/6] qemu-img: dma map buffers Fam Zheng
2017-02-23 9:28 ` [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device no-reply
2017-02-23 10:48 ` Fam Zheng
2017-02-23 10:50 ` Paolo Bonzini
2017-02-23 11:19 ` Fam Zheng
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=20170223100128.GA14175@lemon.lan \
--to=famz@redhat.com \
--cc=krister@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).