From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>,
Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org, Yauhen Kharuzhy <jekhor@gmail.com>
Subject: Re: crypto: aesni - add ccm(aes) algorithm implementation
Date: Sat, 22 Oct 2016 22:31:40 +0200 [thread overview]
Message-ID: <1477168300.4123.8.camel@sipsolutions.net> (raw)
In-Reply-To: <4298972.T1UOBYP9Tx@debian64> (sfid-20161022_211600_609367_51AA87DC)
On Sat, 2016-10-22 at 21:15 +0200, Christian Lamparter wrote:
>
> It would be a great if mac80211 would do to the encryption and
> decryption asynchronously. As this would work for other ciphers
> and also allows crypto offload to dedicated crypto hardware.
The only problem with that is that we'd essentially need a software
queue for *all* frames, and release them from there in RX order after
decrypt. That's surely doable, but so far nobody has thought it
important enough since mostly HW crypto is used ...
johannes
next prev parent reply other threads:[~2016-10-22 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 16:37 crypto: aesni - add ccm(aes) algorithm implementation greearb
2016-10-19 16:39 ` Ben Greear
2016-10-22 19:15 ` Christian Lamparter
2016-10-22 20:31 ` Johannes Berg [this message]
2016-10-23 2:33 ` Ben Greear
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=1477168300.4123.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=greearb@candelatech.com \
--cc=jekhor@gmail.com \
--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).