From: Stephan Mueller Subject: Re: [PATCH] crypto: AF_ALG AIO - lock context IV Date: Thu, 01 Feb 2018 11:15:48 +0100 Message-ID: <3443894.2QtSl4gYip@tauon.chronox.de> References: <2118226.LQArbCsRu5@tauon.chronox.de> <1794487.2xX5c1mbjk@tauon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Jonathan Cameron , Harsh Jain , Herbert Xu , Linux Crypto Mailing List , linuxarm@huawei.com To: Gilad Ben-Yossef Return-path: Received: from mail.eperm.de ([89.247.134.16]:59118 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751749AbeBAKPu (ORCPT ); Thu, 1 Feb 2018 05:15:50 -0500 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Donnerstag, 1. Februar 2018, 11:06:30 CET schrieb Gilad Ben-Yossef: Hi Gilad, > 2. Pointing out that the problem solved (and rightfully so) by mutex in > AF_ALG AIO implementation must exists elsewhere as well - for example > IPsec, and is probably solved there too, so if we add the flag as > suggested, it can be used there as well to gain similar benefits to what > Jonathan is suggesting. You are quite right. this patch could speed up things for IPSec and the disk encryption logic too. So I think we should CC also the IPSec folks and the disk crypto folks to review the patch. Ciao Stephan