lkml.org 
[lkml]   [2007]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] Colored kernel output (run3)

* Jan Engelhardt <jengelh@computergmbh.de> wrote:

>
> On Oct 7 2007 18:59, Ingo Molnar wrote:
> >> > vmlinux:
> >> > text data bss dec hex filename
> >> > 7732358 1157269 401408 9291035 8dc51b vmlinux.before
> >> > 7732374 1157269 401408 9291051 8dc52b vmlinux.after
> >> >
> >> >16 bytes, or 0.0002% of the total text size. So there's in essence no
> >> >text overhead to talk about. So the text overhead argument is a red
> >> >herring.
> >>
> >> 16 bytes, huh? Can't be. That would be like, perhaps 5, x86 instructions.
> >
> >yes, it's that low, and it's with the feature disabled.
>
> Ah, with CONFIG_CKO=n, right. But where does that 16 byte increase
> come from, when vt.o itself remains constant in size?

comes from printk.o:

text data bss dec hex filename
6068 231 17636 23935 5d7f kernel/printk.o
6075 231 17636 23942 5d86 kernel/printk.o

the effect of the extra parameter. But that is not worth #ifdef-ing for.
For all practical purposes there's no overhead.

Ingo
-
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/

\
 
 \ /
  Last update: 2007-10-07 19:11    [W:0.047 / U:10.784 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site