From: Florian Weimer <fweimer@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [libc/string] State of PAGE_COPY_FWD / PAGE_COPY_THRESHOLD
Date: Thu, 10 Nov 2016 08:25:00 -0000 [thread overview]
Message-ID: <db61e598-d6a8-4938-d930-6ebcb2c803ce@redhat.com> (raw)
In-Reply-To: <CA+=Sn1kZSb2oH+rne0YnT6SB=5=u_y4KvOztqT58xNR21w8nnQ@mail.gmail.com>
On 11/10/2016 09:05 AM, Andrew Pinski wrote:
> Also memcpy/memset is useful to optimize for each micro-arch instead
> of doing this kind of optimization is better in general. I have a
> semi-optimized memcpy for ThunderX (T88, not T81 or T83; still have
> not looked into an optimized version for T83/T81 yet) and have an idea
> how to optimize it for another core but there is no way to handle this
> in glibc because of kernel or glibc infrastructure for arm64.
We do this all the time on x86_64 (and presumably POWER). What's
missing on aarch64?
Thanks,
Florian
next prev parent reply other threads:[~2016-11-10 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 9:28 Maxim Kuvyrkov
2016-11-01 13:59 ` Adhemerval Zanella
2016-11-10 7:39 ` Maxim Kuvyrkov
2016-11-10 7:48 ` Andrew Pinski
2016-11-10 7:52 ` Maxim Kuvyrkov
2016-11-10 8:01 ` Andrew Pinski
2016-11-10 8:05 ` Andrew Pinski
2016-11-10 8:25 ` Florian Weimer [this message]
2016-11-10 8:34 ` Andrew Pinski
2016-11-10 8:55 ` Andrew Pinski
2016-11-10 9:25 ` Siddhesh Poyarekar
2016-11-10 9:29 ` Florian Weimer
2016-11-10 9:34 ` Siddhesh Poyarekar
2016-11-30 11:18 ` Siddhesh Poyarekar
2016-11-10 8:26 ` Florian Weimer
2016-11-10 8:27 ` Florian Weimer
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=db61e598-d6a8-4938-d930-6ebcb2c803ce@redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=pinskia@gmail.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).