The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mieczyslaw Nalewaj <namiltd@yahoo.com>,
	Felix Fietkau <nbd@nbd.name>, Hauke Mehrtens <hauke@hauke-m.de>,
	Aleksander Jan Bajkowski <olek2@wp.pl>,
	Christian Marangi <ansuelsmth@gmail.com>,
	Rosen Penev <rosenp@gmail.com>,
	Nick Hainke <vincent@systemli.org>,
	openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH] MIPS: ralink: reduce ARCH_DMA_MINALIGN
Date: Tue, 26 May 2026 16:42:49 +0200	[thread overview]
Message-ID: <ahWxaT2josfOnKNa@alpha.franken.de> (raw)
In-Reply-To: <20260428082543.95896-1-qingfang.deng@linux.dev>

On Tue, Apr 28, 2026 at 04:25:40PM +0800, Qingfang Deng wrote:
> Currently, Ralink 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 16 bytes for
> RT288X and 32 bytes for other Ralink SoCs.
> 
> Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>
> ---
>  arch/mips/include/asm/mach-ralink/kmalloc.h | 9 +++++++++
>  1 file changed, 9 insertions(+)
>  create mode 100644 arch/mips/include/asm/mach-ralink/kmalloc.h

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 ]

      reply	other threads:[~2026-05-26 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  8:25 [PATCH] MIPS: ralink: reduce ARCH_DMA_MINALIGN Qingfang Deng
2026-05-26 14:42 ` 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=ahWxaT2josfOnKNa@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=ansuelsmth@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=namiltd@yahoo.com \
    --cc=nbd@nbd.name \
    --cc=olek2@wp.pl \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=qingfang.deng@linux.dev \
    --cc=rosenp@gmail.com \
    --cc=vincent@systemli.org \
    /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