linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ash Logan <ash@heyquark.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	officialTechflashYT@gmail.com,
	"A. Wilcox" <AWilcox@wilcox-tech.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: 32-bit HIGHMEM and game console downstreams
Date: Tue, 16 Sep 2025 09:00:52 +0200	[thread overview]
Message-ID: <20250916070052.GA3616@1wt.eu> (raw)
In-Reply-To: <39164c56-78f8-4bac-acd2-a996149c1c57@app.fastmail.com>

On Tue, Sep 16, 2025 at 08:20:35AM +0200, Arnd Bergmann wrote:
> > The maintainer of that downstream claims to be able to boot modern 
> > text-mode distros on the GameCube' 24MB, which I find really impressive!
> 
> 24MB is impressive indeed. In my latest tests I did not get below 32MB
> (+swap) on an ARMv7 kernel with Debian Bookworm, and major features
> turned off in both kernel and userland.
> 
> On a simpler musl+busybox userland and even more feature reduced
> kernel (no network, initramfs-only) I could get to ~10MB, but then it
> doesn't really do anything besides showing a shell.

When you build your systems from source and install only the necessary
*files* (not packages) you can get much lower. Here's my reverse-proxy
for example (aarch64):

  $ df /
  Filesystem     1K-blocks  Used Available Use% Mounted on
  /dev/ram0          11520 11520         0 100% /

and my firewall:

  $ df /
  Filesystem     1K-blocks  Used Available Use% Mounted on
  /dev/ram0          16640 16640         0 100% /

these are full-featured images with tcpdump, exim, haproxy, nftables,
pppd, ntpd, wireguard, openvpn, hostapd etc and even glibc. I've been
used to installing them on 25128 SPI NOR flashes (16 MB). But yeah
that requires gcc -Os, getting rid of NLS, deciding on a case by case
basis between shared or static linking, and installing the strict
minimum for each service. I even have an old boot loader recovery
image where kernel+initramfs fit into just 1 MB with a small recovery
shell, mke2fs, dropbear and tftp client (i386).

Cheers,
Willy


  reply	other threads:[~2025-09-16  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 10:53 32-bit HIGHMEM and game console downstreams Ash Logan
2025-09-13 13:52 ` Arnd Bergmann
2025-09-16  1:57   ` Ash Logan
2025-09-16  6:20     ` Arnd Bergmann
2025-09-16  7:00       ` Willy Tarreau [this message]
2025-09-16  9:13         ` Arnd Bergmann
2025-09-16 16:58     ` Segher Boessenkool
2025-09-14 14:14 ` Segher Boessenkool
2025-09-16  2:10   ` Ash Logan
2025-09-16 15:41     ` Segher Boessenkool

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=20250916070052.GA3616@1wt.eu \
    --to=w@1wt.eu \
    --cc=AWilcox@wilcox-tech.com \
    --cc=arnd@arndb.de \
    --cc=ash@heyquark.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=officialTechflashYT@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).