[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <76a8c896-d7ea-4471-99a2-34b3a7ac9804@app.fastmail.com>
Date: Tue, 17 Jun 2025 10:26:51 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Christoph Hellwig" <hch@....de>
Cc: "James Clark" <james.clark@...aro.org>, "Mark Brown" <broonie@...nel.org>,
"Vladimir Oltean" <olteanv@...il.com>, oe-kbuild-all@...ts.linux.dev,
"Larisa Grigore" <larisa.grigore@....com>, "Frank Li" <Frank.li@....com>,
linux-spi@...r.kernel.org, imx@...ts.linux.dev, linux-kernel@...r.kernel.org,
"kernel test robot" <lkp@...el.com>,
"Marek Szyprowski" <m.szyprowski@...sung.com>,
"Robin Murphy" <robin.murphy@....com>, iommu@...ts.linux.dev
Subject: Re: [PATCH] dma-mapping: Stub out dma_{alloc,free,map}_pages() API
On Tue, Jun 17, 2025, at 09:53, Arnd Bergmann wrote:
> Between SH72xx/SH76xx, SUN3 and M68328, I believe the
> supported machines are all limited to between 1MB and 32MB in
> the maximum configuration, which is obviously extremely
> tight.
I checked the exact numbers we're talking about here: enabling
CONFIG_HAS_DMA on rsk7269_defconfig adds 10KB of extra vmlinux
size, which doesn't seem too bad:
text data bss dec hex filename
3295084 1111396 112264 4518744 44f358 vmlinux-before
3302836 1113652 112264 4528752 451a70 vmlinux-after
Arnd
Powered by blists - more mailing lists