All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] lib/crc32: remove unused combination support
Date: Sun, 8 Jun 2025 16:47:41 -0700	[thread overview]
Message-ID: <20250608234741.GF1259@sol> (raw)
In-Reply-To: <20250607032228.27868-1-ebiggers@kernel.org>

On Fri, Jun 06, 2025 at 08:22:28PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Remove crc32_le_combine() and crc32_le_shift(), since they are no longer
> used.
> 
> Although combination is an interesting thing that can be done with CRCs,
> it turned out that none of the users of it in the kernel were even close
> to being worthwhile.  All were much better off simply chaining the CRCs
> or processing zeroes.
> 
> Let's remove the CRC32 combination code for now.  It can come back
> (potentially optimized with carryless multiplication instructions) if
> there is ever a case where it would actually be worthwhile.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  include/linux/crc32.h | 25 ----------------
>  lib/crc32.c           | 67 -------------------------------------------
>  lib/tests/crc_kunit.c | 39 +------------------------
>  3 files changed, 1 insertion(+), 130 deletions(-)

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next

- Eric

      reply	other threads:[~2025-06-08 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  3:22 [PATCH] lib/crc32: remove unused combination support Eric Biggers
2025-06-08 23:47 ` 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=20250608234741.GF1259@sol \
    --to=ebiggers@kernel.org \
    --cc=ardb@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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.