From: Steffen Klassert <steffen.klassert@secunet.com>
To: Ilya Lesokhin <ilyal@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sd@queasysnail.net" <sd@queasysnail.net>,
Boris Pismenny <borisp@mellanox.com>,
"davejwatson@fb.com" <davejwatson@fb.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: Using the aesni generic gcm(aes) aead in atomic context
Date: Wed, 1 Nov 2017 10:21:07 +0100 [thread overview]
Message-ID: <20171101092106.GI11292@secunet.com> (raw)
In-Reply-To: <AM4PR0501MB2723C14143D6FE272BDA58E5D45E0@AM4PR0501MB2723.eurprd05.prod.outlook.com>
On Tue, Oct 31, 2017 at 09:41:24AM +0000, Ilya Lesokhin wrote:
>
> Are you sure supporting ASYNC crypto for fallback is worth the trouble?
It is not just for fallback, I plan to support the IPsec GSO codepath
for software crypto too. In this case we should be able to handle all
algorithms, including the async ones.
> This path is going to be slower that the path were you do the crypto in advance, right?
If the cryptd is used, yes. At least that's what I messured for IPsec
forwarding. But I think this is because we enqueue requests much
faster that the cryptd dequeues them.
prev parent reply other threads:[~2017-11-01 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 15:18 Using the aesni generic gcm(aes) aead in atomic context Ilya Lesokhin
2017-10-31 4:10 ` Herbert Xu
2017-10-31 7:14 ` Ilya Lesokhin
2017-10-31 7:17 ` Herbert Xu
2017-10-31 7:23 ` Ilya Lesokhin
2017-10-31 7:32 ` Herbert Xu
2017-10-31 7:39 ` Ilya Lesokhin
2017-10-31 7:44 ` Herbert Xu
2017-10-31 7:58 ` Ilya Lesokhin
2017-10-31 9:13 ` Steffen Klassert
2017-10-31 9:41 ` Ilya Lesokhin
2017-11-01 9:21 ` Steffen Klassert [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=20171101092106.GI11292@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=herbert@gondor.apana.org.au \
--cc=ilyal@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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.