From: "Arnd Bergmann" <arnd@arndb.de>
To: "Willy Tarreau" <w@1wt.eu>
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 11:13:03 +0200 [thread overview]
Message-ID: <afb4527e-3958-4b04-9bbf-d48e80616aa0@app.fastmail.com> (raw)
In-Reply-To: <20250916070052.GA3616@1wt.eu>
On Tue, Sep 16, 2025, at 09:00, Willy Tarreau wrote:
> 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!
>>
>> 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% /
Yes, that was what I did in my busybox example, which used a tiny
initramfs in the end. Your ramdisk itself is already bigger than
my total 10MB RAM here, but then it also does one thing instead
of nothing.
Arnd
next prev parent reply other threads:[~2025-09-16 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 10:53 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
2025-09-16 9:13 ` Arnd Bergmann [this message]
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=afb4527e-3958-4b04-9bbf-d48e80616aa0@app.fastmail.com \
--to=arnd@arndb.de \
--cc=AWilcox@wilcox-tech.com \
--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 \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®