Hi,
On Mon, Sep 24, 2012 at 09:13:15PM +0200, Lluís Batlle i Rossell wrote:
> On Mon, Sep 24, 2012 at 08:54:31PM +0200, Nikos Mavrogiannopoulos wrote:
> > On 09/24/2012 08:46 PM, Lluís Batlle i Rossell wrote:
> > memcpy? Do you see any error message "Error getting user pages. Falling
> > back to n
On Mon, Sep 24, 2012 at 08:54:31PM +0200, Nikos Mavrogiannopoulos wrote:
> On 09/24/2012 08:46 PM, Lluís Batlle i Rossell wrote:
> memcpy? Do you see any error message "Error getting user pages. Falling
> back to non zero copy." to kernel log? The cryptodev operation is pretty
> much zero copy othe
On 09/24/2012 08:46 PM, Lluís Batlle i Rossell wrote:
>> There will be no much change. If you mv_cesa doesn't support sha1, it
>> may be faster to use the userspace implementation of sha1.
> I got it working. Simply, the mv_cesa wants a 'fallback'. Maybe for some
> shorter-than-usual-length block
On Mon, Sep 24, 2012 at 08:08:59PM +0200, Nikos Mavrogiannopoulos wrote:
> On 09/23/2012 11:54 PM, Lluís Batlle i Rossell wrote:
>
> >> Specifically, this 3.5.4 reports on dmesg:
> >> MV-CESA:Fallback driver 'hmac(sha1)' could not be loaded!
> >> MV-CESA:Fallback driver 'sha1' could not be loaded!
On 09/23/2012 11:54 PM, Lluís Batlle i Rossell wrote:
>> Specifically, this 3.5.4 reports on dmesg:
>> MV-CESA:Fallback driver 'hmac(sha1)' could not be loaded!
>> MV-CESA:Fallback driver 'sha1' could not be loaded!
>>
>> This happens every time I run something doing sha1 in openssl. Let it be
>>
On Sun, Sep 23, 2012 at 11:23:19PM +0200, Lluís Batlle i Rossell wrote:
> I've openssl working well with AES, but I find that sha1 is not working.
>
> Specifically, this 3.5.4 reports on dmesg:
> MV-CESA:Fallback driver 'hmac(sha1)' could not be loaded!
> MV-CESA:Fallback driver 'sha1' could not b
