linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix .altinstructions linking failures
Date: Wed, 7 May 2003 12:16:37 +0200	[thread overview]
Message-ID: <20030507101637.GB2389@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030507094752.GA4050@averell>

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

  reply	other threads:[~2003-05-07 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  6:30 [PATCH] Fix .altinstructions linking failures Andi Kleen
2003-05-06 16:44 ` Adrian Bunk
2003-05-06 19:56   ` Andi Kleen
2003-05-06 21:08     ` Andi Kleen
2003-05-06 21:25       ` Andrew Morton
2003-05-06 21:45         ` Andi Kleen
2003-05-07  9:23 ` Jörn Engel
2003-05-07  9:47   ` Andi Kleen
2003-05-07 10:16     ` Jörn Engel [this message]
2003-05-07 16:38     ` Greg KH
2003-05-10  8:50     ` Adrian Bunk
2003-05-10 15:41       ` Jörn Engel

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=20030507101637.GB2389@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    /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).