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, sadly.

Best regards,
Anthony Foiani


On Mon, May 27, 2013 at 4:14 AM, Nikos Mavrogiannopoulos
<n...@gnutls.org> wrote:
> On Sat, May 25, 2013 at 8:58 PM, Anthony Foiani
> <anthony.foi...@gmail.com> wrote:
>> Nikos, JT --
>> On Sat, May 25, 2013 at 12:40 PM, Nikos Mavrogiannopoulos
>> <n...@gnutls.org> 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 x86-64 (very modern linux kernel, 3.8.something -- basically
>> fully up-to-date fedora 18 x86-64 box here).  I'm only using it for
>> signing and encrypting, though, not SSL/TLS communications.
>> I can't get a similar combination (openssl 1.0.1e, cryptodev-linux
>> 1.6, linux 3.4.36) to work on my ppc32 target though, due to too-large
>> work units to the security coprocessor.  I sent a bug about that a few
>> weeks ago, although it might have gotten lost in moderation.  Not sure
>> who has the responsibility for breaking down work into small-enough
>> chunks (the Freescale SEC is limited to 2^16-1 bytes at a time), and
>> don't have the bandwidth right now to pursue it myself.  Original
>> report here:
>
> Hello Anthony,
>  So if I understand correctly that was a driver issue that has now
> been solved in 3.8, or the problem still persists?
>
> Cryptodev could work-around driver issues if needed but if the problem
> is already solved in 3.8 I don't think that there is any need for
> action. We may need to document the issue though.
>
> regards,
> Nikos

_______________________________________________
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel

Reply via email to