From: Pavel Roskin <proski@gnu.org>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Using asynchonous block cipher for CCMP
Date: Sat, 27 Feb 2010 00:44:34 -0500 [thread overview]
Message-ID: <1267249474.6278.23.camel@mj> (raw)
Hello!
I'm looking for ways to accelerate CCMP on Intel IXP425.
drivers/crypto/ixp4xx_crypto.c implements only asynchronous block
ciphers, and the reason appears to be that the crypto processor uses DMA
and interrupts to communicate with the CPU, which would make synchronous
encryption ineffective.
It turns out that mac80211 uses plain AES for CCMP. However, it uses an
asynchronous block cipher "ecb(arc4)" for WEP and TKIP.
I'd like to make CCMP use an asynchronous block cipher. Has anyone
attempted that? Are there any issues I should be aware of?
--
Regards,
Pavel Roskin
next reply other threads:[~2010-02-27 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 5:44 Pavel Roskin [this message]
2010-02-27 7:03 ` Using asynchonous block cipher for CCMP Johannes Berg
2010-02-27 22:14 ` Pavel Roskin
2010-03-08 7:57 ` Johannes Berg
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=1267249474.6278.23.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).