Quoting Garg Vakul-B16394 <B16394@xxxxxxxxxxxxx>:
-----Original Message-----
From: Jussi Kivilinna [mailto:jussi.kivilinna@xxxxxxxx]
Sent: Saturday, January 19, 2013 5:25 AM
To: Garg Vakul-B16394
Cc: linux-crypto@xxxxxxxxxxxxxxx
Subject: RE: [PATCH][RFC] crypto: tcrypt - Ahash tests changed to run in
parallel.
Quoting Garg Vakul-B16394 <B16394@xxxxxxxxxxxxx>:
>
>> Does not this change make tcrypt give inconsistent results?
>>
>
> Based on kernel scheduling of threads, this change can make tcrypt
> give varying results in different runs.
> For consistent results, we can use existing synchronous mode crypto
sessions.
But one cannot get consistent results for asynchronous software
implementations after this patch.
Should we launch threads optionally based on module argument (in
both synchronous and async mode)?
This would preserve existing tcrypt behavior.
Yes, that would be better.
-Jussi
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
