From: Eric Biggers <ebiggers3@gmail.com>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S . Miller" <davem@davemloft.net>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Martin Willi <martin@strongswan.org>,
Eric Biggers <ebiggers@google.com>
Subject: [PATCH 3/3] crypto: x86/poly1305 - remove cra_alignmask
Date: Fri, 29 Dec 2017 10:10:26 -0600 [thread overview]
Message-ID: <20171229161026.28102-4-ebiggers3@gmail.com> (raw)
In-Reply-To: <20171229161026.28102-1-ebiggers3@gmail.com>
From: Eric Biggers <ebiggers@google.com>
crypto_poly1305_final() no longer requires a cra_alignmask, and nothing
else in the x86 poly1305-simd implementation does either. So remove the
cra_alignmask so that the crypto API does not have to unnecessarily
align the buffers.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
arch/x86/crypto/poly1305_glue.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/crypto/poly1305_glue.c b/arch/x86/crypto/poly1305_glue.c
index e32142bc071d..f58f89b05a7f 100644
--- a/arch/x86/crypto/poly1305_glue.c
+++ b/arch/x86/crypto/poly1305_glue.c
@@ -171,7 +171,6 @@ static struct shash_alg alg = {
.cra_driver_name = "poly1305-simd",
.cra_priority = 300,
.cra_flags = CRYPTO_ALG_TYPE_SHASH,
- .cra_alignmask = sizeof(u32) - 1,
.cra_blocksize = POLY1305_BLOCK_SIZE,
.cra_module = THIS_MODULE,
},
--
2.15.1
next prev parent reply other threads:[~2017-12-29 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 16:10 [PATCH 0/3] crypto: poly1305 - get rid of cra_alignmask Eric Biggers
2017-12-29 16:10 ` [PATCH 1/3] crypto: poly1305 - use unaligned access macros to output digest Eric Biggers
2017-12-29 16:10 ` [PATCH 2/3] crypto: poly1305 - remove cra_alignmask Eric Biggers
2017-12-29 16:10 ` Eric Biggers [this message]
2018-01-05 11:17 ` [PATCH 0/3] crypto: poly1305 - get rid of cra_alignmask Herbert Xu
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=20171229161026.28102-4-ebiggers3@gmail.com \
--to=ebiggers3@gmail.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=martin@strongswan.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.