On Fri, Mar 27, 2009 at 04:36:15PM +0800, Herbert Xu wrote:
On Mon, Mar 16, 2009 at 12:52:51PM +0100, Steffen Klassert wrote:
If the crypro requests of a crypto transformation are processed in
parallel, the usual chain IV generator would serialize the crypto
requests again. The percpu IV
On Fri, Mar 27, 2009 at 04:44:57PM +0800, Herbert Xu wrote:
On Mon, Mar 16, 2009 at 12:55:26PM +0100, Steffen Klassert wrote:
@@ -447,7 +448,7 @@ static int esp_init_aead(struct xfrm_state *x)
struct crypto_aead *aead;
int err;
- aead = crypto_alloc_aead(x-aead-alg_name,
On Mon, Mar 30, 2009 at 01:54:15PM +0200, Steffen Klassert wrote:
Well, to do efficient parallel processing we need a percpu IV chain
genarator. pcrypt sends the crypto requests round robin to the cpus
independent of the flow they are belong to, so the flows and the IV
streams are mixing. As
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.
Yes, that's an option too. I'll give it a try.
Thanks!
--
To unsubscribe
