Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnacek@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ondrej Mosnacek <omosnacek@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
	Jeffrey Walton <noloader@gmail.com>,
	Milan Broz <gmazyland@gmail.com>
Subject: [PATCH v5 0/4] gf128mul refactoring
Date: Sun,  2 Apr 2017 21:19:12 +0200	[thread overview]
Message-ID: <20170402191916.9309-1-omosnacek@gmail.com> (raw)

This patchset contains the following gf128mul-related changes:
  1. The gf128mul_x_* functions are moved to gf128mul.h for performance reasons.
  2. The gf128mul_x_ble function is fixed to use the correct block type.
  3. The le128_gf128mul_x_ble function from glue_helper.h is removed and its
     usages replaced with gf128mul_x_ble calls.
  4. The now obsolete dependency of CRYPTO_XTS on CRYPTO_GF128MUL is removed.

v4 -> v5: added the other three patches
v3 -> v4: a faster version of gf128mul_x_lle
v2 -> v3: constant-time implementation
v1 -> v2: move all _x_ functions to the header, not just gf128mul_x_ble

Ondrej Mosnacek (4):
  crypto: gf128mul - define gf128mul_x_* in gf128mul.h
  crypto: gf128mul - switch gf128mul_x_ble to le128
  crypto: glue_helper - remove the le128_gf128mul_x_ble function
  crypto: xts - drop gf128mul dependency

 arch/x86/crypto/camellia_glue.c           |  4 +--
 arch/x86/crypto/glue_helper.c             |  3 +-
 arch/x86/crypto/serpent_sse2_glue.c       |  4 +--
 arch/x86/crypto/twofish_glue_3way.c       |  4 +--
 arch/x86/include/asm/crypto/glue_helper.h | 10 ------
 crypto/Kconfig                            |  1 -
 crypto/gf128mul.c                         | 33 +------------------
 crypto/xts.c                              | 38 ++++++++++-----------
 include/crypto/gf128mul.h                 | 55 +++++++++++++++++++++++++++++--
 include/crypto/xts.h                      |  2 +-
 10 files changed, 82 insertions(+), 72 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-04-02 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02 19:19 Ondrej Mosnacek [this message]
2017-04-02 19:19 ` [PATCH v5 1/4] crypto: gf128mul - define gf128mul_x_* in gf128mul.h Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 2/4] crypto: gf128mul - switch gf128mul_x_ble to le128 Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 3/4] crypto: glue_helper - remove the le128_gf128mul_x_ble function Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 4/4] crypto: xts - drop gf128mul dependency Ondrej Mosnacek
2017-04-05  4:13 ` [PATCH v5 0/4] gf128mul refactoring Eric Biggers
2017-04-05 14:11 ` 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=20170402191916.9309-1-omosnacek@gmail.com \
    --to=omosnacek@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=gmazyland@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=noloader@gmail.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