From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 4/8] crypto: convert xts_tweak_encdec to use xts_uint128 type
Date: Tue, 16 Oct 2018 14:51:47 +0100 [thread overview]
Message-ID: <20181016135147.GG7995@redhat.com> (raw)
In-Reply-To: <w51efcqyr5v.fsf@maestria.local.igalia.com>
On Tue, Oct 16, 2018 at 03:09:16PM +0200, Alberto Garcia wrote:
> On Tue 16 Oct 2018 12:09:14 PM CEST, Daniel P. Berrangé wrote:
>
> > @@ -110,20 +111,34 @@ void xts_decrypt(const void *datactx,
> > /* encrypt the iv */
> > encfunc(tweakctx, XTS_BLOCK_SIZE, T.b, iv);
> >
> > - for (i = 0; i < lim; i++) {
> > - xts_tweak_encdec(datactx, decfunc, src, dst, T.b);
> > -
> > - src += XTS_BLOCK_SIZE;
> > - dst += XTS_BLOCK_SIZE;
> > + if (QEMU_PTR_IS_ALIGNED(src, sizeof(uint64_t)) &&
> > + QEMU_PTR_IS_ALIGNED(dst, sizeof(uint64_t))) {
> > + xts_uint128 *S = (xts_uint128 *)src;
> > + xts_uint128 *D = (xts_uint128 *)dst;
> > + for (i = 0; i < lim; i++, S++, D++) {
> > + xts_tweak_encdec(datactx, decfunc, S, D, &T);
> > + }
> > + } else {
> > + xts_uint128 S, D;
> > +
> > + for (i = 0; i < lim; i++) {
> > + memcpy(&S, src, XTS_BLOCK_SIZE);
> > + xts_tweak_encdec(datactx, decfunc, &S, &D, &T);
> > + memcpy(dst, &D, XTS_BLOCK_SIZE);
> > + src += XTS_BLOCK_SIZE;
> > + dst += XTS_BLOCK_SIZE;
> > + }
>
> The patch looks good to me, but a couple of comments:
>
> - As far as I can see xts_tweak_encdec() works the same regardless of
> whether src and dst point to the same address or not. As a matter of
> fact both qcrypto_block_decrypt() and qcrypto_block_encrypt() do the
> decryption and encryption in place, and as you can see the
> qcrypto_cipher_*crypt() calls in crypto/block.c pass the same buffer
> as input and output.
>
> So instead of having S and D you should be fine with just one of them.
Yes, I could do that in the 2nd loop.
>
> - I think this is just a matter of style preference, but in the first
> for loop you can remove the comma operator (i++, S++, D++) and use
> S[i] and D[I] instead in the line after that. I'm fine if you prefer
> the current style, though.
The syntax I used results in slightly more efficient asm code.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-10-16 13:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 10:09 [Qemu-devel] [PATCH v2 0/8] crypto: improve performance of XTS cipher mode Daniel P. Berrangé
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 1/8] crypto: expand algorithm coverage for cipher benchmark Daniel P. Berrangé
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 2/8] crypto: remove code duplication in tweak encrypt/decrypt Daniel P. Berrangé
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 3/8] crypto: introduce a xts_uint128 data type Daniel P. Berrangé
2018-10-16 12:45 ` Alberto Garcia
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 4/8] crypto: convert xts_tweak_encdec to use xts_uint128 type Daniel P. Berrangé
2018-10-16 13:09 ` Alberto Garcia
2018-10-16 13:51 ` Daniel P. Berrangé [this message]
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 5/8] crypto: convert xts_mult_x " Daniel P. Berrangé
2018-10-16 13:35 ` Alberto Garcia
2018-10-16 13:59 ` Daniel P. Berrangé
2018-10-16 14:22 ` Alberto Garcia
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 6/8] crypto: annotate xts_tweak_encdec as inlineable Daniel P. Berrangé
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 7/8] crypto: refactor XTS cipher mode test suite Daniel P. Berrangé
2018-10-16 14:34 ` Alberto Garcia
2018-10-16 10:09 ` [Qemu-devel] [PATCH v2 8/8] crypto: add testing for unaligned buffers with XTS cipher mode Daniel P. Berrangé
2018-10-16 14:50 ` Alberto Garcia
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=20181016135147.GG7995@redhat.com \
--to=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=qemu-devel@nongnu.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 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).