public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: [RFC]: Removing old Falkor ifuncs
Date: Wed, 21 Dec 2022 17:27:08 +0000	[thread overview]
Message-ID: <PAWPR08MB898232B3AA0D061EC6562A3483EB9@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PAWPR08MB8982BB3BDB74B7A370D6212A831C9@PAWPR08MB8982.eurprd08.prod.outlook.com>

Hi Siddhesh,

>>On 2022-12-09 10:14, Wilco Dijkstra wrote:
>>> Do we need the ifuncs for Falkor? The SIMD memcpy is now the default
>>> generic memcpy and that is quite similar to the Falkor one, so it seems
>>> time to remove the Falkor variants. Since you are the original author,
>>> what do you think?
>>
>> The key differentiator in memcpy/memmove at that time was the register 
>> number usage since that affected how the hardware prefetcher performed. 
>> Changing that might affect performance on falkor, although I don't 
>> exactly remember by how much.
>
> If there was a difference, it would likely be on large copies. But it would be hard
> to test without access to a machine...

I managed to get an old Falkor revived, so was able to finally run benchtests.
The new generic memcpy is about 10% faster on bench-memcpy-random test
when sizes fit in L1, and about 5% faster overall. Bench-memcpy-large and -walk
are very similar, so it doesn't seem to have any effect on prefetching in large copies.

So it looks like the new generic memcpy is better overall.

Cheers,
Wilco

  reply	other threads:[~2022-12-21 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 15:14 Wilco Dijkstra
2022-12-09 15:24 ` Siddhesh Poyarekar
2022-12-09 18:00   ` Wilco Dijkstra
2022-12-21 17:27     ` Wilco Dijkstra [this message]
2022-12-21 23:38       ` Siddhesh Poyarekar

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=PAWPR08MB898232B3AA0D061EC6562A3483EB9@PAWPR08MB8982.eurprd08.prod.outlook.com \
    --to=wilco.dijkstra@arm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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 read-only IMAP folder(s) and NNTP newsgroup(s).