Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932768AbZAJBS5 (ORCPT ); Fri, 9 Jan 2009 20:18:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755477AbZAJBSq (ORCPT ); Fri, 9 Jan 2009 20:18:46 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:60694 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753523AbZAJBSp (ORCPT ); Fri, 9 Jan 2009 20:18:45 -0500 Date: Fri, 9 Jan 2009 20:18:41 -0500 (EST) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Ingo Molnar cc: Linus Torvalds , Harvey Harrison , "H. Peter Anvin" , Andi Kleen , Chris Mason , Peter Zijlstra , paulmck@linux.vnet.ibm.com, Gregory Haskins , Matthew Wilcox , Andrew Morton , Linux Kernel Mailing List , linux-fsdevel , linux-btrfs , Thomas Gleixner , Nick Piggin , Peter Morreale , Sven Dietrich Subject: Re: [PATCH -v7][RFC]: mutex: implement adaptive spinning In-Reply-To: <20090110010125.GA31031@elte.hu> Message-ID: References: <4966AB74.2090104@zytor.com> <20090109133710.GB31845@elte.hu> <20090109204103.GA17212@elte.hu> <20090109213442.GA20051@elte.hu> <1231537320.5726.2.camel@brick> <20090109231227.GA25070@elte.hu> <20090110010125.GA31031@elte.hu> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1871 Lines: 48 > - Headers could probably go back to 'extern inline' again. At not small > expense - we just finished moving to 'static inline'. We'd need to > guarantee a library instantiation for every header include file - this > is an additional mechanism with additional introduction complexities > and an ongoing maintenance cost. I thought the "static inline" in headers should be more of a "always inline". As Andrew Morton keeps yelling at me to use static inline instead of macros ;-) I do not see the point in the functions in the headers needing to have their "inlines" removed. > > - 'static inline' functions in .c files that are not used cause no build > warnings - while if we change them to 'static', we get a 'defined but > not used' warning. Hundreds of new warnings in the allyesconfig builds. Perhaps that's a good thing to see what functions are unused in the source. > > I know that because i just have removed all variants of 'inline' from all > .c files of the kernel, it's a 3.5MB patch: > > 3263 files changed, 12409 insertions(+), 12409 deletions(-) > > x86 defconfig comparisons: > > text filename > 6875817 vmlinux.always-inline ( 0.000% ) > 6838290 vmlinux.always-inline+remove-c-inlines ( -0.548% ) > 6794474 vmlinux.optimize-inlining ( -1.197% ) > > So the kernel's size improved by half a percent. Should i submit it? Are there cases that are "must inline" in that patch? Also, what is the difference if you do vmlinux.optimize-remove-c-inlines? Is there a difference there? -- Steve -- 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/