From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Anton Blanchard <anton@samba.org>
Subject: Re: 64bit kernel is huge
Date: Wed, 30 Sep 2009 15:57:42 +0200 [thread overview]
Message-ID: <200909301557.42625.arnd@arndb.de> (raw)
In-Reply-To: <20090928074503.GB16073@kryten>
On Monday 28 September 2009, Anton Blanchard wrote:
> 262144 kstat_irqs_all
> 131072 irq_desc
> 16384 irq_stat
>
> Could we dynamically allocate our irq structures?
There were patches floating around for that a few years ago,
but I haven't seen anyone working on it since.
> 131072 lppaca
> 65536 paca
>
> I think we've attacked these before, not sure if there is anything left
> we can trim.
well, it essentially comes down to CONFIG_NR_CPUS. If you build with NR_CPUS=4,
this is really small.
> 131072 __log_buf
>
> Looks like we can dynamically allocate a large log buf at runtime. Perhaps
> we should default to a small log_buf and grow it at boot based on machine size
> (eg max cpus).
I like the idea of being able to very easily find the log buffer in
dump files or in hw debuggers for bringup, but it's probably not
worth it for production systems. A config option might be nice.
> 101160 powerpc_opcodes
>
> xmon instruction disassembly. I'd probably prefer to cut off my right hand and
> debug one handed before losing this though.
This should be very compressible though, which will help binary size, but not
runtime memory footprint.
> 77452 _fw_acenic_tg2_bin_bin
>
> We could probably change acenic to be a module,
CONFIG_FIRMWARE_IN_KERNEL ?
> 17784 ioctl_start
I have a patch for this one that I need to submit some day.
Arnd <><
next prev parent reply other threads:[~2009-09-30 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 7:45 64bit kernel is huge Anton Blanchard
2009-09-28 8:07 ` Benjamin Herrenschmidt
2009-09-28 9:13 ` Michael Ellerman
2009-09-30 6:01 ` Michael Neuling
2009-09-30 20:30 ` Benjamin Herrenschmidt
2009-10-01 5:06 ` Michael Neuling
2009-10-01 5:09 ` Michael Neuling
2009-09-30 13:57 ` Arnd Bergmann [this message]
2009-10-01 3:36 ` Michael Ellerman
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=200909301557.42625.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.