From: "Rémi Denis-Courmont" <remi@remlab.net>
To: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 02/12] riscv: Add vector extension XOR implementation
Date: Tue, 11 Jul 2023 20:33:50 +0300 [thread overview]
Message-ID: <2289969.yH7iMFiWxO@basile.remlab.net> (raw)
In-Reply-To: <20230711153743.1970625-3-heiko@sntech.de>
Le tiistaina 11. heinäkuuta 2023, 18.37.33 EEST Heiko Stuebner a écrit :
> diff --git a/arch/riscv/lib/xor.S b/arch/riscv/lib/xor.S
> new file mode 100644
> index 000000000000..3bc059e18171
> --- /dev/null
> +++ b/arch/riscv/lib/xor.S
> @@ -0,0 +1,81 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/*
> + * Copyright (C) 2021 SiFive
> + */
> +#include <linux/linkage.h>
> +#include <asm-generic/export.h>
> +#include <asm/asm.h>
> +
> +ENTRY(xor_regs_2_)
> + vsetvli a3, a0, e8, m8, ta, ma
AFAICT, so far, Linux only uses `vsetvli` to save/restore/flush vectors, and
that's, of course, with LMUL=8, so that's not really telling much anything.
This function could be the first actual vector optimisation in kernel if/when
it gets merged.
Should the same group multiplier be used for "actual" vector loops throughout
the kernel? I've seen conflicting advises or opinions here. Should kernel code
always use the maximum possible LMUL, depending on register pressure of the
loop? Or will that just increase latency with no bandwidth gains compared to,
say, LMUL=1 or LMUL=2?
> + vle8.v v0, (a1)
> + vle8.v v8, (a2)
> + sub a0, a0, a3
> + vxor.vv v16, v0, v8
> + add a2, a2, a3
> + vse8.v v16, (a1)
> + add a1, a1, a3
> + bnez a0, xor_regs_2_
> + ret
> +END(xor_regs_2_)
> +EXPORT_SYMBOL(xor_regs_2_)
> +
> +ENTRY(xor_regs_3_)
> + vsetvli a4, a0, e8, m8, ta, ma
> + vle8.v v0, (a1)
> + vle8.v v8, (a2)
> + sub a0, a0, a4
> + vxor.vv v0, v0, v8
> + vle8.v v16, (a3)
> + add a2, a2, a4
> + vxor.vv v16, v0, v16
> + add a3, a3, a4
> + vse8.v v16, (a1)
> + add a1, a1, a4
> + bnez a0, xor_regs_3_
> + ret
> +END(xor_regs_3_)
> +EXPORT_SYMBOL(xor_regs_3_)
> +
> +ENTRY(xor_regs_4_)
> + vsetvli a5, a0, e8, m8, ta, ma
> + vle8.v v0, (a1)
> + vle8.v v8, (a2)
> + sub a0, a0, a5
> + vxor.vv v0, v0, v8
> + vle8.v v16, (a3)
> + add a2, a2, a5
> + vxor.vv v0, v0, v16
> + vle8.v v24, (a4)
> + add a3, a3, a5
> + vxor.vv v16, v0, v24
> + add a4, a4, a5
> + vse8.v v16, (a1)
> + add a1, a1, a5
> + bnez a0, xor_regs_4_
> + ret
> +END(xor_regs_4_)
> +EXPORT_SYMBOL(xor_regs_4_)
> +
> +ENTRY(xor_regs_5_)
> + vsetvli a6, a0, e8, m8, ta, ma
> + vle8.v v0, (a1)
> + vle8.v v8, (a2)
> + sub a0, a0, a6
> + vxor.vv v0, v0, v8
> + vle8.v v16, (a3)
> + add a2, a2, a6
> + vxor.vv v0, v0, v16
> + vle8.v v24, (a4)
> + add a3, a3, a6
> + vxor.vv v0, v0, v24
> + vle8.v v8, (a5)
> + add a4, a4, a6
> + vxor.vv v16, v0, v8
> + add a5, a5, a6
> + vse8.v v16, (a1)
> + add a1, a1, a6
> + bnez a0, xor_regs_5_
> + ret
> +END(xor_regs_5_)
> +EXPORT_SYMBOL(xor_regs_5_)
--
レミ・デニ-クールモン
http://www.remlab.net/
next prev parent reply other threads:[~2023-07-11 18:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 15:37 [PATCH v4 00/12] RISC-V: support some cryptography accelerations Heiko Stuebner
2023-07-11 15:37 ` [PATCH v4 01/12] riscv: Add support for kernel mode vector Heiko Stuebner
2023-07-11 17:11 ` Rémi Denis-Courmont
2023-07-13 17:19 ` Andy Chiu
2023-07-11 15:37 ` [PATCH v4 02/12] riscv: Add vector extension XOR implementation Heiko Stuebner
2023-07-11 17:33 ` Rémi Denis-Courmont [this message]
2023-07-11 15:37 ` [PATCH v4 03/12] RISC-V: add helper function to read the vector VLEN Heiko Stuebner
2023-07-11 18:06 ` Rémi Denis-Courmont
2023-07-11 15:37 ` [PATCH v4 04/12] RISC-V: add vector crypto extension detection Heiko Stuebner
2023-07-12 10:40 ` Anup Patel
2023-07-18 14:55 ` Conor Dooley
2023-07-21 5:48 ` Eric Biggers
2023-07-11 15:37 ` [PATCH v4 05/12] RISC-V: crypto: update perl include with helpers for vector (crypto) instructions Heiko Stuebner
2023-07-11 18:04 ` Rémi Denis-Courmont
2023-07-11 15:37 ` [PATCH v4 06/12] RISC-V: crypto: add Zvbb+Zvbc accelerated GCM GHASH implementation Heiko Stuebner
2023-08-10 9:57 ` Andy Chiu
2023-07-11 15:37 ` [PATCH v4 07/12] RISC-V: crypto: add Zvkg " Heiko Stuebner
2023-07-11 15:37 ` [PATCH v4 08/12] RISC-V: crypto: add a vector-crypto-accelerated SHA256 implementation Heiko Stuebner
2023-07-21 4:42 ` Eric Biggers
2023-07-11 15:37 ` [PATCH v4 09/12] RISC-V: crypto: add a vector-crypto-accelerated SHA512 implementation Heiko Stuebner
2023-07-11 15:37 ` [PATCH v4 10/12] RISC-V: crypto: add Zvkned accelerated AES encryption implementation Heiko Stuebner
2023-07-21 5:40 ` Eric Biggers
2023-07-21 11:39 ` Ard Biesheuvel
2023-07-21 14:23 ` Ard Biesheuvel
2023-09-11 13:06 ` Jerry Shih
2023-09-12 7:04 ` Ard Biesheuvel
2023-09-12 7:15 ` Jerry Shih
2023-09-15 1:28 ` He-Jie Shih
2023-07-11 15:37 ` [PATCH v4 11/12] RISC-V: crypto: add Zvksed accelerated SM4 " Heiko Stuebner
2023-07-11 15:37 ` [PATCH v4 12/12] RISC-V: crypto: add Zvksh accelerated SM3 hash implementation Heiko Stuebner
2023-07-13 7:40 ` [PATCH v4 00/12] RISC-V: support some cryptography accelerations Eric Biggers
2023-07-14 6:27 ` Eric Biggers
2023-07-14 7:02 ` Heiko Stuebner
2023-07-21 5:12 ` Eric Biggers
2023-09-14 0:11 ` Eric Biggers
2023-09-14 1:10 ` Charlie Jenkins
2023-09-15 1:48 ` He-Jie Shih
2023-09-15 3:21 ` Jerry Shih
2023-10-06 19:47 ` Eric Biggers
2023-10-06 21:01 ` He-Jie Shih
2023-10-06 23:33 ` Ard Biesheuvel
2023-10-07 22:16 ` Eric Biggers
2023-10-07 21:30 ` Eric Biggers
2023-10-31 2:17 ` Jerry Shih
2023-11-02 4:03 ` Eric Biggers
2023-11-21 23:51 ` Eric Biggers
2023-11-22 7:58 ` Jerry Shih
2023-11-22 23:42 ` Eric Biggers
2023-11-23 0:36 ` Christoph Müllner
2023-11-28 20:19 ` Eric Biggers
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=2289969.yH7iMFiWxO@basile.remlab.net \
--to=remi@remlab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
/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