From: Ard Biesheuvel <ardb@kernel.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Help getting aesni crypto patch upstream
Date: Wed, 29 Jul 2020 09:06:53 +0300 [thread overview]
Message-ID: <CAMj1kXFwPPDfm1hvW+LgnfuPO-wfguTZ0NcLyeyesGeBcuDKGQ@mail.gmail.com> (raw)
In-Reply-To: <2a55b661-512b-9479-9fff-0f2e2a581765@candelatech.com>
On Wed, 29 Jul 2020 at 01:03, Ben Greear <greearb@candelatech.com> wrote:
>
> Hello,
>
> As part of my wifi test tool, I need to do decrypt AES on the CPU, and the only way this
> performs well is to use aesni. I've been using a patch for years that does this, but
> recently somewhere between 5.4 and 5.7, the API I've been using has been removed.
>
> Would anyone be interested in getting this support upstream? I'd be happy to pay for
> the effort.
>
> Here is the patch in question:
>
> https://github.com/greearb/linux-ct-5.7/blob/master/wip/0001-crypto-aesni-add-ccm-aes-algorithm-implementation.patch
>
> Please keep me in CC, I'm not subscribed to this list.
>
Hi Ben,
Recently, the x86 FPU handling was improved to remove the overhead of
preserving/restoring of the register state, so the issue that this
patch fixes may no longer exist. Did you try?
In any case, according to the commit log on that patch, the problem is
in the MAC generation, so it might be better to add a cbcmac(aes)
implementation only, and not duplicate all the CCM boilerplate.
next prev parent reply other threads:[~2020-07-29 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 22:03 Help getting aesni crypto patch upstream Ben Greear
2020-07-29 6:06 ` Ard Biesheuvel [this message]
2020-07-29 12:27 ` Ben Greear
2020-07-29 19:09 ` Ard Biesheuvel
2020-07-29 19:29 ` Ben Greear
2020-07-29 20:06 ` Ard Biesheuvel
2020-07-30 22:56 ` Ben Greear
2020-07-31 10:00 ` Ard Biesheuvel
2020-07-31 14:02 ` 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=CAMj1kXFwPPDfm1hvW+LgnfuPO-wfguTZ0NcLyeyesGeBcuDKGQ@mail.gmail.com \
--to=ardb@kernel.org \
--cc=greearb@candelatech.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;
as well as URLs for NNTP newsgroup(s).