Re: [patch 0/3] Allow inlined spinlocks again V3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Sun, 16 Aug 2009, Heiko Carstens wrote:
> > 
> > An allyesconfig (CONFIG_FTRACE disabled) on x86_64 with gcc 
> > 4.3.2 results in the following vmlinux sizes:
> > 
> > 574152755 2009-08-16 20:05 vmlinux-orig
> > 574862000 2009-08-16 20:13 vmlinux-skb-inline
> 
> It's more relevant to look at just code size. BUG_ON() has more of 
> an impact on data sizes, because it does something like 10-12 
> bytes of exception data for each bug-on. But that exception data 
> is out-of-line and not interesting.
> 
> If the code size blows up a lot, that's worse than if the data 
> size expands a bit.

Also, allyesconfig isnt really relevant to inlining cost in general 
as it enables everything. The defconfigs are better (at least on 
x86) because they tend to be some distro-alike config - i.e. they 
are closer to what most Linux users will run in the end.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux