From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id A79D71A0F0B for ; Sat, 21 Feb 2015 03:21:47 +1100 (AEDT) Received: by mail-ig0-f179.google.com with SMTP id l13so4255827iga.0 for ; Fri, 20 Feb 2015 08:21:45 -0800 (PST) Sender: Martin Hicks From: Martin Hicks To: Kim Phillips , Scott Wood , Kumar Gala Subject: [PATCH 0/5] crypto: talitos: Add crypto async queue handling Date: Fri, 20 Feb 2015 11:21:11 -0500 Message-Id: <1424449276-5288-1-git-send-email-mort@bork.org> Cc: Martin Hicks , linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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