From: Paulo Marques <pmarques@grupopie.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: kai.germaschewski@gmx.de, kai@germaschewski.name,
linux-kernel <linux-kernel@vger.kernel.org>,
akpm@osdl.org
Subject: Re: [PATCH] do not save thousands of useless symbols in KALLSYMS kernels
Date: Thu, 11 Aug 2005 12:16:17 +0100 [thread overview]
Message-ID: <42FB3381.3010809@grupopie.com> (raw)
In-Reply-To: <200508111403.39708.vda@ilport.com.ua>
Denis Vlasenko wrote:
> Sample of my kernel's mostly useless symbols
> (starting_with:# of symbols):
>
> __func__: 624
> __vendorstr_: 1760
> __pci_fixup_PCI_: 116
> __ksymtab_: 2597
> __kstrtab_: 2597
> __kcrctab_: 2597
> __initcall_: 236
> __devicestr_: 4686
> __devices_: 1760
> Total: 16973
> Lines in System.map: 39735
>
> Excluding them from in-kernel symbol table saves ~300kb:
>
> text data bss dec hex filename
> 4337710 1054414 259296 5651420 563bdc vmlinux.carrier1 - w/o KALLSYMS
> 4342068 1296046 259296 5897410 59fcc2 vmlinux - with KALLSYMS+patch
> 4341948 1607634 259296 6208878 5ebd6e vmlinux.carrier - with KALLSYMS
> ^^^^^^^
Hummm.... these symbols should only go in if you config KALLSYMS_ALL.
Are you sure your configuration doesn't have KALLSYMS_ALL enabled?
If it does, it seems like the correct behavior to include all symbols if
you specified that you wanted _all_ symbols :)
By the way, there is a completely different version of
scripts/kallsyms.c in -mm that you might want to look at. It will
probably go in after 2.6.13 is out.
--
Paulo Marques - www.grupopie.com
It is a mistake to think you can solve any major problems
just with potatoes.
Douglas Adams
next prev parent reply other threads:[~2005-08-11 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 11:03 Denis Vlasenko
2005-08-11 11:16 ` Paulo Marques [this message]
2005-08-11 11:38 ` Denis Vlasenko
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=42FB3381.3010809@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=kai.germaschewski@gmx.de \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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
all inboxes | Powered by JetHome®