[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1335982c-70ea-6af2-19cf-73a4332ae510@wanadoo.fr>
Date: Tue, 30 May 2023 20:46:21 +0200
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Bernd Petrovitsch <bernd@...rovitsch.priv.at>,
Fenghua Yu <fenghua.yu@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Vinod Koul <vkoul@...nel.org>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
dmaengine@...r.kernel.org
Subject: Re: [PATCH] dmaengine: idxd: No need to clear memory after a
dma_alloc_coherent() call
Le 30/05/2023 à 17:54, Bernd Petrovitsch a écrit :
> On 28/05/2023 16:11, Christophe JAILLET wrote:
>> dma_alloc_coherent() already clear the allocated memory, there is no need
>> to explicitly call memset().
>
> Hmm, so wouldn't be dma_zalloc_coherent() a better name for the function?
>
> Kind regards,
> Bernd
Hi,
No strong opinion about it.
It is not malloc either !)
When dma_zalloc_coherent() has been deprecated (see [1]), for some
reason, it was decided to keep the "alloc" version.
CJ
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/linux/dma-mapping.h?id=06d4dd2f2ce1cdb625f77c0676d5af6ba310c01d
Powered by blists - more mailing lists