linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yu, Fenghua" <fenghua.yu@intel.com>
To: "Dey, Megha" <megha.dey@intel.com>,
	"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Cc: "tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Megha Dey <megha.dey@linux.intel.com>
Subject: RE: [PATCH 2/7] crypto : async implementation for sha1-mb
Date: Thu, 26 May 2016 21:25:14 +0000	[thread overview]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712205DFB9511@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <1463705008-2183-1-git-send-email-megha.dey@intel.com>

> From: Dey, Megha
> Sent: Thursday, May 19, 2016 5:43 PM
> To: herbert@gondor.apana.org.au
> Cc: tim.c.chen@linux.intel.com; davem@davemloft.net; linux-
> crypto@vger.kernel.org; linux-kernel@vger.kernel.org; Dey, Megha
> <megha.dey@intel.com>; Yu, Fenghua <fenghua.yu@intel.com>; Megha
> Dey <megha.dey@linux.intel.com>
> Subject: [PATCH 2/7] crypto : async implementation for sha1-mb
> 
> From: Megha Dey <megha.dey@linux.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@linux.intel.com>
> Signed-off-by: Tim Chen <tim.c.chen@linux.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

      reply	other threads:[~2016-05-26 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  0:43 [PATCH 2/7] crypto : async implementation for sha1-mb Megha Dey
2016-05-26 21:25 ` Yu, Fenghua [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E5A0FA7E9CA944F9D5414FEC6C712205DFB9511@ORSMSX106.amr.corp.intel.com \
    --to=fenghua.yu@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megha.dey@intel.com \
    --cc=megha.dey@linux.intel.com \
    --cc=tim.c.chen@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).