From: Patrick Alken <alken@colorado.edu>
To: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: Reduce cache misses for source_gemm_r
Date: Fri, 19 Oct 2018 08:18:00 -0000 [thread overview]
Message-ID: <bb265183-5575-5d33-0ded-4816b57a56db@colorado.edu> (raw)
In-Reply-To: <CABb0SYR+gNfaui-M6aWg8Ed6cQ8=N8YyBYP+LQgS1VXWG1H-Kg@mail.gmail.com>
Thanks Max, this is fine. I will take a look at your patch as soon as I can.
On 10/19/2018 05:10 AM, Max Bruce wrote:
> Hey guys,
>
> I'm new to contributing to GNU projects, but... I'm guessing I send
> commits through here? Would appreciate some sort of note on the
> procedure on the website
>
> I noticed that your matrix multiplication code had bad cache
> performance due to a misordering of a loop. In a replicated version of
> my change, I saw about 20% performance gains on my AMD FX CPU.
>
> Do let me know if this is not the correct contribution procedure.
>
> -Max
prev parent reply other threads:[~2018-10-19 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 3:10 Max Bruce
2018-10-19 8:18 ` Patrick Alken [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=bb265183-5575-5d33-0ded-4816b57a56db@colorado.edu \
--to=alken@colorado.edu \
--cc=gsl-discuss@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).