From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>, Andrew Pinski <pinskia@gmail.com>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
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 09:34:00 -0000 [thread overview]
Message-ID: <1f45b057-6d17-0c03-fe40-1232c43e7f14@gotplt.org> (raw)
In-Reply-To: <7b84a831-233f-e2a7-c89c-efbf438ae9e5@redhat.com>
On Thursday 10 November 2016 02:59 PM, Florian Weimer wrote:
> Another option would be to get the complete implementation of memcmp
> etc. fom the vDSO, I think.
Hmm, that is an interesting thought.
> In the ARM context, there were also suggestions that we should support
> big/little asymmetric multi-processing. I hope we don't have to do
> this. It would seriously limit IFUNC selection and other
> microarchitecture-based optimizations.
Even if we don't actually have optimal routines for big.LITTLE, we still
have to account for the possibility of their existence, hence the need
to peek into all online processors in the hope (because some could be
offline, giving an incorrect view of the system) of guessing the correct
execution environment.
Siddhesh
next prev parent reply other threads:[~2016-11-10 9:34 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
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 [this message]
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=1f45b057-6d17-0c03-fe40-1232c43e7f14@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--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).