From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/1] nvme-rdma: use dynamic dma mapping per command
Date: Thu, 6 Jun 2019 08:45:37 +0200 [thread overview]
Message-ID: <20190606064537.GE27033@lst.de> (raw)
In-Reply-To: <1559749293-32649-1-git-send-email-maxg@mellanox.com>
> Fixes: 87fd125344d6 ("nvme-rdma: remove redundant reference between ib_device and tagset")
> Suggested-by: Sagi Grimberg <sagi at grimberg.me>
> Tested-by: Jim Harris <james.r.harris at intel.com>
Shouldn't this also have a reported-by?
> -static void nvme_rdma_free_qe(struct ib_device *ibdev, struct nvme_rdma_qe *qe,
> - size_t capsule_size, enum dma_data_direction dir)
> +static void nvme_rdma_free_mapped_qe(struct ib_device *ibdev,
> + struct nvme_rdma_qe *qe, size_t capsule_size,
> + enum dma_data_direction dir)
> {
> ib_dma_unmap_single(ibdev, qe->dma, capsule_size, dir);
> kfree(qe->data);
> }
>
> -static int nvme_rdma_alloc_qe(struct ib_device *ibdev, struct nvme_rdma_qe *qe,
> - size_t capsule_size, enum dma_data_direction dir)
> +static int nvme_rdma_alloc_mapped_qe(struct ib_device *ibdev,
> + struct nvme_rdma_qe *qe, size_t capsule_size,
> + enum dma_data_direction dir)
I agree with Sagi that we probably should drop the renames.
Can you write out the explanation somewhere why the AEN SQE doesn't
need this treatment? Especially as that would actually allow moving
the DMA mapping into nvme_rdma_post_send and clean things up a bit.
next prev parent reply other threads:[~2019-06-06 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:41 [PATCH 1/1] nvme-rdma: use dynamic dma mapping per command Max Gurtovoy
2019-06-05 17:27 ` Sagi Grimberg
2019-06-05 22:08 ` Max Gurtovoy
2019-06-06 6:45 ` Christoph Hellwig [this message]
2019-06-06 7:38 ` Max Gurtovoy
2019-06-06 8:31 ` Christoph Hellwig
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=20190606064537.GE27033@lst.de \
--to=hch@lst.de \
/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.