All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>, linux-crypto@vger.kernel.org
Subject: Re: [RFC] [PATCH 2/4] cpu_chainiv: add percpu IV chain genarator
Date: Wed, 8 Apr 2009 13:40:14 +0200	[thread overview]
Message-ID: <20090408114014.GL6791@secunet.com> (raw)
In-Reply-To: <20090330131955.GA22604@gondor.apana.org.au>

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

  parent reply	other threads:[~2009-04-08 11:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 11:49 [RFC] [PATCH 0/4] Parallel IPsec Steffen Klassert
2009-03-16 11:51 ` [RFC] [PATCH 1/4] padata: generic interface for parallel processing Steffen Klassert
2009-03-16 11:52 ` [RFC] [PATCH 2/4] cpu_chainiv: add percpu IV chain genarator Steffen Klassert
2009-03-27  8:36   ` Herbert Xu
2009-03-30 11:54     ` Steffen Klassert
2009-03-30 13:19       ` Herbert Xu
2009-03-30 14:49         ` Steffen Klassert
2009-04-08 11:40         ` Steffen Klassert [this message]
2009-04-09  3:20           ` Herbert Xu
2009-04-14 13:05             ` Steffen Klassert
2009-03-16 11:54 ` [RFC] [PATCH 3/4] pcrypt: Add pcrypt crypto parallelization engine Steffen Klassert
2009-03-16 11:55 ` [RFC] [PATCH 4/4] esp: add the pcrypt hooks to esp Steffen Klassert
2009-03-27  8:44   ` Herbert Xu
2009-03-30 12:22     ` Steffen Klassert

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=20090408114014.GL6791@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /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.