From: "Loc Ho" <locnho@sbcglobal.net>
To: <linux-crypto@vger.kernel.org>
Subject: New Crypto Hardware
Date: Mon, 12 Nov 2007 10:19:49 -0800 [thread overview]
Message-ID: <007c01c82558$9d175180$2005420a@amcc.com> (raw)
In-Reply-To:
Hi,
I am about to start developing a new device driver for new crypto hardware.
I am thinking of starting with Linux CryptoAPI interface. But I have the
following requirement:
1. Asynchronous encrypt/decrypt
2. Asynchronous hashing
3. Asynchronous combined mode (GCM, CCM, and GMAC) 4.
Asynchronous/synchronous public key accelaration (large vector operation) 5.
Support for additional algorithms - ARC4, Kasumi, AES-XCBC and etc 6. Other
minor offload such as windows check and etc. In fact, it can do packet level
processing as well.
What is the current state of asynchronous hashing? Will AEAD be changed to
make use of asynchronous hashing? Is anyone working on #1 and changing AEAD
to asychronous interface? In addition, most of the existent device driver
only use synchronous interface. Are there any one changing them to
asynchronous crypto interface - such as NETKEY (Linux IPSec)?
Thanks,
Loc
next parent reply other threads:[~2007-11-12 18:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0CA0A16855646F4FA96D25A158E299D603B5A5EB@SDCEXCHANGE01.ad.amcc.com>
2007-11-12 18:19 ` Loc Ho [this message]
2007-11-13 1:41 ` New Crypto Hardware Herbert Xu
[not found] ` <0CA0A16855646F4FA96D25A158E299D603EB866F@SDCEXCHANGE01.ad.amcc.com>
2007-12-25 7:32 ` Herbert Xu
[not found] ` <0CA0A16855646F4FA96D25A158E299D603FCC15D@SDCEXCHANGE01.ad.amcc.com>
2008-01-17 11:23 ` Herbert Xu
2008-01-17 18:37 ` Loc Ho
2008-01-17 20:27 ` Sebastian Siewior
[not found] ` <0CA0A16855646F4FA96D25A158E299D603FCC4D7@SDCEXCHANGE01.ad.amcc.com>
2008-01-18 23:07 ` Sebastian Siewior
2008-01-22 1:29 ` Loc Ho
2008-01-22 23:18 ` Sebastian Siewior
2008-01-23 2:17 ` Loc Ho
2008-01-24 21:07 ` RFC: Async Hash Support Loc Ho
2008-01-24 23:09 ` Sebastian Siewior
2008-01-25 2:45 ` [PATCH 1/1] CryptoAPI: Add " Loc Ho
2008-03-13 11:42 ` Herbert Xu
2008-03-13 17:39 ` Loc Ho
2008-04-10 2:03 ` Loc Ho
2008-04-10 2:29 ` Herbert Xu
2008-04-22 11:16 ` Herbert Xu
2008-04-22 17:23 ` Loc Ho
2008-05-07 13:00 ` Herbert Xu
2008-05-07 13:09 ` Patrick McHardy
2008-05-07 13:15 ` Herbert Xu
2008-05-13 20:27 ` [PATCH 1/3] [CRYPTO] hash: " Loc Ho
2008-05-14 12:40 ` Herbert Xu
2008-05-14 12:44 ` Herbert Xu
2008-05-14 13:26 ` Herbert Xu
2008-05-13 20:29 ` [PATCH 2/3] [CRYPTO] cryptd: " Loc Ho
2008-05-13 20:30 ` [PATCH 3/3] [CRYPTO] tcrypt: " Loc Ho
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='007c01c82558$9d175180$2005420a@amcc.com' \
--to=locnho@sbcglobal.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.