From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: libc-alpha@sourceware.org, Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: [PING][PATCH 0/2] aarch64,falkor: memcpy/memmove performance improvements
Date: Thu, 10 May 2018 02:59:00 -0000 [thread overview]
Message-ID: <89b4a63f-75e0-3b10-4320-660b83b9273f@gotplt.org> (raw)
In-Reply-To: <20180503175209.2943-1-siddhesh@sourceware.org>
Ping!
On 05/03/2018 11:22 PM, Siddhesh Poyarekar wrote:
> Hi,
>
> Here are a couple of patches to improve performance of the falkor memcpy
> and memmove implementations based on testing on the latest hardware.
> The theme of the optimization is to avoid trying to train the hardware
> prefetcher for smaller sizes and in the loop tail since that just
> mis-trains the prefetcher. Instead, use multiple registers to aid
> reordering wherever possible. Testing showed that regressions in these
> sizes compared to generic memcpy are resolved with this patch.
>
> Siddhesh
>
> Siddhesh Poyarekar (2):
> aarch64,falkor: Ignore prefetcher hints for memmove tail
> Ignore prefetcher tagging for smaller copies
>
> sysdeps/aarch64/multiarch/memcpy_falkor.S | 68 ++++++++++++++++++------------
> sysdeps/aarch64/multiarch/memmove_falkor.S | 48 ++++++++++++---------
> 2 files changed, 70 insertions(+), 46 deletions(-)
>
prev parent reply other threads:[~2018-05-10 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 17:52 [PATCH " Siddhesh Poyarekar
2018-05-03 17:52 ` [PATCH 2/2] Ignore prefetcher tagging for smaller copies Siddhesh Poyarekar
2018-05-10 10:29 ` Szabolcs Nagy
2018-05-03 17:52 ` [PATCH 1/2] aarch64,falkor: Ignore prefetcher hints for memmove tail Siddhesh Poyarekar
2018-05-10 10:29 ` Szabolcs Nagy
2018-05-10 2:59 ` Siddhesh Poyarekar [this message]
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=89b4a63f-75e0-3b10-4320-660b83b9273f@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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).