From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-mips@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-crypto@vger.kernel.org, loongarch@lists.linux.dev,
sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-ext4@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [f2fs-dev] [PATCH v2 03/18] lib/crc32: expose whether the lib is really optimized at runtime
Date: Fri, 25 Oct 2024 22:31:52 +0000 [thread overview]
Message-ID: <20241025223152.GC2637569@google.com> (raw)
In-Reply-To: <CAMj1kXHZy3yPvonS5ZVof0qa0V_Lxhv5Q7i1UVf5P6D3d+=KRw@mail.gmail.com>
On Fri, Oct 25, 2024 at 11:37:45PM +0200, Ard Biesheuvel wrote:
> On Fri, 25 Oct 2024 at 23:32, Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > On Fri, Oct 25, 2024 at 10:32:14PM +0200, Ard Biesheuvel wrote:
> > > On Fri, 25 Oct 2024 at 21:15, Eric Biggers <ebiggers@kernel.org> wrote:
> > > >
> > > > From: Eric Biggers <ebiggers@google.com>
> > > >
> > > > Make the CRC32 library export some flags that indicate which CRC32
> > > > functions are actually executing optimized code at runtime. Set these
> > > > correctly from the architectures that implement the CRC32 functions.
> > > >
> > > > This will be used to determine whether the crc32[c]-$arch shash
> > > > algorithms should be registered in the crypto API. btrfs could also
> > > > start using these flags instead of the hack that it currently uses where
> > > > it parses the crypto_shash_driver_name.
> > > >
> > > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > > > ---
> > > > arch/arm64/lib/crc32-glue.c | 15 +++++++++++++++
> > > > arch/riscv/lib/crc32-riscv.c | 15 +++++++++++++++
> > > > include/linux/crc32.h | 15 +++++++++++++++
> > > > lib/crc32.c | 5 +++++
> > > > 4 files changed, 50 insertions(+)
> > > >
> > > ...
> > > > diff --git a/include/linux/crc32.h b/include/linux/crc32.h
> > > > index 58c632533b08..bf26d454b60d 100644
> > > > --- a/include/linux/crc32.h
> > > > +++ b/include/linux/crc32.h
> > > > @@ -35,10 +35,25 @@ static inline u32 __pure __crc32c_le(u32 crc, const u8 *p, size_t len)
> > > > if (IS_ENABLED(CONFIG_CRC32_ARCH))
> > > > return crc32c_le_arch(crc, p, len);
> > > > return crc32c_le_base(crc, p, len);
> > > > }
> > > >
> > > > +/*
> > > > + * crc32_optimizations contains flags that indicate which CRC32 library
> > > > + * functions are using architecture-specific optimizations. Unlike
> > > > + * IS_ENABLED(CONFIG_CRC32_ARCH) it takes into account the different CRC32
> > > > + * variants and also whether any needed CPU features are available at runtime.
> > > > + */
> > > > +#define CRC32_LE_OPTIMIZATION BIT(0) /* crc32_le() is optimized */
> > > > +#define CRC32_BE_OPTIMIZATION BIT(1) /* crc32_be() is optimized */
> > > > +#define CRC32C_OPTIMIZATION BIT(2) /* __crc32c_le() is optimized */
> > > > +#if IS_ENABLED(CONFIG_CRC32_ARCH)
> > > > +extern u32 crc32_optimizations;
> > > > +#else
> > > > +#define crc32_optimizations 0
> > > > +#endif
> > > > +
> > >
> > > Wouldn't it be cleaner to add a new library function for this, instead
> > > of using a global variable?
> >
> > The architecture crc32 modules need to be able to write to this. There could be
> > a setter function and a getter function, but just using a variable is simpler.
> >
>
> If we just add 'u32 crc32_optimizations()', there is no need for those
> modules to have init/exit hooks, the only thing they need to export is
> this routine.
>
> Or perhaps it could even be a static inline, with the right plumbing
> of header files. At least on arm64,
>
> static inline u32 crc32_optimizations() {
> if (!alternative_have_const_cap_likely(ARM64_HAS_CRC32))
> return 0;
> return CRC32_LE_OPTIMIZATION | CRC32_BE_OPTIMIZATION | CRC32C_OPTIMIZATION;
> }
>
> should be all we need.
In 7 of the 9 affected arches, I already have a module_init function that checks
the CPU features in order to set up static keys. (arm64 and riscv already used
alternatives patching, so I kept that.) It's slightly convenient to set these
flags at the same time, but yes the above solution would work too.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-10-25 22:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 19:14 [f2fs-dev] [PATCH v2 00/18] Wire up CRC32 library functions to arch-optimized code Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 01/18] lib/crc32: drop leading underscores from __crc32c_le_base Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 02/18] lib/crc32: improve support for arch-specific overrides Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 03/18] lib/crc32: expose whether the lib is really optimized at runtime Eric Biggers via Linux-f2fs-devel
2024-10-25 20:32 ` Ard Biesheuvel via Linux-f2fs-devel
2024-10-25 21:32 ` Eric Biggers via Linux-f2fs-devel
2024-10-25 21:37 ` Ard Biesheuvel via Linux-f2fs-devel
2024-10-25 22:31 ` Eric Biggers via Linux-f2fs-devel [this message]
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 04/18] crypto: crc32 - don't unnecessarily register arch algorithms Eric Biggers via Linux-f2fs-devel
2024-10-25 20:47 ` Ard Biesheuvel via Linux-f2fs-devel
2024-10-25 22:02 ` Eric Biggers via Linux-f2fs-devel
2024-10-26 4:09 ` Eric Biggers via Linux-f2fs-devel
2024-10-27 8:14 ` Ard Biesheuvel via Linux-f2fs-devel
2024-11-02 9:45 ` Herbert Xu via Linux-f2fs-devel
2024-11-02 9:58 ` Ard Biesheuvel via Linux-f2fs-devel
2024-11-02 10:19 ` Herbert Xu via Linux-f2fs-devel
2024-11-02 10:46 ` Ard Biesheuvel via Linux-f2fs-devel
2024-11-02 11:05 ` Ard Biesheuvel via Linux-f2fs-devel
2024-11-02 11:08 ` Herbert Xu via Linux-f2fs-devel
2024-11-02 16:36 ` Eric Biggers via Linux-f2fs-devel
2024-11-02 16:46 ` Ard Biesheuvel via Linux-f2fs-devel
2024-11-02 17:21 ` Milan Broz
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 05/18] arm/crc32: expose CRC32 functions through lib Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 06/18] loongarch/crc32: " Eric Biggers via Linux-f2fs-devel
2024-11-03 13:36 ` WangYuli
2024-11-03 13:57 ` Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 07/18] mips/crc32: " Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 08/18] powerpc/crc32: " Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 09/18] s390/crc32: " Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 10/18] sparc/crc32: " Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 11/18] x86/crc32: update prototype for crc_pcl() Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 12/18] x86/crc32: update prototype for crc32_pclmul_le_16() Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 13/18] x86/crc32: expose CRC32 functions through lib Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 14/18] lib/crc32: make crc32c() go directly to lib Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 15/18] ext4: switch to using the crc32c library Eric Biggers via Linux-f2fs-devel
2024-11-02 22:26 ` Theodore Ts'o
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 16/18] jbd2: " Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 17/18] f2fs: switch to using the crc32 library Eric Biggers via Linux-f2fs-devel
2024-10-25 19:14 ` [f2fs-dev] [PATCH v2 18/18] scsi: target: iscsi: switch to using the crc32c library Eric Biggers via Linux-f2fs-devel
2024-10-25 22:14 ` Ard Biesheuvel via Linux-f2fs-devel
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=20241025223152.GC2637569@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--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-ext4@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=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=sparclinux@vger.kernel.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).