From: Eric Biggers <ebiggers@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, herbert@gondor.apana.org.au,
davem@davemloft.net, conor.dooley@microchip.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, christoph.muellner@vrull.eu,
Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: Re: [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Date: Wed, 29 Mar 2023 18:43:59 +0000 [thread overview]
Message-ID: <ZCSG71bRuTzVutdm@gmail.com> (raw)
In-Reply-To: <20230329140642.2186644-1-heiko.stuebner@vrull.eu>
Hi Heiko,
On Wed, Mar 29, 2023 at 04:06:38PM +0200, Heiko Stuebner wrote:
>
> [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Has there been consideration of implementing AES-GCM instead of GHASH by itself?
This is what arm64 does, for example. There is not currently any use case for
GHASH outside of AES-GCM, and it's more efficient to implement the full AES-GCM.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, herbert@gondor.apana.org.au,
davem@davemloft.net, conor.dooley@microchip.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, christoph.muellner@vrull.eu,
Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: Re: [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Date: Wed, 29 Mar 2023 18:43:59 +0000 [thread overview]
Message-ID: <ZCSG71bRuTzVutdm@gmail.com> (raw)
In-Reply-To: <20230329140642.2186644-1-heiko.stuebner@vrull.eu>
Hi Heiko,
On Wed, Mar 29, 2023 at 04:06:38PM +0200, Heiko Stuebner wrote:
>
> [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions
Has there been consideration of implementing AES-GCM instead of GHASH by itself?
This is what arm64 does, for example. There is not currently any use case for
GHASH outside of AES-GCM, and it's more efficient to implement the full AES-GCM.
- Eric
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-29 18:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 14:06 [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 1/4] RISC-V: add Zbc extension detection Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 2/4] RISC-V: add Zbkb " Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 3/4] RISC-V: hook new crypto subdir into build-system Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 14:06 ` [PATCH v4 4/4] RISC-V: crypto: add accelerated GCM GHASH implementation Heiko Stuebner
2023-03-29 14:06 ` Heiko Stuebner
2023-03-29 18:37 ` Eric Biggers
2023-03-29 18:37 ` Eric Biggers
2023-03-29 19:20 ` Heiko Stübner
2023-03-29 19:20 ` Heiko Stübner
2023-04-05 15:04 ` Heiko Stübner
2023-04-05 15:04 ` Heiko Stübner
2023-06-12 14:45 ` Heiko Stübner
2023-06-12 14:45 ` Heiko Stübner
2023-04-11 15:00 ` Nathan Huckleberry
2023-04-11 15:00 ` Nathan Huckleberry
2023-05-11 10:30 ` Heiko Stübner
2023-05-11 10:30 ` Heiko Stübner
2023-05-11 19:02 ` Nathan Huckleberry
2023-05-11 19:02 ` Nathan Huckleberry
2023-03-29 18:43 ` Eric Biggers [this message]
2023-03-29 18:43 ` [PATCH v4 0/4] Implement GCM ghash using Zbc and Zbkb extensions Eric Biggers
2023-04-26 22:55 ` Eric Biggers
2023-04-26 22:55 ` Eric Biggers
2023-04-26 23:20 ` Heiko Stübner
2023-04-26 23:20 ` Heiko Stübner
2023-04-26 23:23 ` Eric Biggers
2023-04-26 23:23 ` Eric Biggers
2023-04-26 23:28 ` Heiko Stübner
2023-04-26 23:28 ` Heiko Stübner
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=ZCSG71bRuTzVutdm@gmail.com \
--to=ebiggers@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=christoph.muellner@vrull.eu \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=heiko.stuebner@vrull.eu \
--cc=heiko@sntech.de \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.