From: "yekai(A)" <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wangzhou1@hisilicon.com>
Subject: Re: [PATCH] crypto: hisilicon/sec - delele the flag CRYPTO_ALG_ALLOCATES_MEMORY
Date: Fri, 13 May 2022 16:07:09 +0800 [thread overview]
Message-ID: <ce014c64-b25a-da31-1468-c673b3e27aad@huawei.com> (raw)
In-Reply-To: <20220513075542.16227-1-yekai13@huawei.com>
On 2022/5/13 15:55, Kai Ye wrote:
> Should not to uses the CRYPTO_ALG_ALLOCATES_MEMORY in SEC2. The SEC2
> driver uses the pre-allocated buffers, including the src sgl pool, dst
> sgl pool and other qp ctx resources. (e.g. IV buffer, mac buffer, key
> buffer). The SEC2 driver doesn't allocate memory during request processing.
> The driver only maps software sgl to allocated hardware sgl during I/O. So
> here is fix it.
>
> Signed-off-by: Kai Ye <yekai13@huawei.com>
> ---
> drivers/crypto/hisilicon/sec2/sec_crypto.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.c b/drivers/crypto/hisilicon/sec2/sec_crypto.c
> index a91635c348b5..6eebe739893c 100644
> --- a/drivers/crypto/hisilicon/sec2/sec_crypto.c
> +++ b/drivers/crypto/hisilicon/sec2/sec_crypto.c
> @@ -2113,7 +2113,6 @@ static int sec_skcipher_decrypt(struct skcipher_request *sk_req)
> .cra_driver_name = "hisi_sec_"sec_cra_name,\
> .cra_priority = SEC_PRIORITY,\
> .cra_flags = CRYPTO_ALG_ASYNC |\
> - CRYPTO_ALG_ALLOCATES_MEMORY |\
> CRYPTO_ALG_NEED_FALLBACK,\
> .cra_blocksize = blk_size,\
> .cra_ctxsize = sizeof(struct sec_ctx),\
> @@ -2366,7 +2365,6 @@ static int sec_aead_decrypt(struct aead_request *a_req)
> .cra_driver_name = "hisi_sec_"sec_cra_name,\
> .cra_priority = SEC_PRIORITY,\
> .cra_flags = CRYPTO_ALG_ASYNC |\
> - CRYPTO_ALG_ALLOCATES_MEMORY |\
> CRYPTO_ALG_NEED_FALLBACK,\
> .cra_blocksize = blk_size,\
> .cra_ctxsize = sizeof(struct sec_ctx),\
>
Please ignore this patch, There was a title misspelled, "delete->delele"
Thanks
Kai
prev parent reply other threads:[~2022-05-13 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:55 Kai Ye
2022-05-13 8:07 ` yekai(A) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce014c64-b25a-da31-1468-c673b3e27aad@huawei.com \
--to=yekai13@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®