On Tue, Apr 05, 2022 at 02:57:55PM +0100, Catalin Marinas wrote: > ARCH_DMA_MINALIGN represents the minimum (static) alignment for safe DMA > operations while ARCH_KMALLOC_MINALIGN is the minimum kmalloc() objects > alignment. > > Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx> > Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > Cc: "David S. Miller" <davem@xxxxxxxxxxxxx> > --- > include/linux/crypto.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/linux/crypto.h b/include/linux/crypto.h > index 2324ab6f1846..654b9c355575 100644 > --- a/include/linux/crypto.h > +++ b/include/linux/crypto.h > @@ -167,7 +167,7 @@ > * maintenance for non-coherent DMA (cache invalidation in particular) does not > * affect data that may be accessed by the CPU concurrently. > */ > -#define CRYPTO_MINALIGN ARCH_KMALLOC_MINALIGN > +#define CRYPTO_MINALIGN ARCH_DMA_MINALIGN I think this should remain as ARCH_KMALLOC_MINALIGN with the comment above modified. The reason is that we assume memory returned by kmalloc is already aligned to this value. Ard, you added the comment regarding the DMA requirement, so does anything actually rely on this? If they do, they now need to do their own alignment. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
