From: Eric Biggers <ebiggers@kernel.org>
To: liulongfang <liulongfang@huawei.com>
Cc: Chenghai Huang <huangchenghai2@huawei.com>,
herbert@gondor.apana.org.au, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
fanghao11@huawei.com, qianweili@huawei.com,
wangzhou1@hisilicon.com
Subject: Re: [PATCH] crypto: hisilicon/sec2 - lower priority for hisilicon crypto implementations
Date: Wed, 20 May 2026 01:32:40 +0000 [thread overview]
Message-ID: <20260520013240.GC1875993@google.com> (raw)
In-Reply-To: <fe78b23b-37bb-5995-94b5-64fcf9578722@huawei.com>
On Wed, May 20, 2026 at 09:22:49AM +0800, liulongfang wrote:
> On 2026/5/11 8:49, Chenghai Huang wrote:
> > From: lizhi <lizhi206@huawei.com>
> >
> > Lower the priority of HiSilicon's crypto implementations to allow more
> > suitable alternatives to be selected. For example, certain kernel
> > use-cases do not benefit from HiSilicon's symmetric crypto algorithms.
> > This change ensures that more appropriate options are chosen first while
> > retaining HiSilicon's implementations as alternatives.
> >
> > Signed-off-by: lizhi <lizhi206@huawei.com>
> > Signed-off-by: Chenghai Huang <huangchenghai2@huawei.com>
> > ---
> > drivers/crypto/hisilicon/sec2/sec_crypto.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.c b/drivers/crypto/hisilicon/sec2/sec_crypto.c
> > index 2471a4dd0b50..77e0e03cbcab 100644
> > --- a/drivers/crypto/hisilicon/sec2/sec_crypto.c
> > +++ b/drivers/crypto/hisilicon/sec2/sec_crypto.c
> > @@ -20,7 +20,7 @@
> > #include "sec.h"
> > #include "sec_crypto.h"
> >
> > -#define SEC_PRIORITY 4001
> > +#define SEC_PRIORITY 80
> > #define SEC_XTS_MIN_KEY_SIZE (2 * AES_MIN_KEY_SIZE)
> > #define SEC_XTS_MID_KEY_SIZE (3 * AES_MIN_KEY_SIZE)
> > #define SEC_XTS_MAX_KEY_SIZE (2 * AES_MAX_KEY_SIZE)
> >
>
> Reviewed-by: Longfang Liu <liulongfang@huawei.com>
Makes sense, but perhaps this driver should just be removed entirely?
- Eric
next prev parent reply other threads:[~2026-05-20 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 0:49 [PATCH] crypto: hisilicon/sec2 - lower priority for hisilicon crypto implementations Chenghai Huang
2026-05-20 1:22 ` liulongfang
2026-05-20 1:32 ` Eric Biggers [this message]
2026-05-20 9:27 ` huangchenghai
2026-05-22 12:27 ` Herbert Xu
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=20260520013240.GC1875993@google.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=fanghao11@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=huangchenghai2@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--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