public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Will Newton <will.newton@linaro.org>
To: Torvald Riegel <triegel@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	"Carlos O'Donell" <carlos@redhat.com>,
		GLIBC Devel <libc-alpha@sourceware.org>,
	libc-ports <libc-ports@sourceware.org>
Subject: Re: [PATCH] Unify pthread_once (bug 15215)
Date: Mon, 31 Mar 2014 11:44:00 -0000	[thread overview]
Message-ID: <CANu=DmiGP9b+KSW3DrQKoFCKVQ3mscajBz0-ZASivKQVEXbtjw@mail.gmail.com> (raw)
In-Reply-To: <1381182784.18547.138.camel@triegel.csb>

On 7 October 2013 22:53, Torvald Riegel <triegel@redhat.com> wrote:
> On Mon, 2013-10-07 at 16:04 +0000, Joseph S. Myers wrote:
>> I have no comments on the substance of this patch, but note that ports/
>> has a separate ChangeLog file for each architecture.
>
> Sorry. The attached patch now has separate ChangeLog entries for each of
> the affected archs.

There seems to be a significant performance delta on aarch64:

Old code:

"pthread_once": {
"": {
"duration": 9.29471e+09, "iterations": 1.10667e+09, "max": 24.54,
"min": 8.38, "mean": 8.39882

New code:

"pthread_once": {
"": {
"duration": 9.72366e+09, "iterations": 4.33843e+08, "max": 30.86,
"min": 22.38, "mean": 22.4128

And also ARM:

Old code:

"pthread_once": {
"": {
"duration": 8.38662e+09, "iterations": 6.6695e+08, "max": 35.292,
"min": 12.416, "mean": 12.5746

New code:

"pthread_once": {
"": {
"duration": 9.26424e+09, "iterations": 3.07574e+08, "max": 86.125,
"min": 28.875, "mean": 30.1204

It would be nice to understand the source of this variation. I can put
it on my todo list but I can't promise I will be able to look at it
any time soon.

-- 
Will Newton
Toolchain Working Group, Linaro

  reply	other threads:[~2014-03-31 11:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 14:44 Torvald Riegel
2013-05-08 17:51 ` Rich Felker
2013-05-08 20:47   ` Torvald Riegel
2013-05-08 21:25     ` Rich Felker
2013-05-09  8:39       ` Torvald Riegel
2013-05-09 14:02         ` Rich Felker
2013-05-09 15:14           ` Torvald Riegel
2013-05-09 15:56             ` Rich Felker
2013-05-10  8:31               ` Torvald Riegel
2013-05-10 13:22                 ` Rich Felker
2013-05-23  4:15 ` Carlos O'Donell
2013-08-26 12:50   ` Ondřej Bílka
2013-08-26 16:45     ` Rich Felker
2013-08-26 18:41       ` Ondřej Bílka
2013-08-27  2:29         ` Rich Felker
2013-10-06  0:20   ` Torvald Riegel
2013-10-06 21:41     ` Torvald Riegel
2013-10-07 16:04     ` Joseph S. Myers
2013-10-07 21:53       ` Torvald Riegel
2014-03-31 11:44         ` Will Newton [this message]
2014-03-31 20:09           ` Torvald Riegel

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='CANu=DmiGP9b+KSW3DrQKoFCKVQ3mscajBz0-ZASivKQVEXbtjw@mail.gmail.com' \
    --to=will.newton@linaro.org \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=triegel@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).