[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712205DFB9511@ORSMSX106.amr.corp.intel.com>
Date: Thu, 26 May 2016 21:25:14 +0000
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: "Dey, Megha" <megha.dey@...el.com>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>
CC: "tim.c.chen@...ux.intel.com" <tim.c.chen@...ux.intel.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Megha Dey <megha.dey@...ux.intel.com>
Subject: RE: [PATCH 2/7] crypto : async implementation for sha1-mb
> From: Dey, Megha
> Sent: Thursday, May 19, 2016 5:43 PM
> To: herbert@...dor.apana.org.au
> Cc: tim.c.chen@...ux.intel.com; davem@...emloft.net; linux-
> crypto@...r.kernel.org; linux-kernel@...r.kernel.org; Dey, Megha
> <megha.dey@...el.com>; Yu, Fenghua <fenghua.yu@...el.com>; Megha
> Dey <megha.dey@...ux.intel.com>
> Subject: [PATCH 2/7] crypto : async implementation for sha1-mb
>
> From: Megha Dey <megha.dey@...ux.intel.com>
>
> Herbert wants the sha1-mb algorithm to have an async implementation:
> https://lkml.org/lkml/2016/4/5/286.
> Currently, sha1-mb uses an async interface for the outer algorithm and a sync
> interface for the inner algorithm. This patch introduces a async interface for
> even the inner algorithm.
>
> Signed-off-by: Megha Dey <megha.dey@...ux.intel.com>
> Signed-off-by: Tim Chen <tim.c.chen@...ux.intel.com>
> ---
> arch/x86/crypto/sha-mb/sha1_mb.c | 190 ++++++++++++++++++++++------
> -----------
> crypto/ahash.c | 6 --
> crypto/mcryptd.c | 117 +++++++++++++-----------
> include/crypto/hash.h | 6 ++
> include/crypto/internal/hash.h | 8 +-
> include/crypto/mcryptd.h | 8 +-
> 6 files changed, 184 insertions(+), 151 deletions(-)
>
Hi, Herbert,
Any comment/feedback on this patch set? Is there any plan to push it to upstream?
Thanks.
-Fenghua
Powered by blists - more mailing lists