[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Ve85_gDMUN91ZOhRLO3TkxmdO1crAcYjb1TGDCBmWbmFQ@mail.gmail.com>
Date: Mon, 11 Apr 2022 17:57:08 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Will Deacon <will@...nel.org>, Marc Zyngier <maz@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH 02/10] drivers/base: Use ARCH_DMA_MINALIGN instead of ARCH_KMALLOC_MINALIGN
On Wed, Apr 6, 2022 at 2:30 PM Catalin Marinas <catalin.marinas@....com> wrote:
>
> ARCH_DMA_MINALIGN represents the minimum (static) alignment for safe DMA
> operations while ARCH_KMALLOC_MINALIGN is the minimum kmalloc() objects
> alignment.
...
> - * Thus we use ARCH_KMALLOC_MINALIGN here and get exactly the same
> + * Thus we use ARCH_DMA_MINALIGN here and get at least the same
> * buffer alignment as if it was allocated by plain kmalloc().
But then it becomes not true either, because the kmalloc() has other
alignment constraints.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists