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
Date: Tue, 12 May 2015 11:48:37 +0200 [thread overview]
Message-ID: <20150512094837.GC11477@gmail.com> (raw)
In-Reply-To: <5551CB8B.6060007@redhat.com>
* 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
next prev parent reply other threads:[~2015-05-12 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 17:57 [PATCH] force inlining of spinlock ops Denys Vlasenko
2015-05-11 18:53 ` Josh Triplett
2015-05-11 22:19 ` Andrew Morton
2015-05-12 8:16 ` Hagen Paul Pfeifer
2015-05-12 9:44 ` Denys Vlasenko
2015-05-12 9:48 ` Ingo Molnar [this message]
2015-05-12 7:44 ` Ingo Molnar
2015-05-12 11:02 ` Denys Vlasenko
2015-05-12 11:43 ` Ingo Molnar
2015-05-12 13:13 ` Denys Vlasenko
2015-05-13 10:17 ` Ingo Molnar
2015-05-13 10:28 ` Denys Vlasenko
2015-05-13 10:43 ` Ingo Molnar
2015-05-13 14:09 ` Denys Vlasenko
2015-05-15 7:20 ` Heiko Carstens
-- strict thread matches above, loose matches on Subject: below --
2015-07-13 18:31 Denys Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150512094837.GC11477@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=davem@davemloft.net \
--cc=dvlasenk@redhat.com \
--cc=hagen@jauu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=tgraf@suug.ch \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).