public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Stefan Wiehler <stefan.wiehler@nokia.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Highmem on AXM and K2
Date: Fri, 19 Sep 2025 15:24:57 +0200	[thread overview]
Message-ID: <8f104eba-6805-46e0-90da-232ce18973c5@nokia.com> (raw)

Hi Arnd,

You've been calling out for users still needing highmem, and here we are ;-) We
use both the Intel AXM 5516 and the TI KeyStone II with > 4 GB of RAM in our
networking products.

We use the AXM 5516 with 6 GB of RAM and highmem is therefore a must for us.
The latest estimate from product management for EOL is June 2029. We would
appreciate if this date (plus some buffer) could be kept in mind when choosing
the last LTS kernel with highmem.

With the TI K2, the situation is more complicated: The EOL for the latest
product hasn't even been defined yet, but most likely we need to support it
until 2037; it really depends on when the last 2G/3G networks will be shut
down. Obviously the community cannot wait that long with highmem removal. While
we have 5 GB of RAM there, a little bit less than half is used by Linux. I see
two options:

1. We'll need to evaluate if we could move away from current CONFIG_MEMSPLIT_3G
with our rather special memory configuration. My current understanding is that
there hasn't been a lot of interest in getting CONFIG_VMSPLIT_4G_4G into
mainline. As we cannot accept major performance degradation, I doubt that this
will be a viable path.
2. We'll need to switch over to the last highmem-enabled SLTS kernel, earliest
around 2028 (to keep some support buffer).

Kind regards,

Stefan


             reply	other threads:[~2025-09-19 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 13:24 Stefan Wiehler [this message]
2025-09-22 13:20 ` Highmem on AXM and K2 Arnd Bergmann
2025-10-15 16:08   ` Stefan Wiehler
2026-04-15 14:48     ` Stefan Wiehler
2026-04-15 15:32       ` Arnd Bergmann

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=8f104eba-6805-46e0-90da-232ce18973c5@nokia.com \
    --to=stefan.wiehler@nokia.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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