From: Steffen Klassert Subject: Re: [RFC] [PATCH 2/4] cpu_chainiv: add percpu IV chain genarator Date: Wed, 8 Apr 2009 13:40:14 +0200 Message-ID: <20090408114014.GL6791@secunet.com> References: <20090316114940.GN13998@secunet.com> <20090316115251.GP13998@secunet.com> <20090327083615.GB27903@gondor.apana.org.au> <20090330115415.GC6791@secunet.com> <20090330131955.GA22604@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Miller , linux-crypto@vger.kernel.org To: Herbert Xu Return-path: Received: from a.mx.secunet.com ([213.68.205.161]:34159 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764877AbZDHLiT (ORCPT ); Wed, 8 Apr 2009 07:38:19 -0400 Content-Disposition: inline In-Reply-To: <20090330131955.GA22604@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Mon, Mar 30, 2009 at 09:19:55PM +0800, Herbert Xu wrote: > > How about using eseqiv? It's designed for exactly this situation > where you want parallel async processing. Its overhead is just > one extra encryption block. > Actually I'm instantiate a crypto_nivaead_type algorithm and choose for cpu_chainiv as the IV generator for that algorithm. If I want to do the same with eseqiv it would require to add aead support to eseqiv. Is this what you are thinking about, or is there a way to instantiate a crypto_aead_type algorithm and notify the ablkcipher to choose for eseqiv as it's default IV genarator? Steffen