From: "H.J. Lu" <hjl.tools@gmail.com>
To: Erich Elsen <eriche@google.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: memcpy performance regressions 2.19 -> 2.24(5)
Date: Tue, 23 May 2017 02:25:00 -0000 [thread overview]
Message-ID: <CAMe9rOowieroCST=wq81Co+OHud81jyjJZ8OZpqQCmEnnoPZfQ@mail.gmail.com> (raw)
In-Reply-To: <CAOVZoAOWzf0U7T-1Gbf7YUOfz4+X4frE+y1OHbSuQ-_Ta1uX2w@mail.gmail.com>
On Mon, May 22, 2017 at 6:23 PM, Erich Elsen <eriche@google.com> wrote:
> I definitely think increasing the size in the case of processors with
> a large number of cores makes sense. Hopefully with some testing we
> can confirm it is a net win and/or find a more empirical number.
>
> Thanks for that patch with the tunable support. I've just put a
> similar patch in review for sharing right now. It adds support in the
> case that HAVE_TUNABLES isn't defined like the similar code in arena.c
> and also makes a minor change that turns init_cacheinfo into a
> init_cacheinfo_impl (a hidden callable). init_cacheinfo is now a
> constructor that just calls the impl and passes the cpu_features
> struct. This is useful in that it makes the code a bit more modular
> (something that we'll need to be able to test this internally).
This sounds a good idea. I'd also like to add tunable support in
init_cpu_features to turn on/off CPU features. non_temporal_threshold
will be one of them.
--
H.J.
next prev parent reply other threads:[~2017-05-23 2:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 17:09 Erich Elsen
2017-05-05 18:09 ` Carlos O'Donell
2017-05-06 0:57 ` Erich Elsen
2017-05-06 15:41 ` H.J. Lu
2017-05-09 23:48 ` Erich Elsen
2017-05-10 17:33 ` H.J. Lu
2017-05-11 2:17 ` Carlos O'Donell
2017-05-12 19:47 ` Erich Elsen
[not found] ` <CAOVZoAPp3_T+ourRkNFXHfCSQUOMFn4iBBm9j50==h=VJcGSzw@mail.gmail.com>
2017-05-12 20:21 ` H.J. Lu
2017-05-12 21:21 ` H.J. Lu
2017-05-18 20:59 ` Erich Elsen
2017-05-22 19:17 ` H.J. Lu
2017-05-22 20:22 ` H.J. Lu
2017-05-23 1:23 ` Erich Elsen
2017-05-23 2:25 ` H.J. Lu [this message]
2017-05-23 3:19 ` Erich Elsen
2017-05-23 20:39 ` Erich Elsen
2017-05-23 20:46 ` H.J. Lu
2017-05-23 20:57 ` Erich Elsen
2017-05-23 22:08 ` H.J. Lu
2017-05-23 22:12 ` Erich Elsen
2017-05-23 22:55 ` H.J. Lu
2017-05-24 0:56 ` Erich Elsen
2017-05-24 3:42 ` H.J. Lu
2017-05-24 21:03 ` Erich Elsen
2017-05-24 21:36 ` H.J. Lu
2017-05-25 21:23 ` Erich Elsen
2017-05-25 21:57 ` Erich Elsen
2017-05-25 22:03 ` H.J. Lu
2017-05-27 0:31 ` Erich Elsen
2017-05-27 21:35 ` H.J. Lu
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='CAMe9rOowieroCST=wq81Co+OHud81jyjJZ8OZpqQCmEnnoPZfQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=carlos@redhat.com \
--cc=eriche@google.com \
--cc=libc-alpha@sourceware.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).