From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
Chuck Lever <cel@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Chuck Lever <chuck.lever@oracle.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
Subject: Re: [PATCH RFC 0/9] Exploring biovec support in (R)DMA API
Date: Mon, 23 Oct 2023 07:59:51 +0200 [thread overview]
Message-ID: <20231023055951.GB11569@lst.de> (raw)
In-Reply-To: <41218260-1e5f-4d36-8287-fc6f50f3ec00@arm.com>
On Fri, Oct 20, 2023 at 11:30:06AM +0100, Robin Murphy wrote:
>> Well, we can stage this. I wish I could find my old proposal about the
>> dma_batch API (I remember Robin commented on it, my he is better at
>> finding it than me).
>
> Heh, the dirty secret is that Office 365 is surprisingly effective at
> searching 9 years worth of email I haven't deleted :)
>
> https://lore.kernel.org/linux-iommu/79926b59-0eb9-2b88-b1bb-1bd472b10370@arm.com/
Perfect, thanks!
> The other thing that's clear by now is that I think we definitely want
> distinct APIs for "please map this bunch of disjoint things" for true
> scatter-gather cases like biovecs where it's largely just convenient to
> keep them grouped together (but opportunistic merging might still be a
> bonus), vs. "please give me a linearised DMA mapping of these pages (and
> fail if you can't)" for the dma-buf style cases.
Hmm, I'm not sure I agree. For both the iommu and swiotlb case we
get the linear mapping for free with small limitations:
- for the iommu case the alignment needs to be a multiple of the iommu
page size
- for swiotlb the size of each mapping is very limited
If these conditions are matched we can linearize for free, if they aren't
we can't linearize at all.
But maybe I'm missing something?
next prev parent reply other threads:[~2023-10-23 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:25 Chuck Lever
2023-10-19 15:25 ` [PATCH RFC 4/9] mm: kmsan: Add support for DMA mapping bio_vec arrays 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 [this message]
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=20231023055951.GB11569@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=glider@google.com \
--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 \
--cc=willy@infradead.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: 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