From: Sebastian Andrzej Siewior <linux-crypto@ml.breakpoint.cc>
To: Huang Ying <ying.huang@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] crypto: Add fpu template, a wrapper for blkcipher touching FPU
Date: Thu, 5 Mar 2009 12:54:02 +0100 [thread overview]
Message-ID: <20090305115402.GA4101@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <1236219941.24215.38.camel@yhuang-dev.sh.intel.com>
* Huang Ying | 2009-03-05 10:25:41 [+0800]:
>Blkcipher touching FPU need to be enclosed by kernel_fpu_begin() and
>kernel_fpu_end(). If they are invoked in cipher algorithm
>implementation, they will be invoked for each block, so that
>performance will be hurt, because they are "slow" operations. This
>patch implements "fpu" template, which makes these operations to be
>invoked for each request.
>
>Signed-off-by: Huang Ying <ying.huang@intel.com>
>
>---
> crypto/Kconfig | 7 ++
> crypto/Makefile | 1
> crypto/fpu.c | 166 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 174 insertions(+)
>
>--- a/crypto/Kconfig
>+++ b/crypto/Kconfig
>@@ -236,6 +236,13 @@ config CRYPTO_XTS
> key size 256, 384 or 512 bits. This implementation currently
> can't handle a sectorsize which is not a multiple of 16 bytes.
>
>+config CRYPTO_FPU
>+ tristate "FPU wrapper"
>+ select CRYPTO_BLKCIPHER
>+ select CRYPTO_MANAGER
>+ help
>+ FPU: Wrapper for blkcipher touching FPU.
I as an end-user have to clue what this could be about. I suggest you
don't make it visible since the explanation won't be helpfull either :)
>+
> comment "Hash modes"
>
> config CRYPTO_HMAC
Sebastian
next prev parent reply other threads:[~2009-03-05 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 2:25 Huang Ying
2009-03-05 11:54 ` Sebastian Andrzej Siewior [this message]
2009-03-06 1:00 ` Huang Ying
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=20090305115402.GA4101@Chamillionaire.breakpoint.cc \
--to=linux-crypto@ml.breakpoint.cc \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.com \
/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
all inboxes | Powered by JetHome®