Resending to linux-crypto in plain text. Sorry to everyone else for the duplication. mh On Fri, Feb 20, 2015 at 1:23 PM, Martin Hicks <mort@xxxxxxxx> wrote: > > I've just noticed that performance is pretty terrible with maxcpus=1, so > I'll investigate that. > mh > > On Fri, Feb 20, 2015 at 11:21 AM, Martin Hicks <mort@xxxxxxxx> wrote: >> >> I was testing dm-crypt performance with a Freescale P1022 board with >> a recent kernel and was getting IO errors while doing testing with LUKS. >> Investigation showed that all hardware FIFO slots were filling and >> the driver was returning EAGAIN to the block layer, which is not an >> expected response for an async crypto implementation. >> >> The following patch series adds a few small fixes, and reworks the >> submission path to use the crypto_queue mechanism to handle the >> request backlog. >> >> >> Martin Hicks (5): >> crypto: talitos: Simplify per-channel initialization >> crypto: talitos: Remove MD5_BLOCK_SIZE >> crypto: talitos: Fix off-by-one and use all hardware slots >> crypto: talitos: Reorganize request submission data structures >> crypto: talitos: Add software backlog queue handling >> >> drivers/crypto/talitos.c | 189 >> ++++++++++++++++++++++++---------------------- >> drivers/crypto/talitos.h | 44 +++++++++-- >> 2 files changed, 137 insertions(+), 96 deletions(-) >> >> -- >> 1.7.10.4 >> > > > > -- > Martin Hicks P.Eng. | mort@xxxxxxxx > Bork Consulting Inc. | +1 (613) 266-2296 -- Martin Hicks P.Eng. | mort@xxxxxxxx Bork Consulting Inc. | +1 (613) 266-2296 -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
