From: Ingo Molnar <mingo@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, x86@kernel.org,
linux-arch@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 00/12] lib/crc: improve how arch-optimized code is integrated
Date: Mon, 9 Jun 2025 09:40:40 +0200 [thread overview]
Message-ID: <aEaP-A21IB4ufbZT@gmail.com> (raw)
In-Reply-To: <20250607200454.73587-1-ebiggers@kernel.org>
* Eric Biggers <ebiggers@kernel.org> wrote:
> This series is also available at:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git lib-crc-arch-v2
>
> This series improves how lib/crc supports arch-optimized code. First,
> instead of the arch-optimized CRC code being in arch/$(SRCARCH)/lib/, it
> will now be in lib/crc/$(SRCARCH)/. Second, the API functions (e.g.
> crc32c()), arch-optimized functions (e.g. crc32c_arch()), and generic
> functions (e.g. crc32c_base()) will now be part of a single module for
> each CRC type, allowing better inlining and dead code elimination. The
> second change is made possible by the first.
>
> As an example, consider CONFIG_CRC32=m on x86. We'll now have just
> crc32.ko instead of both crc32-x86.ko and crc32.ko. The two modules
> were already coupled together and always both got loaded together via
> direct symbol dependency, so the separation provided no benefit.
>
> Note: later I'd like to apply the same design to lib/crypto/ too, where
> often the API functions are out-of-line so this will work even better.
> In those cases, for each algorithm we currently have 3 modules all
> coupled together, e.g. libsha256.ko, libsha256-generic.ko, and
> sha256-x86.ko. We should have just one, inline things properly, and
> rely on the compiler's dead code elimination to decide the inclusion of
> the generic code instead of manually setting it via kconfig.
>
> Having arch-specific code outside arch/ was somewhat controversial when
> Zinc proposed it back in 2018. But I don't think the concerns are
> warranted. It's better from a technical perspective, as it enables the
> improvements mentioned above. This model is already successfully used
> in other places in the kernel such as lib/raid6/. The community of each
> architecture still remains free to work on the code, even if it's not in
> arch/. At the time there was also a desire to put the library code in
> the same files as the old-school crypto API, but that was a mistake; now
> that the library is separate, that's no longer a constraint either.
>
> Changed in v2:
> - Fixed build warning on architectures without any optimized CRC code
> - Fixed build warning in sparc/crc32.h by removing pr_fmt
> - Moved fallback definitions of crc32*_arch back into arch files
> - Remove ARCH_HAS_CRC* symbols at end of series instead of beginning,
> so that they're not removed until they're no longer being selected
> - Slightly improved some commit messages
> - Rebased onto other pending lib/crc changes
>
> Eric Biggers (12):
> lib/crc: move files into lib/crc/
> lib/crc: prepare for arch-optimized code in subdirs of lib/crc/
> lib/crc/arm: migrate arm-optimized CRC code into lib/crc/
> lib/crc/arm64: migrate arm64-optimized CRC code into lib/crc/
> lib/crc/loongarch: migrate loongarch-optimized CRC code into lib/crc/
> lib/crc/mips: migrate mips-optimized CRC code into lib/crc/
> lib/crc/powerpc: migrate powerpc-optimized CRC code into lib/crc/
> lib/crc/riscv: migrate riscv-optimized CRC code into lib/crc/
> lib/crc/s390: migrate s390-optimized CRC code into lib/crc/
> lib/crc/sparc: migrate sparc-optimized CRC code into lib/crc/
> lib/crc/x86: migrate x86-optimized CRC code into lib/crc/
> lib/crc: remove ARCH_HAS_* kconfig symbols
For the movement of the x86 bits:
Acked-by: Ingo Molnar <mingo@kernel.org>
> rename {arch/s390/lib => lib/crc/s390}/crc32be-vx.c (100%)
> rename {arch/s390/lib => lib/crc/s390}/crc32le-vx.c (100%)
> rename arch/sparc/lib/crc32.c => lib/crc/sparc/crc32.h (60%)
> rename {arch/sparc/lib => lib/crc/sparc}/crc32c_asm.S (100%)
> create mode 100644 lib/crc/tests/Makefile
> rename lib/{ => crc}/tests/crc_kunit.c (100%)
> rename {arch/x86/lib => lib/crc/x86}/crc-pclmul-consts.h (100%)
> rename {arch/x86/lib => lib/crc/x86}/crc-pclmul-template.S (100%)
> rename {arch/x86/lib => lib/crc/x86}/crc-pclmul-template.h (100%)
> rename arch/x86/lib/crc-t10dif.c => lib/crc/x86/crc-t10dif.h (56%)
> rename {arch/x86/lib => lib/crc/x86}/crc16-msb-pclmul.S (100%)
> rename {arch/x86/lib => lib/crc/x86}/crc32-pclmul.S (100%)
One small namespace suggestion: wouldn't it be better to move the arch
support code to lib/crc/arch/, instead of lib/crc/? That way any
generic code will stand out better and architecture directories don't
crowd out what is supposed to be generic code.
Thanks,
Ingo
next prev parent reply other threads:[~2025-06-09 7:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 20:04 [PATCH v2 00/12] lib/crc: improve how arch-optimized code is integrated Eric Biggers
2025-06-07 20:04 ` [PATCH v2 01/12] lib/crc: move files into lib/crc/ Eric Biggers
2025-06-07 20:04 ` [PATCH v2 02/12] lib/crc: prepare for arch-optimized code in subdirs of lib/crc/ Eric Biggers
2025-06-07 20:04 ` [PATCH v2 03/12] lib/crc/arm: migrate arm-optimized CRC code into lib/crc/ Eric Biggers
2025-06-07 20:04 ` [PATCH v2 04/12] lib/crc/arm64: migrate arm64-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 05/12] lib/crc/loongarch: migrate loongarch-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 06/12] lib/crc/mips: migrate mips-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 07/12] lib/crc/powerpc: migrate powerpc-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 08/12] lib/crc/riscv: migrate riscv-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 09/12] lib/crc/s390: migrate s390-optimized " Eric Biggers
2025-06-13 16:01 ` Alexander Gordeev
2025-06-13 17:11 ` Eric Biggers
2025-06-14 13:24 ` Alexander Gordeev
2025-06-07 20:04 ` [PATCH v2 10/12] lib/crc/sparc: migrate sparc-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 11/12] lib/crc/x86: migrate x86-optimized " Eric Biggers
2025-06-07 20:04 ` [PATCH v2 12/12] lib/crc: remove ARCH_HAS_* kconfig symbols Eric Biggers
2025-06-07 23:47 ` [PATCH v2 00/12] lib/crc: improve how arch-optimized code is integrated Jason A. Donenfeld
2025-06-08 23:48 ` Eric Biggers
2025-06-10 17:39 ` Jason A. Donenfeld
2025-06-10 19:12 ` Eric Biggers
2025-06-09 7:40 ` Ingo Molnar [this message]
2025-06-09 18:54 ` Eric Biggers
2025-06-09 8:15 ` Julian Calaby
2025-06-09 19:48 ` Eric Biggers
2025-06-09 22:36 ` Julian Calaby
2025-06-09 22:59 ` Eric Biggers
2025-06-09 19:16 ` Martin K. Petersen
2025-06-10 18:47 ` Eric Biggers
2025-06-14 12:59 ` Alexander Gordeev
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=aEaP-A21IB4ufbZT@gmail.com \
--to=mingo@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).