From: Eric Biggers <ebiggers3@gmail.com>
To: Ondrej Mosnacek <omosnacek@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"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: Re: [PATCH v5 0/4] gf128mul refactoring
Date: Tue, 4 Apr 2017 21:13:51 -0700 [thread overview]
Message-ID: <20170405041351.GA4761@zzz> (raw)
In-Reply-To: <20170402191916.9309-1-omosnacek@gmail.com>
Hi Ondrej,
On Sun, Apr 02, 2017 at 09:19:12PM +0200, Ondrej Mosnacek wrote:
> 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
These all look good to me, and you can add
Reviewed-by: Eric Biggers <ebiggers@google.com>
to the patches.
I think the change to le128 is an improvement, but what I've actually wanted to
do is have the GF(2^128) elements strongly typed, with ble128, bbe128, and
lle128 types, so that the types would reflect both the bit order and the byte
order. But that's harder to do and I ran into some issues when I tried it last.
- Eric
next prev parent reply other threads:[~2017-04-05 4:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 19:19 [PATCH v5 0/4] gf128mul refactoring Ondrej Mosnacek
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 ` Eric Biggers [this message]
2017-04-05 14:11 ` [PATCH v5 0/4] gf128mul refactoring 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=20170405041351.GA4761@zzz \
--to=ebiggers3@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 \
--cc=omosnacek@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