From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig
Date: Fri, 18 Mar 2016 16:37:55 +0100 [thread overview]
Message-ID: <20160318163755.0c33d403@free-electrons.com> (raw)
In-Reply-To: <20160318151826.GI19428@n2100.arm.linux.org.uk>
Russell,
On Fri, 18 Mar 2016 15:18:26 +0000, Russell King - ARM Linux wrote:
> That's kind of the sticking point for userspace. As I understand the
> situation, there's been two userspace APIs for crypto - the current
> one, which is network based (af-alg-rr), but performs badly, and
> another (I forget what it's called but it needs kernel patches, but
> is more popular amongst openwrt folk) which I've no experience of.
You have the choice between cryptodev-linux
(http://cryptodev-linux.org/) or OCF-Linux
(http://ocf-linux.sourceforge.net/).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-18 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 8:12 [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig Romain Perier
2016-03-18 13:14 ` Andrew Lunn
2016-03-18 13:51 ` Thomas Petazzoni
2016-03-18 14:26 ` Gregory CLEMENT
2016-03-18 14:46 ` Russell King - ARM Linux
2016-03-18 15:35 ` Thomas Petazzoni
2016-03-18 15:45 ` Russell King - ARM Linux
2016-03-18 15:52 ` Thomas Petazzoni
2016-03-18 16:22 ` Russell King - ARM Linux
2016-03-19 17:48 ` Jason Cooper
2016-03-18 14:30 ` Andrew Lunn
2016-03-18 15:05 ` Romain Perier
2016-03-18 15:18 ` Russell King - ARM Linux
2016-03-18 15:37 ` Thomas Petazzoni [this message]
2016-03-18 14:21 ` Gregory CLEMENT
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=20160318163755.0c33d403@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 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.