From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-mips@vger.kernel.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: ath79: reduce ARCH_DMA_MINALIGN
Date: Mon, 15 Jun 2026 12:28:50 +0200 [thread overview]
Message-ID: <ai_T4m2Bsd6lOC6s@alpha.franken.de> (raw)
In-Reply-To: <20260527222504.17381-1-rosenp@gmail.com>
On Wed, May 27, 2026 at 03:25:04PM -0700, Rosen Penev wrote:
> Currently, ath79 SoCs use the default ARCH_DMA_MINALIGN value of 128
> bytes defined in mach-generic. This is excessive for these platforms
> and leads to significant memory waste in kmalloc.
>
> Override ARCH_DMA_MINALIGN to use L1_CACHE_BYTES, which is 32 bytes for
> ath79 SoCs.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> arch/mips/include/asm/mach-ath79/kmalloc.h | 7 +++++++
> 1 file changed, 7 insertions(+)
> create mode 100644 arch/mips/include/asm/mach-ath79/kmalloc.h
>
> diff --git a/arch/mips/include/asm/mach-ath79/kmalloc.h b/arch/mips/include/asm/mach-ath79/kmalloc.h
> new file mode 100644
> index 000000000000..954f5d6e0dd0
> --- /dev/null
> +++ b/arch/mips/include/asm/mach-ath79/kmalloc.h
> @@ -0,0 +1,7 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef __ASM_MACH_ATH79_KMALLOC_H
> +#define __ASM_MACH_ATH79_KMALLOC_H
> +
> +#define ARCH_DMA_MINALIGN L1_CACHE_BYTES
> +
> +#endif /* __ASM_MACH_ATH79_KMALLOC_H */
> --
> 2.54.0
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-06-15 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 22:25 [PATCH] MIPS: ath79: reduce ARCH_DMA_MINALIGN Rosen Penev
2026-06-15 10:28 ` Thomas Bogendoerfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ai_T4m2Bsd6lOC6s@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rosenp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox