Re: [PATCH v2.1 4/7] crypto: GnuPG based MPI lib - additional sources (part 4)

On Mon, 17 Oct 2011, Kasatkin, Dmitry wrote: It is there for completeness and it will not be even compiled at all without CONFIG_MPILIB_EXTRA Still remove? Yes, please. -- James Morris jmor...@namei.org -- To unsubscribe from this list: send the line unsubscribe linux-crypto in the body

Re: [PATCH] talitos: handle descriptor not found in error path

Kim Phillips kim.phill...@freescale.com wrote: The CDPR (Current Descriptor Pointer Register) can be unreliable when trying to locate an offending descriptor. Handle that case by (a) not OOPSing, and (b) reverting to the machine internal copy of the descriptor header in order to report the

[PATCH 00/18] crypto: Add helper functions for parallelized LRW and XTS modes

This series adds lrw_crypt() and xts_crypt() functions for cipher implementations that can benefit from parallel cipher block operations. To make interface flexible, caller is reponsible of allocating buffer large enough to store temporary cipher blocks. This buffer size should be as large as

[PATCH 02/18] crypto: lrw: use blocksize constant

LRW has fixed blocksize of 16. Define LRW_BLOCK_SIZE and use in place of crypto_cipher_blocksize(). Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/lrw.c |8 +--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/crypto/lrw.c b/crypto/lrw.c index

[PATCH 03/18] crypto: lrw: split gf128mul table initialization from setkey

Split gf128mul initialization from setkey so that it can be used outside lrw-module. Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/lrw.c | 61 ++ 1 files changed, 40 insertions(+), 21 deletions(-) diff --git

[PATCH 04/18] crypto: lrw: add interface for parallelized cipher implementions

Export gf128mul table initialization routines and add lrw_crypt() function that can be used by cipher implementations that can benefit from parallelized cipher operations. Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/lrw.c | 105

[PATCH 05/18] crypto: testmgr: add lrw(serpent) test vectors

Add test vectors for lrw(serpent). These are generated from lrw(aes) test vectors. Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/testmgr.c | 15 ++ crypto/testmgr.h | 502 ++ 2 files changed, 517 insertions(+), 0

[PATCH 06/18] crypto: tcrypt: add lrw(serpent) tests

Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/tcrypt.c |9 + crypto/tcrypt.h |1 + 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c index 5526065..9a9e170 100644 --- a/crypto/tcrypt.c +++ b/crypto/tcrypt.c @@

[PATCH 07/18] crypto: serpent-sse2: add lrw support

Patch adds LRW support for serpent-sse2 by using lrw_crypt(). Patch has been tested with tcrypt and automated filesystem tests. Tcrypt benchmarks results (serpent-sse2/serpent_generic speed ratios): Benchmark results with tcrypt: Intel Celeron T1600 (x86_64) (fam:6, model:15, step:13): size

[PATCH 08/18] crypto: testmgr: add lrw(twofish) test vectors

Add test vectors for lrw(twofish). These are generated from lrw(aes) test vectors. Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/testmgr.c | 15 ++ crypto/testmgr.h | 501 ++ 2 files changed, 516 insertions(+), 0

[PATCH 09/18] crypto: tcrypt: add lrw(twofish) tests

Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/tcrypt.c |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c index 9a9e170..0120383 100644 --- a/crypto/tcrypt.c +++ b/crypto/tcrypt.c @@ -990,6 +990,7 @@ static int

[PATCH 10/18] crypto: twofish-x86_64-3way: add lrw support

Patch adds LRW support for twofish-x86_64-3way by using lrw_crypt(). Patch has been tested with tcrypt and automated filesystem tests. Tcrypt benchmarks results (twofish-3way/twofish-asm speed ratios): Intel Celeron T1600 (fam:6, model:15, step:13): sizelrw-enc lrw-dec 16B 0.99x 1.00x

[PATCH 11/18] crypto: xts: use blocksize constant

XTS has fixed blocksize of 16. Define XTS_BLOCK_SIZE and use in place of crypto_cipher_blocksize(). Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/xts.c |8 +--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/crypto/xts.c b/crypto/xts.c index

[PATCH 13/18] crypto: testmgr: add xts(serpent) test vectors

Add test vectors for xts(serpent). These are generated from xts(aes) test vectors. Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/testmgr.c | 15 + crypto/testmgr.h | 682 ++ 2 files changed, 697 insertions(+), 0

[PATCH 15/18] crypto: serpent-sse2: add xts support

Patch adds XTS support for serpent-sse2 by using xts_crypt(). Patch has been tested with tcrypt and automated filesystem tests. Tcrypt benchmarks results (serpent-sse2/serpent_generic speed ratios): Intel Celeron T1600 (x86_64) (fam:6, model:15, step:13): sizexts-enc xts-dec 16B 0.98x

[PATCH 14/18] crypto: tcrypt: add xts(serpent) tests

Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/tcrypt.c |9 + crypto/tcrypt.h |1 + 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c index 0120383..a664595 100644 --- a/crypto/tcrypt.c +++ b/crypto/tcrypt.c @@

[PATCH 17/18] crypto: tcrypt: add xts(twofish) tests

Signed-off-by: Jussi Kivilinna jussi.kivili...@mbnet.fi --- crypto/tcrypt.c |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c index a664595..7736a9f 100644 --- a/crypto/tcrypt.c +++ b/crypto/tcrypt.c @@ -991,6 +991,7 @@ static int

[PATCH 18/18] crypto: twofish-x86_64-3way: add xts support

Patch adds XTS support for twofish-x86_64-3way by using xts_crypt(). Patch has been tested with tcrypt and automated filesystem tests. Tcrypt benchmarks results (twofish-3way/twofish-asm speed ratios): Intel Celeron T1600 (fam:6, model:15, step:13): sizexts-enc xts-dec 16B 0.98x 1.00x

Hardware acceleration indication in af_alg

I did some experiments with af_alg and noticed that to be really useful, it should indicate whether a certain algorithm is hardware accelerated. I guess this has to be inferred by the priority of the algorithm could be made available via a read-only socket option. Any thoughts on this? I can

Re: [PATCH] talitos: handle descriptor not found in error path

On Tue, 18 Oct 2011 09:36:18 +0200 Herbert Xu herb...@gondor.apana.org.au wrote: Kim Phillips kim.phill...@freescale.com wrote: The CDPR (Current Descriptor Pointer Register) can be unreliable when trying to locate an offending descriptor. Handle that case by (a) not OOPSing, and (b)