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: Thu, 25 May 2017 22:03:00 -0000 [thread overview]
Message-ID: <CAMe9rOpKqUmvm3Jv2+63ukEGxTrQZ4He5mqQxJBEJ-mcZSz=yQ@mail.gmail.com> (raw)
In-Reply-To: <CAOVZoAPiL6_aYEoKKCsTQVHDN4BopOiw6EyBe_8_sOtn1NXoWw@mail.gmail.com>
On Thu, May 25, 2017 at 2:57 PM, Erich Elsen <eriche@google.com> wrote:
> It looks like you already added the non_temporal_threshold as part of
> the cpu_features tunables? Here's a small patch that allows the
No, I didn't. I only added cache info to CPU features.
> cpu_features struct to be passed in. This is useful if you need to be
> able to call init_cacheinfo with cpu_features other than the global
> ones.
I need to see the complete working patch.
>
>
> On Thu, May 25, 2017 at 2:23 PM, Erich Elsen <eriche@google.com> wrote:
>> Ok, will do.
>>
>> On Wed, May 24, 2017 at 2:36 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> On Mon, May 22, 2017 at 8:19 PM, Erich Elsen <eriche@google.com> wrote:
>>>> Here is the patch that slightly refactors how init_cacheinfo is called.
>>>>
>>>
>>> Please take a look at hjl/tunables/master branch. You can add
>>> non_temporal_threshold support on top of it.
>>>
>>>
>>> --
>>> H.J.
--
H.J.
next prev parent reply other threads:[~2017-05-25 22:03 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
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 [this message]
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='CAMe9rOpKqUmvm3Jv2+63ukEGxTrQZ4He5mqQxJBEJ-mcZSz=yQ@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).