Re: [RFC PATCH 18/18] net: wireguard - switch to crypto API for packet encryption
From: Andy Lutomirski <luto@kernel.org>
Date: 2019-09-27 04:37:31
Also in:
linux-crypto
From: Andy Lutomirski <luto@kernel.org>
Date: 2019-09-27 04:37:31
Also in:
linux-crypto
On Thu, Sep 26, 2019 at 8:54 PM Herbert Xu [off-list ref] wrote:
On Thu, Sep 26, 2019 at 07:54:03PM -0700, Linus Torvalds wrote:quoted
Side note: almost nobody does this. Almost every single async interface I've ever seen ends up being "only designed for async". And I think the reason is that everybody first does the simply synchronous interfaces, and people start using those, and a lot of people are perfectly happy with them. They are simple, and they work fine for the huge majority of users.The crypto API is not the way it is because of async. In fact, the crypto API started out as sync only and async was essentially bolted on top with minimial changes.
Then what's up with the insistence on using physical addresses for so many of the buffers? --Andy _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel