From: Paulo Marques <pmarques@grupopie.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Roland Dreier <rolandd@cisco.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move GFP_KERNEL use out of line to shrink text
Date: Thu, 15 Sep 2005 12:42:03 +0100 [thread overview]
Message-ID: <43295E0B.5000000@grupopie.com> (raw)
In-Reply-To: <200509150813.24041.vda@ilport.com.ua>
Denis Vlasenko wrote:
> On Wednesday 14 September 2005 21:39, Roland Dreier wrote:
>
>> text data bss dec hex filename
>> 24202272 7609162 1998512 33809946 203e61a vmlinux-before
>> 24197561 7609474 1998512 33805547 203d4eb vmlinux-after
>>
>>for a net savings of 4711 bytes of text (at a cost of 312 bytes of
>>data for some reason). With my usual config, the patched kernel boots
>>and runs fine.
>
> FYI: "some reason" == KALLSYMS
312 bytes for a couple more symbols is too much to be justified from
kallsyms alone.
In a 64 bit machine each new symbol should take about 8 bytes for the
address + ~ half the size of the symbol name, which in this case would
give at most about ~50 bytes.
I guess the rest should come from the extra EXPORT_SYMBOL's...
--
Paulo Marques - www.grupopie.com
The rule is perfect: in all matters of opinion our
adversaries are insane.
Mark Twain
next prev parent reply other threads:[~2005-09-15 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 15:18 [PATCH] SELinux - convert to kzalloc James Morris
2005-09-13 19:07 ` Andrew Morton
2005-09-13 20:37 ` James Morris
2005-09-14 1:43 ` Roland Dreier
2005-09-14 5:09 ` [PATCH] Create __kzalloc_gfp_kernel() Roland Dreier
2005-09-14 5:35 ` Andrew Morton
2005-09-14 18:39 ` [PATCH] Move GFP_KERNEL use out of line to shrink text Roland Dreier
2005-09-15 5:13 ` Denis Vlasenko
2005-09-15 11:42 ` Paulo Marques [this message]
2005-09-14 5:06 ` [PATCH] SELinux - convert to kzalloc 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=43295E0B.5000000@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rolandd@cisco.com \
--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 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.