Long pause when using pcrypt

Long pause when using pcrypt

[Nils Rennebarth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

As parallel encryption of ipsec is now in the official kernel, I tried to use
it, and to actually make ipsec connections use it, I did

  $ modprobe tcrypt alg='pcrypt(authenc(hmac(sha1),cbc(aes)))' type=3

This works, but the computer pauses for about 60s when running the modprobe,
and appears to be completely idle in the meantime. Why is that necessary?

Is there another recommended way to instantiate pcrypt, e.g. via netlink?
I searched for a while, by browsing the sources, but found nothing appropriate.

- --
                                     ______
                                    (Muuuhh)
Global Village Sau  ==>        ^..^ |/¯¯¯¯¯
(Kann Fremdsprache) ==>        (oo)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvQD3QACgkQqgAZ+sZlgs43DgCg43ehtSAai1A+v8c2vuIuuIxO
dloAn0TeB/Ur+b/mUI6dUhA1UCZpGCmp
=SLiY
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Long pause when using pcrypt

[Steffen Klassert]

On Thu, Apr 22, 2010 at 10:57:24AM +0200, Nils Rennebarth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> As parallel encryption of ipsec is now in the official kernel, I tried to use
> it, and to actually make ipsec connections use it, I did
> 
>   $ modprobe tcrypt alg='pcrypt(authenc(hmac(sha1),cbc(aes)))' type=3
> 
> This works, but the computer pauses for about 60s when running the modprobe,
> and appears to be completely idle in the meantime. Why is that necessary?

You can try to specify the drivers e.g.

modprobe tcrypt alg="pcrypt(authenc(hmac(sha1-generic),cbc(aes-asm)))" type=3

this should be faster.

> 
> Is there another recommended way to instantiate pcrypt, e.g. via netlink?
> I searched for a while, by browsing the sources, but found nothing appropriate.
> 

Unfortunately not yet, this should change as soon as we have a generic crypto user
configuration interface.

Steffen