All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/7] btrfs-progs: crypto: cleanup and prepare for new architectures
Date: Mon,  9 Nov 2026 14:39:54 +1030	[thread overview]
Message-ID: <cover.1794196688.git.wqu@suse.com> (raw)

[CHANGELOG]
v2:
- Introduce new cleanups as a preparation for new architectures
- Enhance hash-*test to bring more coverage

The patchset is split into 3 mostly independent parts:

- ASM cleanup
  Patch 1 and 2.
  To remove existing inlined or dedicated ASM file usages.
  Use compiler wrappers instead, and port an existing ASM file for
  pclmul optimization to pure C with compiler wrappers.

- Minor rename and cleanups for new architecture
  Patch 3 ~ 5.

- Enhance existing hash-*test
  Patch 6 and 7.

  To bring more block sizes.

Qu Wenruo (7):
  btrfs-progs: cleanup inline asm usage
  btrfs-progs: crypto/crc32c: port crc32c-pcl optimization to C
  btrfs-progs: rename cpu features to prepare for other archs
  btrfs-progs: simplify the cpu utils for future expanasion
  btrfs-progs: crypto: select accelerated algo directly for testing
  btrfs-progs: crypto: hash-speedtest: cover more block sizes
  btrfs-progs: crypto: hash-vectest: cover more block sizes

 .gitignore                       |   1 +
 Makefile                         |  14 --
 common/cpu-utils.c               | 104 +++------
 common/cpu-utils.h               |  19 +-
 config/ax_gcc_builtin.m4         |   1 +
 configure.ac                     |   1 +
 crypto/blake2.h                  |   2 +
 crypto/blake2b-ref.c             |  30 ++-
 crypto/crc32c-pcl-intel-asm_64.S | 370 -------------------------------
 crypto/crc32c.c                  | 320 +++++++++++++++++++++++---
 crypto/crc32c.h                  |   2 +
 crypto/hash-speedtest.c          | 179 ++++++++-------
 crypto/hash-vectest.c            | 212 ++++++++++++++++--
 crypto/hash.c                    |   9 +
 crypto/hash.h                    |   2 +
 crypto/sha.h                     |   2 +
 crypto/sha224-256.c              |  18 +-
 libbtrfs/crc32c.c                |  43 +---
 18 files changed, 676 insertions(+), 653 deletions(-)
 delete mode 100644 crypto/crc32c-pcl-intel-asm_64.S

--
2.56.0


             reply	other threads:[~2026-11-09  4:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  4:09 Qu Wenruo [this message]
2026-11-09  4:09 ` [PATCH v2 1/7] btrfs-progs: cleanup inline asm usage Qu Wenruo
2026-11-09  4:09 ` [PATCH v2 2/7] btrfs-progs: crypto/crc32c: port crc32c-pcl optimization to C Qu Wenruo
2026-11-11 16:58   ` good crcs in userspace, " Christoph Hellwig
2026-11-11 20:28     ` Qu Wenruo
2026-11-09  4:09 ` [PATCH v2 3/7] btrfs-progs: rename cpu features to prepare for other archs Qu Wenruo
2026-11-09  4:09 ` [PATCH v2 4/7] btrfs-progs: simplify the cpu utils for future expanasion Qu Wenruo
2026-11-09  4:09 ` [PATCH v2 5/7] btrfs-progs: crypto: select accelerated algo directly for testing Qu Wenruo
2026-11-09  4:10 ` [PATCH v2 6/7] btrfs-progs: crypto: hash-speedtest: cover more block sizes Qu Wenruo
2026-11-09  4:10 ` [PATCH v2 7/7] btrfs-progs: crypto: hash-vectest: " Qu Wenruo

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=cover.1794196688.git.wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.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.