Re: [PATCH] force inlining of spinlock ops

[Heiko Carstens]

On Wed, May 13, 2015 at 04:09:18PM +0200, Denys Vlasenko wrote:
> On 05/13/2015 12:43 PM, Ingo Molnar wrote:
> > We only know that the net effect is +70 bytes. Does that come out of:
> > 
> >  - large fluctuations such as -1000-1000+1000+1070, which happens to 
> >    net out into a small net number?
> > 
> >  - or does it come from much smaller fluctuations?
> > 
> > So to make an informed decision we need to know those details.
> 
> Fair enough. Let's investigate.
> 
> I produced a list of functions with their sizes from each vmlinux,
> and diffed them:
> 
> $ nm --size-sort vmlinux | sed 's/\.[0-9]*.*/.NNN/' >vmlinux.nm
> $ nm --size-sort vmlinuxO2.before | sed 's/\.[0-9]*.*/.NNN/' >vmlinuxO2.before.nm
> $ diff -u vmlinuxO2.before.nm vmlinux.nm | grep -v '^[ @]' >vmlinux.nm.dif

FWIW, scripts/bloat-o-meter is a nice tool to examine the size differences
of two vmlinux images.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/