From: David Laight <David.Laight@ACULAB.COM>
To: "'Paulo Flabiano Smorigo'" <pfsmorigo@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Paul Mackerras <paulus@samba.org>,
"open list:IBM Power VMX Cryptographic instructions"
<linux-crypto@vger.kernel.org>,
"open list:LINUX FOR POWERPC 32-BIT AND 64-BIT"
<linuxppc-dev@lists.ozlabs.org>,
"David S. Miller" <davem@davemloft.net>
Subject: RE: [PATCH 1/2] crypto: vmx - Adding asm subroutines for XTS
Date: Tue, 12 Jul 2016 16:19:42 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D5F4F62C4@AcuExch.aculab.com> (raw)
In-Reply-To: <1468264060-22769-1-git-send-email-pfsmorigo@linux.vnet.ibm.com>
From: Paulo Flabiano Smorigo
> Sent: 11 July 2016 20:08
>
> This patch add XTS subroutines using VMX-crypto driver.
>
> It gives a boost of 20 times using XTS.
>
> These code has been adopted from OpenSSL project in collaboration
> with the original author (Andy Polyakov <appro@openssl.org>).
Yep, typical openssl code. 1000+ lines of uncommented impenetrable assembler.
There is 0 chance of anyone ever checking this does what it should.
David
prev parent reply other threads:[~2016-07-12 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 19:07 [PATCH 1/2] crypto: vmx - Adding asm subroutines for XTS Paulo Flabiano Smorigo
2016-07-11 19:07 ` [PATCH 2/2] crypto: vmx - Adding support " Paulo Flabiano Smorigo
2016-07-11 20:10 ` Stephan Mueller
2016-07-11 23:37 ` [PATCH 1/2] crypto: vmx - Adding asm subroutines " Stephen Rothwell
2016-07-13 3:05 ` Stewart Smith
2016-07-13 13:34 ` Paulo Flabiano Smorigo
2016-07-13 15:11 ` Stephen Rothwell
2016-07-13 16:02 ` Paulo Flabiano Smorigo
2016-07-12 16:19 ` David Laight [this message]
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=063D6719AE5E284EB5DD2968C1650D6D5F4F62C4@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=pfsmorigo@linux.vnet.ibm.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).