[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3acea31c-054c-43a8-a6f7-ab4b5b6a7dca@samsung.com>
Date: Thu, 26 Jun 2025 09:21:00 +0200
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: Petr Tesarik <ptesarik@...e.com>, Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>
Cc: Jonathan Corbet <corbet@....net>, Andrew Morton
<akpm@...ux-foundation.org>, Leon Romanovsky <leon@...nel.org>, Keith Busch
<kbusch@...nel.org>, Caleb Sander Mateos <csander@...estorage.com>, Sagi
Grimberg <sagi@...mberg.me>, Jens Axboe <axboe@...nel.dk>, John Garry
<john.g.garry@...cle.com>, "open list:DOCUMENTATION"
<linux-doc@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>, "open
list:MEMORY MANAGEMENT" <linux-mm@...ck.org>, iommu@...ts.linux.dev
Subject: Re: [PATCH 2/8] docs: dma-api: replace consistent with coherent
On 26.06.2025 06:51, Petr Tesarik wrote:
> On Tue, 24 Jun 2025 15:39:17 +0200
> Petr Tesarik <ptesarik@...e.com> wrote:
>
>> For consistency, always use the term "coherent" when talking about memory
>> that is not subject to CPU caching effects. The term "consistent" is a
>> relic of a long-removed pci_alloc_consistent() function.
> I realize that I'm not an authoritative source for this, but I forgot
> to add more trusted maintainers to the recipient list.
>
> Now, all you DMA experts, do you agree that the word "consistent"
> should be finally eradicated from DMA API documentation?
Well, this was always puzzling for me, why there are those 2 names used
(especially in case of dma_alloc_coherent() vs.
dma_alloc_nonconsistent()). I'm for unifying them to "coherent" as this
is the term use more often.
> > ...
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Powered by blists - more mailing lists