On Wed, May 07, 2003 at 11:23:29AM +0200, Jörn Engel wrote:
> I've been a bit sceptical of the whole .altinstructions idea,
> self-modifying code opens a can of worms for anyone trying to do code
> analysis (coverage, verification,...). But with this followup, I
> personally pay money to get that stuff ripped out again.
Ok. How much do you pay ? ;@)
Seriously. To give some numbers. This is the maxi kernel (about 8MB .text,
everything compiled in that compiles in 2.5.69) which is far too big to even
even boot.
20 .exit.text 00005afa c0ada3d0 c0ada3d0 009db3d0 2**4
CONTENTS, ALLOC, LOAD, READONLY, CODE
About 20k from 8MB
On a realistic kernel that actually boots we are talking about 1-2KB,
probably even less. If you really wanted to combat bloat there are a lot
other areas where you can avoid much more than 2KB with minimum effort.
Just go through include/linux/* and move a few unnecessary inlines away, that
will help much more. If you want to save real memory attack mem_map, like
I proposed earlier.
-Andi
P.S.: In case someone is interested: The hall of shame for the 2.5.69 SMP
maxi kernel (stuff that doesn't build) currently is: Sound/Alsa (one driver
doesn't compile), USB (3 drivers don't compile), MTD (lots of stuff doesn't
compile). Everything else is quite good.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/