Re: [PATCH] Fix .altinstructions linking failures

Jörn Engel (joern@wohnheim.fh-wedel.de)
Wed, 7 May 2003 12:16:37 +0200


On Wed, 7 May 2003 11:47:52 +0200, Andi Kleen wrote:
> 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.

Sounds more like 1/2 maxi to me, but you are basically right. 2-3k on
one of my production embedded kernels. I can accept that, but it
doesn't really make me happy.

> 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.

Still on my list, but I didn't get to it yet.

> 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.

Do you have a .config for that kernel. I tried to create a maximal one
for 2.5.69 as well, but the problems in the Subject: stopped me and ld
didn't give me enough clues, which drivers to remove.

Jörn

-- 
When people work hard for you for a pat on the back, you've got
to give them that pat.
-- Robert Heinlein
-
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/