From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: implement optimized percpu variable access
Date: Mon, 12 Nov 2012 15:01:58 -0600 [thread overview]
Message-ID: <50A163C6.6080208@gmail.com> (raw)
In-Reply-To: <20121112165117.GB18863@mudshark.cambridge.arm.com>
On 11/12/2012 10:51 AM, Will Deacon wrote:
> On Mon, Nov 12, 2012 at 02:41:22PM +0000, Will Deacon wrote:
>> On Mon, Nov 12, 2012 at 02:21:27PM +0000, Rob Herring wrote:
>>> On 11/12/2012 04:23 AM, Will Deacon wrote:
>>>> Hi Rob,
>>>>
>>>> On Sun, Nov 11, 2012 at 03:20:40AM +0000, Rob Herring wrote:
>>>>> From: Rob Herring <rob.herring@calxeda.com>
>>>>>
>>>>> Use the previously unused TPIDRPRW register to store percpu offsets.
>>>>> TPIDRPRW is only accessible in PL1, so it can only be used in the kernel.
>>>>>
>>>>> This saves 2 loads for each percpu variable access which should yield
>>>>> improved performance, but the improvement has not been quantified.
>>>>
>>>> The patch looks largely fine to me (one minor comment below), but we should
>>>> try and see what the performance difference is like on a few cores before
>>>> merging this. Have you tried something like hackbench to see if the
>>>> difference is measurable there? If not, I guess we'll need something more
>>>> targetted.
>>>
>>> Looks like it's about a 1.4% improvement on Cortex-A9 (highbank) with
>>> hackbench.
>>>
>>> Average of 30 runs of "hackbench -l 1000":
>>>
>>> Before: 6.2190666667
>>> After: 6.1347666667
>>>
>>> I'll add this data to the commit msg.
>>
>> Wow, that's really cool! I'll take it for a spin on 11MPCore to test the v6
>> angle...
>
> Ok, similar numbers over here so it looks like this is definitely worth
> doing. However, I still object to the "cc", particularly after discussion
> with the tools guys here who agree that the behaviour you're seeing is
> indicative of a buggy compiler. It may even be part of a larger issue with
> GCC's definition of `reachability' for kernel entry points. For interest, I
> failed to reproduce with:
>
> gcc version 4.7.3 20121001 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2012.10-20121022 - Linaro GCC 2012.10)
> (http://launchpad.net/linaro-toolchain-binaries/trunk/2012.10/+download/gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2)
>
> which sounds fairly close to the tools that you are using. Please can you
> file a bug in launchpad?
Strangely, I can't reproduce it either now...
Rob
next prev parent reply other threads:[~2012-11-12 21:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 3:20 [PATCH] ARM: implement optimized percpu variable access Rob Herring
2012-11-12 10:23 ` Will Deacon
2012-11-12 13:03 ` Rob Herring
2012-11-12 13:28 ` Will Deacon
2012-11-12 14:03 ` Rob Herring
2012-11-27 17:29 ` Nicolas Pitre
2012-11-12 14:21 ` Rob Herring
2012-11-12 14:41 ` Will Deacon
2012-11-12 16:51 ` Will Deacon
2012-11-12 21:01 ` Rob Herring [this message]
2012-11-13 10:40 ` Will Deacon
2012-11-22 11:34 ` Will Deacon
2012-11-22 11:39 ` Russell King - ARM Linux
2012-11-23 17:06 ` Rob Herring
2012-11-23 17:12 ` Russell King - ARM Linux
2012-11-23 17:16 ` Will Deacon
2012-11-23 20:34 ` Tony Lindgren
2012-11-23 20:32 ` Tony Lindgren
2012-11-25 18:46 ` Rob Herring
2012-11-26 11:13 ` Will Deacon
2012-11-26 15:15 ` Will Deacon
2012-11-26 17:30 ` Rob Herring
2012-11-27 13:17 ` Will Deacon
2012-11-27 13:26 ` Russell King - ARM Linux
2012-11-26 21:58 ` Jamie Lokier
2012-11-26 23:50 ` Jamie Lokier
2012-11-27 1:02 ` Jamie Lokier
2012-11-27 22:02 ` Rob Herring
2012-11-28 12:34 ` Will Deacon
2012-11-27 17:35 ` Nicolas Pitre
2012-11-27 19:27 ` Nicolas Pitre
2012-11-27 17:19 ` Nicolas Pitre
2012-11-27 19:37 ` Rob Herring
2012-11-27 20:42 ` Rob Herring
2012-11-27 22:02 ` Nicolas Pitre
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=50A163C6.6080208@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 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.