From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Ingo Molnar <mingo@kernel.org>,
Denys Vlasenko <vda.linux@googlemail.com>
Cc: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH RFC] x86: enforce inlining for atomics
Date: Mon, 13 Jul 2015 21:20:16 +0200 (CEST) [thread overview]
Message-ID: <131222735.1080.1436815216582.JavaMail.open-xchange@ox1app> (raw)
In-Reply-To: <CAK1hOcPknhNFjihFheF9mwPJbp_++5XCoyMyAPOvs243E1g=Uw@mail.gmail.com>
> On July 13, 2015 at 8:27 PM Denys Vlasenko <vda.linux@googlemail.com>
> wrote:
> > So I think the original patch makes sense (and I already applied it),
> > we want known-simple and performance critical methods (such as atomic
> > ops) always inlined.
>
> I will send more such force-inlining patches your way then.
Now? We discuss this a month back or so? :-)
Anyway, if so I prefer to group the patchset in at least two patches to
simplify review:
- performance criticial group
- inline assembler group
The former group contains all inline critical functions and the later to
identify functions where gcc has problems because their inline heuristic
for asm code is a toy.
Hagen
next prev parent reply other threads:[~2015-07-13 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:27 [PATCH RFC] x86: enforce inlining for atomics Hagen Paul Pfeifer
2015-04-20 21:56 ` Borislav Petkov
2015-04-20 22:08 ` Hagen Paul Pfeifer
2015-04-21 7:42 ` Ingo Molnar
2015-04-21 10:56 ` Hagen Paul Pfeifer
2015-04-21 22:57 ` Hagen Paul Pfeifer
2015-04-22 0:57 ` Linus Torvalds
2015-04-22 5:24 ` Markus Trippelsdorf
2015-04-22 5:58 ` Hagen Paul Pfeifer
2015-04-22 9:20 ` Markus Trippelsdorf
2015-04-22 9:28 ` Ingo Molnar
2015-04-22 9:31 ` Hagen Paul Pfeifer
2015-04-30 1:52 ` Henrique de Moraes Holschuh
2015-07-13 18:27 ` Denys Vlasenko
2015-07-13 19:20 ` Hagen Paul Pfeifer [this message]
2015-07-13 21:06 ` Denys Vlasenko
2015-07-13 21:12 ` Hagen Paul Pfeifer
2015-07-13 18:25 ` Denys Vlasenko
2015-04-20 23:46 ` Peter Zijlstra
2015-04-22 14:10 ` [tip:x86/asm] x86/asm: Always inline atomics tip-bot for Hagen Paul Pfeifer
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=131222735.1080.1436815216582.JavaMail.open-xchange@ox1app \
--to=hagen@jauu.net \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.