From: Eric Biggers <ebiggers@kernel.org>
To: Qingfang Deng <dqfext@gmail.com>
Cc: "Ard Biesheuvel" <ardb@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
linux-crypto@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
"Heiko Stuebner" <heiko.stuebner@vrull.eu>,
"Qingfang Deng" <qingfang.deng@siflower.com.cn>
Subject: Re: [RFC PATCH] crypto: riscv: scalar accelerated GHASH
Date: Thu, 17 Apr 2025 09:58:56 -0700 [thread overview]
Message-ID: <20250417165856.GB800@quark.localdomain> (raw)
In-Reply-To: <CALW65jZVYUZoka7Gbjcoh43qbkD7rGpw8gTZjjOYpZD-BhLyBQ@mail.gmail.com>
On Thu, Apr 17, 2025 at 04:42:46PM +0800, Qingfang Deng wrote:
> > I see. But do you have a particular configuration in mind? Does it
> > have scalar AES too? I looked into that a while ago but I was told
> > that nobody actually incorporates that. So what about these
> > extensions? Are they commonly implemented?
>
> It's aes-generic.c (LUT-based) with accelerated GHASH.
That's an odd combination. Normally accelerated AES and GHASH go together.
Presumably you're targeting some specific RISC-V CPU. Is this going to be a
one-off thing for that specific CPU? Or can we expect many RISC-V CPUs to have
GHASH acceleration without AES? And if so, why?
- Eric
next prev parent reply other threads:[~2025-04-17 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 6:49 [RFC PATCH] crypto: riscv: scalar accelerated GHASH Qingfang Deng
2025-04-17 6:57 ` Ard Biesheuvel
2025-04-17 7:25 ` Qingfang Deng
2025-04-17 7:39 ` Jeffrey Walton
2025-04-17 7:45 ` Qingfang Deng
2025-04-17 7:57 ` Ard Biesheuvel
2025-04-17 8:42 ` Qingfang Deng
2025-04-17 14:15 ` Ard Biesheuvel
2025-04-17 14:39 ` Qingfang Deng
2025-04-17 16:58 ` Eric Biggers [this message]
2025-04-18 1:48 ` Qingfang Deng
2025-04-17 7:21 ` Herbert Xu
2025-04-17 17:09 ` Eric Biggers
2025-04-18 2:49 ` Qingfang Deng
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=20250417165856.GB800@quark.localdomain \
--to=ebiggers@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=christoph.muellner@vrull.eu \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=heiko.stuebner@vrull.eu \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qingfang.deng@siflower.com.cn \
/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