Harsh Jain wrote:
>
> It means cbc, hmac should have smaller(nearly 10 times less) priority
> than their authenc implementation otherwise request will not offload
> to driver because sw authenc priority is (aes * 10 + hmac).
I think you should look at it the other way. The priority of
your hardw
"authenc" and "hmac" are templates, not different implementations of a cipher.
Please take a look at:
https://kernel.readthedocs.io/en/sphinx-samples/crypto-API.html#terminology
On Thu, Apr 6, 2017 at 9:56 AM, Harsh Jain wrote:
> On Tue, Apr 4, 2017 at 6:07 PM, Stephan Müller wrote:
>> Am Dien
On Tue, Apr 4, 2017 at 6:07 PM, Stephan Müller wrote:
> Am Dienstag, 4. April 2017, 09:53:17 CEST schrieb Harsh Jain:
>
> Hi Harsh,
>
>> Hi,
>>
>> Do we have any guidelines documented to decide what should be the
>> algorithm priority. Specially for authenc implementation.Most of the
>> drivers ha
Am Dienstag, 4. April 2017, 09:53:17 CEST schrieb Harsh Jain:
Hi Harsh,
> Hi,
>
> Do we have any guidelines documented to decide what should be the
> algorithm priority. Specially for authenc implementation.Most of the
> drivers have fixed priority for all algos. Problem comes in when we
> have
Hi,
Do we have any guidelines documented to decide what should be the
algorithm priority. Specially for authenc implementation.Most of the
drivers have fixed priority for all algos. Problem comes in when we
have cbc(aes), hmac(sha1) and authenc(cbc(aes),hmac(sha1))
implementation in driver. Base a
