On Wed, Aug 19, 2020 at 05:03:52PM +0200, Tomasz Figa wrote: > > > > -Warning: These pieces of the DMA API should not be used in the > > -majority of cases, since they cater for unlikely corner cases that > > -don't belong in usual drivers. > > +These APIs allow to allocate pages that can be used like normal pages > > +in the kernel direct mapping, but are guaranteed to be DMA addressable. > > Could we elaborate a bit more on what "like normal pages in kernel > direct mapping" mean from the driver perspective? It mostly means you can call virt_to_page and then do anything you'd do with a page struct. Unlike dma_alloc_attrs that just return an opaque virtual address that the caller is not allowed to poke into. > There is one aspect that the existing dma_alloc_attrs() handles, but > this new function doesn't: IOMMU support. The function will always > allocate a physically-contiguous block memory, which is a costly > operation and not even guaranteed to succeed, even if enough free > memory is available. > > Modern SoCs employ IOMMUs to avoid the need to allocate > physically-contiguous memory and those happen to be also the devices > that could benefit from non-coherent allocations a lot. One of the > tasks of the DMA API was making it possible to allocate suitable > memory for a given device, without having the driver know about the > SoC integration details, such as the presence of an IOMMU. This is completely out of scope for this API exactly because it guarantees a page in the direct mapping. But see my previous mail in reply to Robin on how you can implement the funtionality you want right now without any help from the dma-mapping subsystem.
