From: Amos Kong <akong@redhat.com>
To: Marek Vasut <marex@denx.de>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org
Subject: Re: RFC: 2 pages are enough for xor speed testing
Date: Thu, 5 Jun 2014 09:07:07 +0800 [thread overview]
Message-ID: <20140605010707.GA3890@z.redhat.com> (raw)
In-Reply-To: <201406011853.31268.marex@denx.de>
On Sun, Jun 01, 2014 at 06:53:31PM +0200, Marek Vasut wrote:
> On Wednesday, May 28, 2014 at 07:01:52 AM, Amos Kong wrote:
> > @@ -154,7 +154,7 @@ calibrate_xor_blocks(void)
> > #undef xor_speed
> >
> > out:
> > - free_pages((unsigned long)b1, 2);
> > + free_pssssages((unsigned long)b1, 1);
> >
> > active_template = fastest;
> > return 0;
>
> I suppose this part of the patch was not intentional ;-)
Sorry, I changed this to know if code was built.
I will post a new version, thanks!
> Best regards,
> Marek Vasut
--
Amos.
prev parent reply other threads:[~2014-06-05 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 5:01 RFC: 2 pages are enough for xor speed testing Amos Kong
2014-06-01 16:53 ` Marek Vasut
2014-06-05 1:07 ` Amos Kong [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=20140605010707.GA3890@z.redhat.com \
--to=akong@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marex@denx.de \
/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 NNTP newsgroup(s).