From: Klaus Jensen <its@irrelevant.dk>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH RFC 1/4] hw/block/nvme: convert dsm to aiocb
Date: Mon, 8 Mar 2021 19:05:40 +0100 [thread overview]
Message-ID: <YEZndKMdZcMvDKck@apples.localdomain> (raw)
In-Reply-To: <YEZSr7Y/Y4+NJY5V@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2737 bytes --]
On Mar 8 16:37, Stefan Hajnoczi wrote:
> On Tue, Mar 02, 2021 at 12:10:37PM +0100, Klaus Jensen wrote:
> > +static void nvme_dsm_cancel(BlockAIOCB *aiocb)
> > +{
> > + NvmeDSMAIOCB *iocb = container_of(aiocb, NvmeDSMAIOCB, common);
> > +
> > + /* break loop */
> > + iocb->curr.len = 0;
> > + iocb->curr.idx = iocb->nr;
> > +
> > + iocb->ret = -ECANCELED;
> > +
> > + if (iocb->aiocb) {
> > + blk_aio_cancel_async(iocb->aiocb);
> > + iocb->aiocb = NULL;
> > + }
> > +}
>
> Is the case where iocb->aiocb == NULL just in case nvme_dsm_cancel() is
> called after the last discard has completed but before the BH runs? I
> want to make sure there are no other cases because nothing would call
> iocb->common.cb().
>
Yes - that case *can* happen, right?
I modeled this after the appoach in the ide trim code (hw/ide/core.c).
> > static uint16_t nvme_dsm(NvmeCtrl *n, NvmeRequest *req)
> > {
> > NvmeNamespace *ns = req->ns;
> > NvmeDsmCmd *dsm = (NvmeDsmCmd *) &req->cmd;
> > -
> > uint32_t attr = le32_to_cpu(dsm->attributes);
> > uint32_t nr = (le32_to_cpu(dsm->nr) & 0xff) + 1;
> > -
> > uint16_t status = NVME_SUCCESS;
> >
> > trace_pci_nvme_dsm(nvme_cid(req), nvme_nsid(ns), nr, attr);
> >
> > if (attr & NVME_DSMGMT_AD) {
> > - int64_t offset;
> > - size_t len;
> > - NvmeDsmRange range[nr];
> > - uintptr_t *discards = (uintptr_t *)&req->opaque;
> > + NvmeDSMAIOCB *iocb = blk_aio_get(&nvme_dsm_aiocb_info, ns->blkconf.blk,
> > + nvme_misc_cb, req);
> >
> > - status = nvme_dma(n, (uint8_t *)range, sizeof(range),
> > + iocb->req = req;
> > + iocb->bh = qemu_bh_new(nvme_dsm_bh, iocb);
> > + iocb->ret = 0;
> > + iocb->range = g_new(NvmeDsmRange, nr);
> > + iocb->nr = nr;
> > + iocb->curr.len = 0;
> > + iocb->curr.idx = 0;
> > +
> > + status = nvme_dma(n, (uint8_t *)iocb->range, sizeof(NvmeDsmRange) * nr,
> > DMA_DIRECTION_TO_DEVICE, req);
> > if (status) {
> > return status;
> > }
> >
> > - /*
> > - * AIO callbacks may be called immediately, so initialize discards to 1
> > - * to make sure the the callback does not complete the request before
> > - * all discards have been issued.
> > - */
> > - *discards = 1;
> > + nvme_dsm_aio_cb(iocb, 0);
> > + req->aiocb = &iocb->common;
>
> Want to move this line up one just in case something in
> nvme_dsm_aio_cb() accesses req->aiocb?
Sounds reasonable! Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-08 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 11:10 [PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs Klaus Jensen
2021-03-02 11:10 ` [PATCH RFC 1/4] hw/block/nvme: convert dsm to aiocb Klaus Jensen
2021-03-08 16:37 ` Stefan Hajnoczi
2021-03-08 18:05 ` Klaus Jensen [this message]
2021-03-09 16:03 ` Stefan Hajnoczi
2021-03-09 18:27 ` Klaus Jensen
2021-03-02 11:10 ` [PATCH RFC 2/4] hw/block/nvme: convert copy " Klaus Jensen
2021-03-02 11:10 ` [PATCH RFC 3/4] hw/block/nvme: convert flush " Klaus Jensen
2021-03-02 11:10 ` [PATCH RFC 4/4] hw/block/nvme: convert zone reset " Klaus Jensen
2021-03-08 16:38 ` [PATCH RFC 0/4] hw/block/nvme: convert ad-hoc aio tracking to aiocbs Stefan Hajnoczi
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=YEZndKMdZcMvDKck@apples.localdomain \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@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).