From: Jamie Iles <jamie.iles@picochip.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: IPSec AH hardware offload
Date: Wed, 28 Jan 2009 08:36:19 +0000 [thread overview]
Message-ID: <49801903.2000303@picochip.com> (raw)
In-Reply-To: <20090128033736.GA5888@gondor.apana.org.au>
Herbert Xu wrote:
> Once that's completed we can then convert IPsec (or rather, authenc)
> over to using ahash.
Does that include the hash for authentication header in
net/ipv[46]/ah[46].c?
The driver implements authenc algorithms, so we'll already get
asynchronous operation for ESP, but the crypto_alloc_hash() in ah[46].c
explicitly requests a synchronous hash. Is this worth converting to use
ahash?
Thanks,
Jamie
next prev parent reply other threads:[~2009-01-28 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 14:14 IPSec AH hardware offload Jamie Iles
2009-01-28 3:37 ` Herbert Xu
2009-01-28 8:36 ` Jamie Iles [this message]
2009-01-28 10:41 ` 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=49801903.2000303@picochip.com \
--to=jamie.iles@picochip.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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