From: Chuck Lever <cel@kernel.org> To: unlisted-recipients:; (no To-header on input) Cc: iommu@lists.linux.dev, linux-rdma@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com> Subject: [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Date: Thu, 19 Oct 2023 11:26:31 -0400 [thread overview] Message-ID: <169772919129.5232.11342896871510148807.stgit@klimt.1015granger.net> (raw) In-Reply-To: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> From: Chuck Lever <chuck.lever@oracle.com> Cc: iommu@lists.linux.dev Cc: linux-rdma@vger.kernel.org Signed-off-by: Chuck Lever <chuck.lever@oracle.com> --- include/rdma/ib_verbs.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h index 533ab92684d8..5e205fda90f9 100644 --- a/include/rdma/ib_verbs.h +++ b/include/rdma/ib_verbs.h @@ -4220,6 +4220,35 @@ static inline void ib_dma_unmap_sg(struct ib_device *dev, ib_dma_unmap_sg_attrs(dev, sg, nents, direction, 0); } +/** + * ib_dma_map_sg - Map an array of bio_vecs to DMA addresses + * @dev: The device for which the DMA addresses are to be created + * @bvecs: The array of bio_vec entries to map + * @nents: The number of entries in the array + * @direction: The direction of the DMA + */ +static inline int ib_dma_map_bvecs(struct ib_device *dev, + struct bio_vec *bvecs, int nents, + enum dma_data_direction direction) +{ + return dma_map_bvecs_attrs(dev->dma_device, bvecs, nents, direction, 0); +} + +/** + * ib_dma_unmap_bvecs - Unmap a DMA-mapped bio_vec array + * @dev: The device for which the DMA addresses were created + * @bvecs: The array of bio_vec entries to unmap + * @nents: The number of entries in the array + * @direction: The direction of the DMA + */ +static inline void ib_dma_unmap_bvec(struct ib_device *dev, + struct bio_vec *bvecs, int nents, + enum dma_data_direction direction) +{ + if (!ib_uses_virt_dma(dev)) + dma_unmap_bvecs_attrs(dev->dma_device, bvecs, nents, direction); +} + /** * ib_dma_max_seg_size - Return the size limit of a single DMA transfer * @dev: The device to query
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Lever <cel@kernel.org> Cc: iommu@lists.linux.dev, linux-rdma@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com> Subject: [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Date: Thu, 19 Oct 2023 11:26:31 -0400 [thread overview] Message-ID: <169772919129.5232.11342896871510148807.stgit@klimt.1015granger.net> (raw) In-Reply-To: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> From: Chuck Lever <chuck.lever@oracle.com> Cc: iommu@lists.linux.dev Cc: linux-rdma@vger.kernel.org Signed-off-by: Chuck Lever <chuck.lever@oracle.com> --- include/rdma/ib_verbs.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h index 533ab92684d8..5e205fda90f9 100644 --- a/include/rdma/ib_verbs.h +++ b/include/rdma/ib_verbs.h @@ -4220,6 +4220,35 @@ static inline void ib_dma_unmap_sg(struct ib_device *dev, ib_dma_unmap_sg_attrs(dev, sg, nents, direction, 0); } +/** + * ib_dma_map_sg - Map an array of bio_vecs to DMA addresses + * @dev: The device for which the DMA addresses are to be created + * @bvecs: The array of bio_vec entries to map + * @nents: The number of entries in the array + * @direction: The direction of the DMA + */ +static inline int ib_dma_map_bvecs(struct ib_device *dev, + struct bio_vec *bvecs, int nents, + enum dma_data_direction direction) +{ + return dma_map_bvecs_attrs(dev->dma_device, bvecs, nents, direction, 0); +} + +/** + * ib_dma_unmap_bvecs - Unmap a DMA-mapped bio_vec array + * @dev: The device for which the DMA addresses were created + * @bvecs: The array of bio_vec entries to unmap + * @nents: The number of entries in the array + * @direction: The direction of the DMA + */ +static inline void ib_dma_unmap_bvec(struct ib_device *dev, + struct bio_vec *bvecs, int nents, + enum dma_data_direction direction) +{ + if (!ib_uses_virt_dma(dev)) + dma_unmap_bvecs_attrs(dev->dma_device, bvecs, nents, direction); +} + /** * ib_dma_max_seg_size - Return the size limit of a single DMA transfer * @dev: The device to query
next prev parent reply other threads:[~2023-10-19 15:26 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 15:25 [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 15:25 ` [PATCH RFC 1/9] dma-debug: Fix a typo in a debugging eye-catcher Chuck Lever 2023-10-20 4:49 ` Christoph Hellwig 2023-10-20 13:38 ` Chuck Lever III 2023-10-23 5:56 ` Christoph Hellwig 2023-10-19 15:25 ` [PATCH RFC 2/9] bvec: Add bio_vec fields to manage DMA mapping Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 15:25 ` [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 21:38 ` kernel test robot 2023-10-19 23:21 ` Chuck Lever III 2023-10-23 2:43 ` Liu, Yujie 2023-10-23 14:27 ` Chuck Lever III 2023-10-19 21:49 ` kernel test robot 2023-10-19 15:25 ` [PATCH RFC 4/9] mm: kmsan: Add support for DMA " Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 5/9] dma-direct: Support direct " Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 6/9] DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs() Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 22:10 ` kernel test robot 2023-10-19 15:26 ` [PATCH RFC 8/9] iommu/dma: Support DMA-mapping a bio_vec array Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` Chuck Lever [this message] 2023-10-19 15:26 ` [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Chuck Lever 2023-10-19 15:53 ` [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Matthew Wilcox 2023-10-19 17:48 ` Chuck Lever 2023-10-20 4:58 ` Christoph Hellwig 2023-10-20 10:30 ` Robin Murphy 2023-10-23 5:59 ` Christoph Hellwig 2023-10-19 16:43 ` Robin Murphy 2023-10-19 17:53 ` Jason Gunthorpe
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=169772919129.5232.11342896871510148807.stgit@klimt.1015granger.net \ --to=cel@kernel.org \ --cc=chuck.lever@oracle.com \ --cc=iommu@lists.linux.dev \ --cc=linux-rdma@vger.kernel.org \ /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: linkBe 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.