I added some counters (not posted) to the drivers to observe I haven't doneĬomprehensive tests of different data sizes and alignments, so Hung boot, so the changes seem functionally correct. With various errors inserted, all the drivers failed self-tests or Tcrypt: testing decryption speed of sync skcipher cfb(aes) using cfb(aes-aesni)īut I don't see any problems in the source code. Tcrypt: testing encryption speed of sync skcipher cfb(aes) using cfb(aes-aesni) Tcrypt: testing encryption speed of sync skcipher cts(cbc(aes)) using cts(cbc(aes-aesni))

I originally encountered some RCU stalls with tcrypt in aesni: These are not currently limited, so I've included patches for I've included a patch to make them use the same macro name. Using either the SZ_4K macro or a direct reference to 4096 bytes:īlake-2s, chacha, nhpoly1305, poly1305, polyval This series attempts to fix the RCU stalls triggeredīy the x86 crypto drivers discussed following x86 drivers are enforcing a 4 KiB limit today, To: herbert, davem, tim.c.chen, linux-crypto, linux-kernel +Cc: Robert Elliott ` (7 more replies) 0 siblings, 8 replies 126+ messages in threadįrom: Robert Elliott 22:31 UTC ( / raw) 22:31 ` rcu: correct CONFIG_EXT_RCU_CPU_STALL_TIMEOUT descriptions Robert Elliott Crypto: x86 - fix RCU stalls LWN's linux-kernel archive help / color / mirror / Atom feed * crypto: x86 - fix RCU stalls 22:31 Robert Elliott

Ibm imm default ip