ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Richard Weinberger <richard@nod.at>, Arnd Bergmann <arnd@arndb.de>
Cc: ksummit <ksummit@lists.linux.dev>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linuxppc-dev@lists.ozlabs.org,
	linux-mips <linux-mips@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	imx@lists.linux.dev, Lucas Stach <l.stach@pengutronix.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Ankur Arora <ankur.a.arora@oracle.com>,
	David Hildenbrand <david@redhat.com>,
	Mike Rapoport <rppt@kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	vbabka <vbabka@suse.cz>, Suren Baghdasaryan <surenb@google.com>,
	Ira Weiny <ira.weiny@intel.com>, Nishanth Menon <nm@ti.com>,
	heiko <heiko@sntech.de>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	"Chester A. Unal" <chester.a.unal@arinc9.com>,
	Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	Andreas Larsson <andreas@gaisler.com>
Subject: Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout
Date: Wed, 10 Sep 2025 19:11:26 +0200	[thread overview]
Message-ID: <d9caedb4-41c8-4ef7-99b9-51d891aee555@csgroup.eu> (raw)
In-Reply-To: <497308537.21756.1757513073548.JavaMail.zimbra@nod.at>

Hi Richard,

Le 10/09/2025 à 16:04, Richard Weinberger a écrit :
> Arnd,
> 
> ----- Ursprüngliche Mail -----
>> Von: "Arnd Bergmann" <arnd@arndb.de>
>> High memory is one of the least popular features of the Linux kernel.
>> Added in 1999 for linux-2.3.16 to support large x86 machines, there
>> are very few systems that still need it. I talked about about this
>> recently at the Embedded Linux Conference on 32-bit systems [1][2][3]
>> and there were a few older discussions before[4][5][6].
>>
>> While removing a feature that is actively used is clearly a regression
>> and not normally done, I expect removing highmem is going to happen
>> at some point anyway when there are few enough users, but the question
>> is when that time will be.
>>
>> I'm still collecting information about which of the remaining highmem
>> users plan to keep updating their kernels and for what reason. Some
>> users obviously are alarmed about potentially losing this ability,
>> so I hope to get a broad consensus on a specific timeline for how long
>> we plan to support highmem in the page cache and to give every user
>> sufficient time to migrate to a well-tested alternative setup if that
>> is possible, or stay on a highmem-enabled LTS kernel for as long
>> as necessary.
> 
> I am part of a team responsible for products based on various 32-bit SoCs,
> so I'm alarmed.
> These products, which include ARMv7 and PPC32 architectures with up to 2 GiB of RAM,
> are communication systems with five-figure deployments worldwide.
> 
> Removing high memory will have an impact on these systems.
> The oldest kernel version they run is 4.19 LTS, with upgrades to a more recent
> LTS release currently in progress.
> We typically upgrade the kernel every few years and will continue to support
> these systems for at least the next 10 years.
> 
> 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.

Can you tell which PPC32 model/family you are using ? Is it mpc85xx or 
and/or other variants ? Maybe we can look at keeping CONFIG_HIGHMEM or 
find alternatives for that subset of PPC32 only.

Could you also elaborate a bit on the kind of issues you forsee or fear 
with applications and FPGA device drivers.

FWIW I sent out today a patch that removes CONFIG_HIGHMEM complely on 
powerpc in order to get a better view of the impacted areas and allow 
people to test what it looks like on their system without 
CONFIG_HIGHMEM. See [1].

Christophe

[1] 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/28d908b95fe358129db18f69b30891788e15ada0.1757512010.git.christophe.leroy@csgroup.eu/


  parent reply	other threads:[~2025-09-10 17:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 21:23 Arnd Bergmann
2025-09-09 21:38 ` H. Peter Anvin
2025-09-09 22:24   ` Linus Torvalds
2025-09-09 22:39     ` H. Peter Anvin
2025-09-10  1:06     ` René Herman
2025-09-10  1:46 ` Matthew Wilcox
2025-09-10  9:49   ` Linus Walleij
2025-09-10 12:17   ` Arnd Bergmann
2025-09-10 12:32     ` David Hildenbrand
2025-09-10 13:10 ` Linus Walleij
2025-09-10 14:04   ` Matthew Wilcox
2025-09-10 15:13     ` Arnd Bergmann
2025-09-10 14:04 ` Richard Weinberger
2025-09-10 16:34   ` Dave Hansen
2025-09-10 20:33     ` Richard Weinberger
2025-09-10 21:56       ` René Herman
2025-09-12 10:30       ` Arnd Bergmann
2025-09-12 12:46         ` Linus Walleij
2025-10-06 20:15         ` Richard Weinberger
2025-09-10 17:11   ` Christophe Leroy [this message]
2025-09-10 19:37     ` Richard Weinberger
2025-09-11  5:38 ` Andreas Larsson
2025-09-11  7:53   ` Arnd Bergmann
2025-09-12  9:32     ` Andreas Larsson
2025-09-12  9:36       ` H. Peter Anvin
2025-09-12 10:17       ` Arnd Bergmann
2025-09-12  9:58   ` H. Peter Anvin
2025-09-12 13:16     ` Matthew Wilcox
2025-09-12 16:49 ` Nicolas Ferre
2025-09-12 21:09   ` Arnd Bergmann
2025-09-17 12:59 ` Jason Gunthorpe
2025-09-18 13:12   ` Arnd Bergmann
2025-09-18 13:34     ` Andrew Lunn
2025-09-18 16:18       ` Arnd Bergmann
2025-09-18 16:32         ` Andrew Lunn
2025-09-19  7:17     ` Geert Uytterhoeven
2025-09-19 14:22       ` Arnd Bergmann
2025-09-19 14:34         ` Jason Gunthorpe
2025-09-22  6:58           ` Arnd Bergmann
2025-09-22 17:05             ` Nicolas Schichan
2025-09-22 21:22               ` Arnd Bergmann
2025-09-19 14:41       ` Nicolas Ferre
2025-09-19 14:22     ` Nicolas Ferre

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=d9caedb4-41c8-4ef7-99b9-51d891aee555@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.sverdlin@gmail.com \
    --cc=andreas@gaisler.com \
    --cc=ankur.a.arora@oracle.com \
    --cc=arnd@arndb.de \
    --cc=chester.a.unal@arinc9.com \
    --cc=david@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=heiko@sntech.de \
    --cc=imx@lists.linux.dev \
    --cc=ira.weiny@intel.com \
    --cc=ksummit@lists.linux.dev \
    --cc=l.stach@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=nm@ti.com \
    --cc=richard@nod.at \
    --cc=rppt@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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