public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Will Newton <will.newton@linaro.org>
To: "Ondřej Bílka" <neleai@seznam.cz>
Cc: "Shih-Yuan Lee (FourDollars)" <sylee@canonical.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
		libc-ports@sourceware.org, Jesse Sung <jesse.sung@canonical.com>,
	patches@eglibc.org, 	YC Cheng <yc.cheng@canonical.com>,
	rex.tsai@canonical.com
Subject: Re: [Patches] [PATCH] ARM: NEON detected memcpy.
Date: Mon, 08 Apr 2013 09:12:00 -0000	[thread overview]
Message-ID: <CANu=DmjvA9F_opxpwvNb-BMA63obkrr8RVW+yG3PDuhQm9zjHQ@mail.gmail.com> (raw)
In-Reply-To: <20130404063701.GA6324@domone.kolej.mff.cuni.cz>

On 4 April 2013 07:37, Ondřej Bílka <neleai@seznam.cz> wrote:
> On Thu, Apr 04, 2013 at 12:15:17PM +0800, Shih-Yuan Lee (FourDollars) wrote:
>> Hi Ondrej,
>>
>> I do have some benchmark data.
>>
> Hi,
>
> Try also benchmark with real world data (20MB). I put it on
> http://kam.mff.cuni.cz/~ondra/dryrun_memcpy.tar.bz2

Hi Ondrej,

How was the workload chosen for this test run? Is it a known "memcpy
hot" workload?

Also it looks like the data was captured on x86_64? I suspect we
should use a specific data set for each architecture - the alignment
of data will change depending on the ABI alignment rules and different
compilers inline e.g. constant sized memcpys in different ways. Last
time I looked gcc seemed to be much more aggressive with inlining
string functions on x86 than arm for example.

Thanks,

-- 
Will Newton
Toolchain Working Group, Linaro

  reply	other threads:[~2013-04-08  9:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  7:58 Shih-Yuan Lee (FourDollars)
2013-04-03  8:15 ` Will Newton
2013-04-03  9:19   ` Ondřej Bílka
2013-04-03 15:08 ` Joseph S. Myers
2013-04-03 15:48   ` Shih-Yuan Lee (FourDollars)
2013-04-03 16:02     ` Joseph S. Myers
2013-04-04  3:56       ` Shih-Yuan Lee (FourDollars)
2013-04-03 16:20     ` [Patches] " Ondřej Bílka
2013-04-04  4:15       ` Shih-Yuan Lee (FourDollars)
2013-04-04  6:37         ` Ondřej Bílka
2013-04-08  9:12           ` Will Newton [this message]
2013-04-08 10:27             ` Ondřej Bílka
2013-04-09  8:45         ` Richard Earnshaw
2013-04-09  9:05   ` Richard Earnshaw
2013-04-09 12:04     ` Ondřej Bílka
2013-04-09 12:59     ` Carlos O'Donell
2013-04-09 15:00       ` Richard Earnshaw
2013-04-09 15:54         ` Ondřej Bílka
2013-04-09 15:59         ` Carlos O'Donell

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=DmjvA9F_opxpwvNb-BMA63obkrr8RVW+yG3PDuhQm9zjHQ@mail.gmail.com' \
    --to=will.newton@linaro.org \
    --cc=jesse.sung@canonical.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=neleai@seznam.cz \
    --cc=patches@eglibc.org \
    --cc=rex.tsai@canonical.com \
    --cc=sylee@canonical.com \
    --cc=yc.cheng@canonical.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).