linux-kernel - Re: [PATCH] printk_ratelimit functions should use CONFIG

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] [day] [month] [year] [list]

Date:	Fri, 14 Dec 2007 12:11:13 -0800
From:	Joe Perches <joe@...ches.com>
To:	Matt Mackall <mpm@...enic.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] printk_ratelimit functions should use CONFIG_PRINTK

On Fri, 2007-12-14 at 13:12 -0600, Matt Mackall wrote:
> On Fri, Dec 14, 2007 at 11:00:35AM -0800, Joe Perches wrote:
> > Makes an embedded image a bit smaller
> 
> Looks good to me. This should probably go to Andrew first though. And
> it wouldn't hurt to see some size(1) results.

For instance:

x86 32 Allnoconfig, CONFIG_EMBEDDED=y CONFIG_PRINTK not set

with:

$ size -A vmlinux

vmlinux  :
section                      size         addr
.text                      697864   3222274240
.rodata                    121988   3222974464
.data                       75952   3223097344
.bss                        69632   3223289856
Total                     1095589

without:

$ size -A vmlinux
vmlinux  :
section                      size         addr
.text                      698376   3222274240
.rodata                    122032   3222978560
.data                       76080   3223101440
.bss                        69632   3223298048
Total                     1096273


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