From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, x86@kernel.org,
linux-block@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Keith Busch <kbusch@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v4 0/6] x86 CRC optimizations
Date: Mon, 10 Feb 2025 10:01:17 -0800 [thread overview]
Message-ID: <20250210180117.GF1264@sol.localdomain> (raw)
In-Reply-To: <20250210174540.161705-1-ebiggers@kernel.org>
On Mon, Feb 10, 2025 at 09:45:34AM -0800, Eric Biggers wrote:
> This patchset applies to the crc tree and is also available at:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git crc-x86-v4
>
> This series replaces the existing x86 PCLMULQDQ optimized CRC code with
> new code that is shared among the different CRC variants and also adds
> VPCLMULQDQ support, greatly improving performance on recent CPUs. The
> last patch wires up the same optimization to crc64_be() and crc64_nvme()
> (a.k.a. the old "crc64_rocksoft") which previously were unoptimized,
> improving the performance of those CRC functions by as much as 100x.
> crc64_be is used by bcachefs, and crc64_nvme is used by blk-integrity.
>
FYI, I've applied this to crc-next.
- Eric
prev parent reply other threads:[~2025-02-10 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 17:45 [PATCH v4 0/6] x86 CRC optimizations Eric Biggers
2025-02-10 17:45 ` [PATCH v4 1/6] x86: move ZMM exclusion list into CPU feature flag Eric Biggers
2025-02-10 20:40 ` Borislav Petkov
2025-02-10 21:01 ` Eric Biggers
2025-02-10 21:17 ` Borislav Petkov
2025-02-10 21:37 ` Eric Biggers
2025-02-10 21:49 ` Borislav Petkov
2025-02-10 17:45 ` [PATCH v4 2/6] scripts/gen-crc-consts: add gen-crc-consts.py Eric Biggers
2025-02-10 17:45 ` [PATCH v4 3/6] x86/crc: add "template" for [V]PCLMULQDQ based CRC functions Eric Biggers
2025-02-10 17:45 ` [PATCH v4 4/6] x86/crc32: implement crc32_le using new template Eric Biggers
2025-02-10 17:45 ` [PATCH v4 5/6] x86/crc-t10dif: implement crc_t10dif " Eric Biggers
2025-02-10 17:45 ` [PATCH v4 6/6] x86/crc64: implement crc64_be and crc64_nvme " Eric Biggers
2025-02-10 18:01 ` Eric Biggers [this message]
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=20250210180117.GF1264@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=kbusch@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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 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.