linux-kernel - Re: [TECH TOPIC] Reaching consensus on CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <640041197.22387.1757536385810.JavaMail.zimbra@nod.at>
Date: Wed, 10 Sep 2025 22:33:05 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Dave Hansen <dave@...1.net>
Cc: Arnd Bergmann <arnd@...db.de>, ksummit <ksummit@...ts.linux.dev>, 
	linux-kernel <linux-kernel@...r.kernel.org>, 
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, 
	linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, 
	linux-mips <linux-mips@...r.kernel.org>, 
	linux-mm <linux-mm@...ck.org>, imx <imx@...ts.linux.dev>, 
	Christophe Leroy <christophe.leroy@...roup.eu>, 
	Lucas Stach <l.stach@...gutronix.de>, 
	Linus Walleij <linus.walleij@...aro.org>, 
	Geert Uytterhoeven <geert+renesas@...der.be>, 
	Ankur Arora <ankur.a.arora@...cle.com>, 
	David Hildenbrand <david@...hat.com>, 
	Mike Rapoport <rppt@...nel.org>, 
	Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, 
	Matthew Wilcox <willy@...radead.org>, 
	Andrew Morton <akpm@...ux-foundation.org>, 
	"Liam R. Howlett" <Liam.Howlett@...cle.com>, vbabka <vbabka@...e.cz>, 
	Suren Baghdasaryan <surenb@...gle.com>, 
	Ira Weiny <ira.weiny@...el.com>, Nishanth Menon <nm@...com>, 
	heiko <heiko@...ech.de>, 
	Alexander Sverdlin <alexander.sverdlin@...il.com>, 
	"Chester A. Unal" <chester.a.unal@...nc9.com>, 
	Sergio Paracuellos <sergio.paracuellos@...il.com>, 
	Andreas Larsson <andreas@...sler.com>
Subject: Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout

Dave,

----- Ursprüngliche Mail -----
> Von: "Dave Hansen" <dave@...1.net>
>> Even with a new memory split, which could utilize most of the
>> available memory, I expect there to be issues with various
>> applications and FPGA device drivers.
> I'd be really curious what the _actual_ issues would be with a
> non-standard split. There are a lot of "maybe" problems and solutions
> here, but it's hard to move forward without known practical problems to
> tackle.
> 
> Has anybody run into actual end user visible problems when using one of
> weirdo PAGE_OFFSET configs?

In the past I saw that programs such as the Java Runtime (JRE) ran into
address space limitations due to a 2G/2G split on embedded systems.
Reverting to a 3G/1G split fixed the problems.

Thanks,
//richard