From: Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>
To: "noloader@gmail.com" <noloader@gmail.com>,
Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Eric Biggers <ebiggers@kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: RE: another testmgr question
Date: Fri, 24 May 2019 09:42:31 +0000 [thread overview]
Message-ID: <AM6PR09MB352306D397F46D5FB5880999D2020@AM6PR09MB3523.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <CAH8yC8nBDa438QsJvs91CGV-e+-j9UxnB2pQ6-KAy0jV3EXj-w@mail.gmail.com>
> On Fri, May 24, 2019 at 4:47 AM Christophe Leroy
> <christophe.leroy@c-s.fr> wrote:
> > ...
> > > As I already mentioned in another thread somewhere, this morning in the
> > > shower I realised that this may be useful if you have no expectation of
> > > the length itself. But it's still a pretty specific use case which was
> > > never considered for our hardware. And our HW doesn't seem to be alone in
> > > this.
> > > Does shaXXXsum or md5sum use the kernel crypto API though?
> >
> > The ones from libkcapi do (http://www.chronox.de/libkcapi.html)
>
> And they can be loaded into OpenSSL through the afalg interface.
>
Hmm ... yeah ... OpenSSL ... yet another synchronous API that doesn't stand a
chance of being HW accelerated (although Intel contributed some async API
fairly recently - but I don't know of any application actually ported to use
that - would love to hear about any if they do exist).
Sorry, open wound ...
Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Inside Secure
www.insidesecure.com
next prev parent reply other threads:[~2019-05-24 9:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM6PR09MB3523CED0B1587FCBDE4095A0D2010@AM6PR09MB3523.eurprd09.prod.outlook.com>
[not found] ` <20190523185833.GA243994@google.com>
2019-05-23 19:32 ` another testmgr question Pascal Van Leeuwen
2019-05-23 20:05 ` Eric Biggers
2019-05-23 21:43 ` Pascal Van Leeuwen
2019-05-23 23:48 ` Eric Biggers
2019-05-24 8:44 ` Pascal Van Leeuwen
2019-05-24 8:46 ` Christophe Leroy
2019-05-24 8:49 ` Jeffrey Walton
2019-05-24 9:42 ` Pascal Van Leeuwen [this message]
2019-05-24 9:21 ` Pascal Van Leeuwen
2019-05-24 9:25 ` Ard Biesheuvel
2019-05-24 9:34 ` Pascal Van Leeuwen
2019-05-24 9:45 ` Ard Biesheuvel
2019-05-24 9:57 ` Pascal Van Leeuwen
2019-05-24 11:09 ` Ard Biesheuvel
2019-05-27 9:52 ` Pascal Van Leeuwen
2019-05-24 10:13 ` Pascal Van Leeuwen
2019-05-24 10:43 ` Kamil Konieczny
2019-05-24 10:54 ` Christophe Leroy
2019-05-27 9:44 ` Pascal Van Leeuwen
2019-05-27 9:49 ` Ard Biesheuvel
2019-05-27 10:04 ` Pascal Van Leeuwen
2019-05-27 10:28 ` Ard Biesheuvel
2019-05-27 10:43 ` Pascal Van Leeuwen
2019-05-27 10:57 ` Ard Biesheuvel
2019-05-27 12:22 ` Pascal Van Leeuwen
2019-05-27 14:59 ` Ard Biesheuvel
2019-05-27 15:56 ` Pascal Van Leeuwen
2019-05-27 16:21 ` Ard Biesheuvel
2019-05-27 20:15 ` Pascal Van Leeuwen
2019-05-27 12:41 ` Pascal Van Leeuwen
2019-05-27 14:45 ` Ard Biesheuvel
2019-05-27 15:16 ` Pascal Van Leeuwen
2019-05-27 15:24 ` Ard Biesheuvel
2019-05-27 20:46 ` Pascal Van Leeuwen
2019-05-25 1:22 ` Eric Biggers
2019-05-27 9:55 ` Pascal Van Leeuwen
2019-05-24 9:27 ` Stephan Mueller
2019-05-24 5:24 ` Ard Biesheuvel
2019-05-24 7:04 ` Kamil Konieczny
2019-05-24 7:47 ` Pascal Van Leeuwen
2019-05-24 9:15 ` Ard Biesheuvel
2019-05-24 9:28 ` Pascal Van Leeuwen
2019-05-24 6:21 ` Christophe Leroy
2019-05-24 8:04 ` Pascal Van Leeuwen
2019-05-24 6:14 ` Jeffrey Walton
2019-05-24 8:00 ` Pascal Van Leeuwen
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=AM6PR09MB352306D397F46D5FB5880999D2020@AM6PR09MB3523.eurprd09.prod.outlook.com \
--to=pvanleeuwen@insidesecure.com \
--cc=christophe.leroy@c-s.fr \
--cc=ebiggers@kernel.org \
--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 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.