JT --
On Fri, Jul 26, 2013 at 11:25 PM, JT Olds wrote:
> So, yeah, openssl speed -evp aes-128-cbc definitely shows a huge
> improvement with cryptodev. It's huge orders of magnitude faster with
> cryptodev.ko inserted into the kernel than without, and it's actually
> about twice as fast as AF_AL
On Fri, Jul 26, 2013 at 10:48 PM, Anthony Foiani
wrote:
> JT --
>
> On Fri, Jul 26, 2013 at 6:18 PM, JT Olds wrote:
>
>> I'm not totally sure the tests exercised cryptodev.ko,
>
> I can't speak to the rest of your questions, but an easy way to test
> that the cryptodev is being used is to use the
JT --
On Fri, Jul 26, 2013 at 6:18 PM, JT Olds wrote:
> I'm not totally sure the tests exercised cryptodev.ko,
I can't speak to the rest of your questions, but an easy way to test
that the cryptodev is being used is to use the openssl speed test.
The native / default mode is to report CPU secon
So, I finally got back to this, sorry for the 2-month delay.
I started completely fresh. I built openssl-1.0.1e after patchiing
eng_cryptodev.c with the one provided in cryptodev-linux 1.6 in the
extras folder. I made sure to have crypto/cryptodev.h in my include
path and built with the addition o
Just for a bit more background, this is on a Marvell Kirkwood device.
On Fri, Jul 26, 2013 at 6:18 PM, JT Olds wrote:
> So, I finally got back to this, sorry for the 2-month delay.
>
> I started completely fresh. I built openssl-1.0.1e after patchiing
> eng_cryptodev.c with the one provided in cr
Nikos --
I haven't tried 3.8 on PPC32.
The acceleration architectures are so different that I'm hesitant to
draw any conclusions on PPC32 based on x86 failure/success.
If I get a chance, I'll try to test out a more current kernel on my
ppc32 box, but that probably won't be for quite a while yet,
On Sat, May 25, 2013 at 8:58 PM, Anthony Foiani
wrote:
> Nikos, JT --
> On Sat, May 25, 2013 at 12:40 PM, Nikos Mavrogiannopoulos
> wrote:
>> I was under the impression the latest openssl included quite a decent
>> eng_cryptodev.c, but as I understand from your mail it doesn't.
> It's my experien
Nikos, JT --
On Sat, May 25, 2013 at 12:40 PM, Nikos Mavrogiannopoulos
wrote:
> I was under the impression the latest openssl included quite a decent
> eng_cryptodev.c, but as I understand from your mail it doesn't.
It's my experience that openssl-1.0.1e works fine with linux-cryptodev
1.6 on x8
On 05/24/2013 06:19 AM, JT Olds wrote:
>> Hello,
>> It seems that the /dev/crypto device in that system is from an older
>> cryptodev driver. You may want to unload the old module and load the new
>> one.
> This is release 1.6 that I built and deployed. Is there something newer?
No. However you
> Hello,
> It seems that the /dev/crypto device in that system is from an older
> cryptodev driver. You may want to unload the old module and load the new
> one.
This is release 1.6 that I built and deployed. Is there something newer?
>
>> Second, Wheezy's OpenSSL 1.0.1e isn't built with cryptod
On 05/21/2013 10:54 PM, JT Olds wrote:
> Hey all,
>
> I have a Marvell ARM device (kirkwood/mv_cesa) running Debian Wheezy (so,
> OpenSSL 1.0.1e) with a Linux 3.8.6 kernel. I am trying to get cryptodev to
> work.
> First off, cryptodev's "make check" fails the following tests:
> ./cipher-aead-srt
Hey all,
I have a Marvell ARM device (kirkwood/mv_cesa) running Debian Wheezy (so,
OpenSSL 1.0.1e) with a Linux 3.8.6 kernel. I am trying to get cryptodev to
work.
First off, cryptodev's "make check" fails the following tests:
./cipher-aead-srtp
ioctl(CIOCGSESSION): Invalid argument
./cipher-gcm
12 matches
Mail list logo
