Re: [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper
Randy Dunlap <[email protected]>
| Newsgroups | org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 8/22/26 5:16 AM, Karl Mehltretter wrote:
> The DMA helper is named dma_max_mapping_size(), not
> dma_map_mapping_size().
>
> Fixes: c93f261dfc39 ("Documentation/core-api: add swiotlb documentation")
> Assisted-by: Codex:gpt-5.6-sol
> Signed-off-by: Karl Mehltretter <[email protected]>
Reviewed-by: Randy Dunlap <[email protected]>
Thanks.
> ---
> Documentation/core-api/swiotlb.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/swiotlb.rst b/Documentation/core-api/swiotlb.rst
> index 9e0fe027dd3bd..303999f09ea03 100644
> --- a/Documentation/core-api/swiotlb.rst
> +++ b/Documentation/core-api/swiotlb.rst
> @@ -107,7 +107,7 @@ A single allocation from swiotlb is limited to IO_TLB_SIZE * IO_TLB_SEGSIZE
> bytes, which is 256 KiB with current definitions. When a device's DMA settings
> are such that the device might use swiotlb, the maximum size of a DMA segment
> must be limited to that 256 KiB. This value is communicated to higher-level
> -kernel code via dma_map_mapping_size() and swiotlb_max_mapping_size(). If the
> +kernel code via dma_max_mapping_size() and swiotlb_max_mapping_size(). If the
> higher-level code fails to account for this limit, it may make requests that
> are too large for swiotlb, and get a "swiotlb full" error.
>
--
~Randy