Return-path: Received: from helcar.hengli.com.au ([209.40.204.226]:54332 "EHLO helcar.hengli.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754579AbcJSDcP (ORCPT ); Tue, 18 Oct 2016 23:32:15 -0400 Date: Wed, 19 Oct 2016 11:31:57 +0800 From: Herbert Xu To: Ard Biesheuvel Cc: Andy Lutomirski , Johannes Berg , Sergey Senozhatsky , "" , "David S. Miller" , "" , "linux-kernel@vger.kernel.org" , Jouni Malinen Subject: Re: [PATCH] crypto: ccm - avoid scatterlist for MAC encryption Message-ID: <20161019033157.GA1457@gondor.apana.org.au> (sfid-20161019_053223_380457_744A085D) References: <1476551776-8099-1-git-send-email-ard.biesheuvel@linaro.org> <1476689310.19992.1.camel@sipsolutions.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Oct 17, 2016 at 06:21:14PM +0100, Ard Biesheuvel wrote: > > Annoyingly, all this complication with scatterlists etc is for doing > asynchronous crypto via DMA capable crypto accelerators, and the > networking code (ipsec as well as mac80211, afaik) only allow > synchronous in the first place, given that they execute in softirq > context. I'm still thinking about the issue (in particular, whether we should continue to rely on the request context being SG-capable or allow it to be on the stack for AEAD). But IPsec definitely supports async crypto. In fact it was the very first user of async crypto. mac80211 on the other hand is currently sync-only. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt