From: Huang Ying <ying.huang@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: GCM benchmark
Date: Fri, 10 Apr 2009 09:51:28 +0800 [thread overview]
Message-ID: <1239328288.6384.69.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20090409082152.GA4099@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Thu, 2009-04-09 at 16:21 +0800, Herbert Xu wrote:
> On Thu, Apr 09, 2009 at 03:50:21PM +0800, Huang Ying wrote:
> > Hi, Herbert,
> >
> > I am working on GCM acceleration with Intel new PCLMULQDQ instructions
> > now. Can you tell me how to do GCM benchmark?
>
> We need to add the infrastructure for testing AEAD speed. It can
> be modelled after the cipher/hash speed testing code.
One issue here is that blkcipher testing infrastructure uses
local_bh_disable()/local_irq_disable() to get more accurate result. But
AEAD uses asynchronous interface, something like
wait_for_completion_interruptable() will be used in test path. How to
get more accurate result for testing asynchronous interface? Maybe it
can be: test many times, select the one with best performance. What's
your opinion?
> > BTW: Similar with AES-NI support, I use cryptd to defer requests in soft
> > IRQ context. Now, cryptd uses crypto_hash instead of crypto_shash as
> > child. I think we should change that. If you have not done that, I will
> > do that.
>
> We need to complete the conversion of all hash algorithms to shash
> first.
Yes.
Best Regards,
Huang Ying
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
parent reply other threads:[~2009-04-10 1:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090409082152.GA4099@gondor.apana.org.au>]
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=1239328288.6384.69.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).