From: Kim Phillips <kim.phillips@freescale.com>
To: <lee.nipper@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH][RFC] crypto: talitos - add hmac algorithms
Date: Thu, 29 Apr 2010 22:13:29 -0500 [thread overview]
Message-ID: <20100429221329.b386cecb.kim.phillips@freescale.com> (raw)
In-Reply-To: <4bd82b35.064c640a.62c0.4de1@mx.google.com>
On Wed, 28 Apr 2010 05:33:57 -0700
<lee.nipper@gmail.com> wrote:
> Add the these hmac algorithms to talitos:
> hmac(md5),
> hmac(sha1),
> hmac(sha256),
> hmac(sha384),
> hmac(sha512).
> These are all type ahash.
>
> Signed-off-by: Lee Nipper <lee.nipper@gmail.com>
> ---
> Currently on an 8349E, there's a problem with hmac for
> any talitos hmac sequence requiring an
> intermediate hash context (Pointer DWORD 1);
> the result is an incorrect hmac.
> An intermediate hash context is required for
> something longer than (65536-blocksize), and for other
> cases when update/finup/final are used inefficiently.
> Interestingly, a normal hash (without hmac) works perfectly
> when using an intermediate context.
> So, I solicit any hints/help for figuring this out,
> since this hmac patch is a bust without this being corrected.
I set up an IPsec AH transport mode tunnel between a sec3.0 (8572)
doing crypto in h/w and another in s/w. When trying to tx a single 64
byte ICMP packet from s/w crypto host to h/w crypto host, I get 2728
(!) talitos IRQs all at once:
[root@hagrid ~]# grep tali /proc/interrupts
45: 161575 0 OpenPIC Level talitos
[root@hagrid ~]# grep tali /proc/interrupts
45: 164303 0 OpenPIC Level talitos
and no ICMP reply...will have to investigate this further.
Kim
prev parent reply other threads:[~2010-05-01 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 12:33 [PATCH][RFC] crypto: talitos - add hmac algorithms lee.nipper
2010-04-28 21:44 ` Lee Nipper
2010-04-30 3:13 ` Kim Phillips [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=20100429221329.b386cecb.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=lee.nipper@gmail.com \
--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