From: Iuliana Prodan
Some crypto backends might require the requests' private contexts
to be allocated in DMA-able memory.
Signed-off-by: Horia Geanta
---
net/ipv4/esp4.c | 7 ++-
net/ipv6/esp6.c | 7 ++-
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/net/ipv4/esp4.c b
From: Horia Geantă
Date: Sat, 14 Mar 2015 14:16:37 +0200
> However, ESP is not using aead_request_alloc().
Then find a way to adjust it to do so.
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info a
On 3/13/2015 9:46 PM, David Miller wrote:
> From: Horia Geanta
> Date: Fri, 13 Mar 2015 19:15:22 +0200
>
>> Some crypto backends might require the requests' private contexts
>> to be allocated in DMA-able memory.
>>
>> Signed-off-by: Horia Geanta
>
> No way.
>
> Upper layers should be absolute
From: Horia Geanta
Date: Fri, 13 Mar 2015 19:15:22 +0200
> Some crypto backends might require the requests' private contexts
> to be allocated in DMA-able memory.
>
> Signed-off-by: Horia Geanta
No way.
Upper layers should be absolutely not required to know about such
requirements.
Such deta
Some crypto backends might require the requests' private contexts
to be allocated in DMA-able memory.
Signed-off-by: Horia Geanta
---
Depends on patch 1/4 (sent only on crypto list) that adds the
CRYPTO_TFM_REQ_DMA flag.
net/ipv4/esp4.c | 7 ++-
net/ipv6/esp6.c | 7 ++-
2 files changed
