From: Andi Kleen <andi@firstfloor.org>
To: Uwe Hermann <uwe@hermann-uwe.de>
Cc: Matt Mackall <mpm@selenic.com>, Andi Kleen <andi@firstfloor.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Jonathan Campbell <jon@nerdgrounds.com>,
linux-kernel@vger.kernel.org
Subject: Re: Patches for REALLY TINY 386 kernels
Date: Fri, 20 Jul 2007 09:35:09 +0200 [thread overview]
Message-ID: <20070720073509.GA19833@one.firstfloor.org> (raw)
In-Reply-To: <20070720072730.GN3700@greenwood>
> Some people are putting Linux kernels in the "BIOS" (i.e. ROM chip) when
> using LinuxBIOS (www.linuxbios.org). It _does_ make a lot of difference
> there how big the kernel is. At the moment you can't do that with
> anything smaller than a 1 MB chip. But if people could use 512 KB chips
> because the kernel is small enough that would sure be a great thing.
I'm sure it would be possibel to save a lot of text size. But I don't
think removing the relatively small CPUID code is the right way.
That is just a big maintenance issue for little gain.
If you're seriously interested you should start measuring and then
attack the real bloat pigs. e.g. a good way is to look for unneeded
inlining.
And also do regression testing, like running bloat-o-meter between
releases and complaining about subsystems which have grown unduly.
-Andi
next prev parent reply other threads:[~2007-07-20 7:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 21:00 Patches for REALLY TINY 386 kernels Jonathan Campbell
2007-07-15 21:42 ` Nigel Cunningham
2007-07-15 22:45 ` Alan Cox
2007-07-15 23:12 ` Nigel Cunningham
2007-07-15 23:14 ` Satyam Sharma
2007-07-15 23:13 ` Arnd Bergmann
2007-07-15 23:28 ` Satyam Sharma
2007-07-15 23:05 ` Adrian Bunk
2007-07-15 23:08 ` H. Peter Anvin
2007-07-17 10:59 ` Jan Engelhardt
2007-07-17 19:30 ` Matt Mackall
2007-07-18 2:33 ` Andi Kleen
2007-07-18 15:55 ` H. Peter Anvin
2007-07-18 18:20 ` Andi Kleen
2007-07-18 18:29 ` Jan Engelhardt
2007-07-18 18:38 ` Andi Kleen
2007-07-18 18:45 ` Jan Engelhardt
2007-07-18 18:47 ` Andi Kleen
2007-07-18 20:24 ` John Stoffel
2007-07-18 18:33 ` Adrian Bunk
2007-07-18 18:42 ` Jan Engelhardt
2007-07-18 18:44 ` Andi Kleen
2007-07-18 19:00 ` H. Peter Anvin
2007-07-21 10:09 ` Oleg Verych
2007-07-18 19:41 ` Matt Mackall
2007-07-18 19:50 ` H. Peter Anvin
2007-07-18 20:10 ` Andi Kleen
2007-07-18 20:24 ` H. Peter Anvin
2007-07-18 21:04 ` Andi Kleen
2007-07-18 22:17 ` H. Peter Anvin
2007-07-30 17:59 ` Denis Vlasenko
2007-07-18 20:41 ` Matt Mackall
2007-07-20 7:27 ` Uwe Hermann
2007-07-20 7:35 ` Andi Kleen [this message]
2007-07-24 14:49 ` Helge Hafting
2007-07-24 20:50 ` Yinghai Lu
2007-07-24 22:56 ` Adrian Bunk
2007-07-25 0:55 ` Yinghai Lu
2007-07-24 22:45 ` Willy Tarreau
[not found] <8HjYY-4Jk-15@gated-at.bofh.it>
[not found] ` <8HlxM-7iT-13@gated-at.bofh.it>
[not found] ` <8HlxL-7iT-11@gated-at.bofh.it>
[not found] ` <8HlHq-7vR-17@gated-at.bofh.it>
[not found] ` <8HlHr-7vR-25@gated-at.bofh.it>
2007-07-16 13:12 ` Bodo Eggert
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=20070720073509.GA19833@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jon@nerdgrounds.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=uwe@hermann-uwe.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.