[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB3342A0A8530F74D408CA2F0298FC0@VI1PR0402MB3342.eurprd04.prod.outlook.com>
Date: Wed, 7 Feb 2018 14:39:52 +0000
From: Horia Geantă <horia.geanta@....com>
To: Christophe Leroy <christophe.leroy@....fr>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>
CC: "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside
the requests
On 10/6/2017 4:06 PM, Christophe Leroy wrote:
> At every request, we map and unmap the same hash hw_context.
>
> This patch moves the dma mapping/unmapping in functions ahash_init()
> and ahash_import().
>
> Signed-off-by: Christophe Leroy <christophe.leroy@....fr>
> ---
> drivers/crypto/talitos.c | 80 ++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 57 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/crypto/talitos.c b/drivers/crypto/talitos.c
> index ebfd6d982ed6..d495649d5267 100644
> --- a/drivers/crypto/talitos.c
> +++ b/drivers/crypto/talitos.c
> @@ -819,6 +819,7 @@ struct talitos_ctx {
> unsigned int keylen;
> unsigned int enckeylen;
> unsigned int authkeylen;
> + dma_addr_t dma_hw_context;
This doesn't look correct.
talitos_ctx structure is the tfm context.
dma_hw_context is the IOVA of hw_context, located in talitos_ahash_req_ctx
structure (request context).
If there are multiple requests in flight for the same tfm, dma_hw_context will
be overwritten.
dma_hw_context needs to be moved in request context (talitos_ahash_req_ctx struct).
Thanks,
Horia
Powered by blists - more mailing lists