From: Herbert Xu <herbert@gondor.apana.org.au>
To: Huang Ying <ying.huang@intel.com>
Cc: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [RFC PATCH crypto 4/4] AES-NI: Add support to Intel AES-NI instructions for x86_64 platform
Date: Mon, 12 Jan 2009 21:43:35 +1100 [thread overview]
Message-ID: <20090112104335.GA4942@gondor.apana.org.au> (raw)
In-Reply-To: <1231743310.5937.107.camel@yhuang-dev.sh.intel.com>
On Mon, Jan 12, 2009 at 02:55:10PM +0800, Huang Ying wrote:
>
> I use a "shell" cbc(aes) algorithm which chooses between
> cryptd(__cbc-aes-aesni) and __cbc-aes-aesni according to context. But
> the struct ablkcipher_request passed in can not be used for cryptd(*).
> This can be resolved by allocating another struct ablkcipher_request for
> cryptd(*) for each incoming struct ablkcipher_request. But is there any
> better solution?
You should include that other ablkcipher_request as part of the
context of your ablkcipher_request.
See for example how aead embeds it.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2009-01-12 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 2:02 Huang Ying
2009-01-09 7:01 ` Herbert Xu
2009-01-09 8:54 ` Huang Ying
2009-01-09 9:18 ` Herbert Xu
2009-01-10 10:08 ` Herbert Xu
2009-01-12 2:30 ` Huang Ying
2009-01-12 3:06 ` Herbert Xu
2009-01-12 6:55 ` Huang Ying
2009-01-12 10:43 ` Herbert Xu [this message]
2009-01-13 2:34 ` Huang Ying
2009-01-13 2:39 ` Herbert Xu
2009-01-13 2:49 ` Huang Ying
2009-01-13 2:53 ` Herbert Xu
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=20090112104335.GA4942@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
--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®