Date: Tue, 12 May 2015 11:48:37 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Thomas Graf <tgraf@suug.ch>, "David S. Miller" <davem@davemloft.net>,
        Bart Van Assche <bvanassche@acm.org>,
        Peter Zijlstra <peterz@infradead.org>,
        David Rientjes <rientjes@google.com>, Oleg Nesterov <oleg@redhat.com>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        linux-kernel@vger.kernel.org, Hagen Paul Pfeifer <hagen@jauu.net>
Subject: Re: [PATCH] force inlining of spinlock ops
Message-ID: <20150512094837.GC11477@gmail.com>
References: <1431367042-31475-1-git-send-email-dvlasenk@redhat.com>
 <20150511151913.86c37cde9294700b4b0e26c4@linux-foundation.org>
 <5551CB8B.6060007@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5551CB8B.6060007@redhat.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 896
Lines: 23


* Denys Vlasenko <dvlasenk@redhat.com> wrote:

> > Also, the inline_for_broken_gcc definition can be made dependent 
> > on particular gcc versions, which will allow us to easily keep an 
> > eye on the behaviour of later gcc versions.
> 
> I've seen it on gcc-4.7.2 and gcc-4.9.2, so this behavior is not 
> limited to a narrow range of gcc versions. I'd say by now about half 
> of running kernels can easily be affected.

Please do the measurements on x86 defconfig (with OPTIMIZE_FOR_SIZE 
and OPTIMIZE_INLINING enabled if necessary), to make sure we are truly 
getting a decrease in kernel size on common distro configs as well.

Thanks,

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