linux-kernel - Re: [PATCH 1/2] Colored kernel output (run3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071007170845.GD32139@elte.hu>
Date:	Sun, 7 Oct 2007 19:08:45 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Verych <olecom@...wer.upol.cz>
Subject: Re: [PATCH 1/2] Colored kernel output (run3)


* Jan Engelhardt <jengelh@...putergmbh.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/