From: Peter Zijlstra <peterz@infradead.org>
To: Bruce Merry <bmerry@ska.ac.za>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] perf bench: fix order of arguments to memcpy_alloc_mem
Date: Thu, 15 Jan 2015 09:44:49 +0100 [thread overview]
Message-ID: <20150115084449.GP23965@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAOm-9aqxsiC15Q+VGTB9k37-+VcSTaSZZL3xov7zexf4Pqr8NQ@mail.gmail.com>
On Thu, Jan 15, 2015 at 10:15:34AM +0200, Bruce Merry wrote:
> This was causing the destination instead of the source to be filled.
> As a result, the source was typically all mapped to one zero page,
> and hence very cacheable
Almost right ;-)
Please have a look at Documentation/SubmittingPatches
We require at least a Signed-off-by: tag in order to process patches.
Thanks!
prev parent reply other threads:[~2015-01-15 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 8:15 [PATCH] perf bench: fix order of arguments to memcpy_alloc_mem Bruce Merry
2015-01-15 8:44 ` Peter Zijlstra [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=20150115084449.GP23965@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=bmerry@ska.ac.za \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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