From: Megha Dey <megha.dey@intel.com>
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,
megha.dey@intel.com, fenghua.yu@intel.com,
Megha Dey <megha.dey@linux.intel.com>
Subject: [PATCH V2 0/2] Implementation of an async interface for sha1-mb
Date: Thu, 2 Jun 2016 19:53:48 -0700 [thread overview]
Message-ID: <1464922430-26976-1-git-send-email-megha.dey@intel.com> (raw)
From: Megha Dey <megha.dey@linux.intel.com>
Currently, sha1-mb uses an async interface for the outer algorithm
and a sync interface for the inner algorithm.
Herbert wants the sha1-mb algorithm to have an async implementation:
https://lkml.org/lkml/2016/4/5/286.
This patch introduces a async interface for even the inner algorithm.
Additionally, there are several checkpatch warnings in the sha1_mb.c file:
'WARNING: line over 80 characters' in the sha1_mb.c file. Also, the
syntax of some multi-line comments are not correct. This patchset fixes
these issues.
changes V1->V2
rename shash_ahash_mcryptd* functions to ahash_mcryptd_*
removed the export_symbols for the shash_ahash_mcryptd_* functions
use ahash_interfaces instead of touching the crypto_ahash_request directly
Megha Dey (2):
crypto: sha1-mb - stylistic cleanup
crypto : async implementation for sha1-mb
arch/x86/crypto/sha-mb/sha1_mb.c | 292 ++++++++++++++++++++++++---------------
crypto/ahash.c | 6 -
crypto/mcryptd.c | 131 +++++++++---------
include/crypto/hash.h | 6 +
include/crypto/internal/hash.h | 16 +--
include/crypto/mcryptd.h | 8 +-
6 files changed, 263 insertions(+), 196 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-03 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 2:53 Megha Dey [this message]
2016-06-03 2:53 ` [PATCH V2 1/2] crypto: sha1-mb - stylistic cleanup Megha Dey
2016-06-07 10:44 ` Herbert Xu
2016-06-03 2:53 ` [PATCH V2 2/2] crypto : async implementation for sha1-mb Megha Dey
2016-06-07 10:35 ` Herbert Xu
2016-06-07 18:10 ` Dey, Megha
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=1464922430-26976-1-git-send-email-megha.dey@intel.com \
--to=megha.dey@intel.com \
--cc=davem@davemloft.net \
--cc=fenghua.yu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).