From: Chuck Lever <cel@kernel.org> To: unlisted-recipients:; (no To-header on input) Cc: Marek Szyprowski <m.szyprowski@samsung.com>, Chuck Lever <chuck.lever@oracle.com>, Robin Murphy <robin.murphy@arm.com>, Alexander Potapenko <glider@google.com>, linux-mm@kvack.org, linux-rdma@vger.kernel.org, Jens Axboe <axboe@kernel.dk>, kasan-dev@googlegroups.com, David Howells <dhowells@redhat.com>, iommu@lists.linux.dev, Christoph Hellwig <hch@lst.de> Subject: [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Date: Thu, 19 Oct 2023 11:25:31 -0400 [thread overview] Message-ID: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> (raw) The SunRPC stack manages pages (and eventually, folios) via an array of struct biovec items within struct xdr_buf. We have not fully committed to replacing the struct page array in xdr_buf because, although the socket API supports biovec arrays, the RDMA stack uses struct scatterlist rather than struct biovec. This (incomplete) series explores what it might look like if the RDMA core API could support struct biovec array arguments. The series compiles on x86, but I haven't tested it further. I'm posting early in hopes of starting further discussion. Are there other upper layer API consumers, besides SunRPC, who might prefer the use of biovec over scatterlist? Besides handling folios as well as single pages in bv_page, what other work might be needed in the DMA layer? What RDMA core APIs should be converted? IMO a DMA mapping and registration API for biovecs would be needed. Maybe RDMA Read and Write too? --- Chuck Lever (9): dma-debug: Fix a typo in a debugging eye-catcher bvec: Add bio_vec fields to manage DMA mapping dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays mm: kmsan: Add support for DMA mapping bio_vec arrays dma-direct: Support direct mapping bio_vec arrays DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() DMA: Add dma_map_bvecs_attrs() iommu/dma: Support DMA-mapping a bio_vec array RDMA: Add helpers for DMA-mapping an array of bio_vecs drivers/iommu/dma-iommu.c | 368 ++++++++++++++++++++++++++++++++++++ drivers/iommu/iommu.c | 58 ++++++ include/linux/bvec.h | 143 ++++++++++++++ include/linux/dma-map-ops.h | 8 + include/linux/dma-mapping.h | 9 + include/linux/iommu.h | 4 + include/linux/kmsan.h | 20 ++ include/rdma/ib_verbs.h | 29 +++ kernel/dma/debug.c | 165 +++++++++++++++- kernel/dma/debug.h | 38 ++++ kernel/dma/direct.c | 92 +++++++++ kernel/dma/direct.h | 17 ++ kernel/dma/mapping.c | 93 +++++++++ mm/kmsan/hooks.c | 13 ++ 14 files changed, 1056 insertions(+), 1 deletion(-) -- Chuck Lever
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Lever <cel@kernel.org> Cc: Marek Szyprowski <m.szyprowski@samsung.com>, Chuck Lever <chuck.lever@oracle.com>, Robin Murphy <robin.murphy@arm.com>, Alexander Potapenko <glider@google.com>, linux-mm@kvack.org, linux-rdma@vger.kernel.org, Jens Axboe <axboe@kernel.dk>, kasan-dev@googlegroups.com, David Howells <dhowells@redhat.com>, iommu@lists.linux.dev, Christoph Hellwig <hch@lst.de> Subject: [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Date: Thu, 19 Oct 2023 11:25:31 -0400 [thread overview] Message-ID: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> (raw) The SunRPC stack manages pages (and eventually, folios) via an array of struct biovec items within struct xdr_buf. We have not fully committed to replacing the struct page array in xdr_buf because, although the socket API supports biovec arrays, the RDMA stack uses struct scatterlist rather than struct biovec. This (incomplete) series explores what it might look like if the RDMA core API could support struct biovec array arguments. The series compiles on x86, but I haven't tested it further. I'm posting early in hopes of starting further discussion. Are there other upper layer API consumers, besides SunRPC, who might prefer the use of biovec over scatterlist? Besides handling folios as well as single pages in bv_page, what other work might be needed in the DMA layer? What RDMA core APIs should be converted? IMO a DMA mapping and registration API for biovecs would be needed. Maybe RDMA Read and Write too? --- Chuck Lever (9): dma-debug: Fix a typo in a debugging eye-catcher bvec: Add bio_vec fields to manage DMA mapping dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays mm: kmsan: Add support for DMA mapping bio_vec arrays dma-direct: Support direct mapping bio_vec arrays DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() DMA: Add dma_map_bvecs_attrs() iommu/dma: Support DMA-mapping a bio_vec array RDMA: Add helpers for DMA-mapping an array of bio_vecs drivers/iommu/dma-iommu.c | 368 ++++++++++++++++++++++++++++++++++++ drivers/iommu/iommu.c | 58 ++++++ include/linux/bvec.h | 143 ++++++++++++++ include/linux/dma-map-ops.h | 8 + include/linux/dma-mapping.h | 9 + include/linux/iommu.h | 4 + include/linux/kmsan.h | 20 ++ include/rdma/ib_verbs.h | 29 +++ kernel/dma/debug.c | 165 +++++++++++++++- kernel/dma/debug.h | 38 ++++ kernel/dma/direct.c | 92 +++++++++ kernel/dma/direct.h | 17 ++ kernel/dma/mapping.c | 93 +++++++++ mm/kmsan/hooks.c | 13 ++ 14 files changed, 1056 insertions(+), 1 deletion(-) -- Chuck Lever
next reply other threads:[~2023-10-19 15:25 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 15:25 Chuck Lever [this message] 2023-10-19 15:25 ` [PATCH RFC 0/9] Exploring biovec support in (R)DMA API 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 ` [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Chuck Lever 2023-10-19 15:26 ` 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=169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net \ --to=cel@kernel.org \ --cc=axboe@kernel.dk \ --cc=chuck.lever@oracle.com \ --cc=dhowells@redhat.com \ --cc=glider@google.com \ --cc=hch@lst.de \ --cc=iommu@lists.linux.dev \ --cc=kasan-dev@googlegroups.com \ --cc=linux-mm@kvack.org \ --cc=linux-rdma@vger.kernel.org \ --cc=m.szyprowski@samsung.com \ --cc=robin.murphy@arm.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: 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.