public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Pearson <rpearson@systemfabricworks.com>
To: linux-kernel@vger.kernel.org
Cc: fzago@systemfabricworks.com, rpearson@systemfabricworks.com,
	Joakim Tjernlund <joakim.tjernlund@transmode.se>,
	George Spelvin <linux@horizon.com>,
	akpm@linux-foundation.org
Subject: [PATCH v6 00/10] crc32
Date: Wed, 31 Aug 2011 17:29:32 -0500	[thread overview]
Message-ID: <4E5EB5CC.1010605@systemfabricworks.com> (raw)

Hi,

This is an attempt to resolve all the issues that were left in the last review.
There is one proposed change that is still causing a difference of opinion
which has to do with the form of the loops and their performance on x86 and ppc
This version has the change to the form that runs faster on x86 as an ifdef.

This patch series provides improved performance for computing the crc32
polynomial on common hardware by adding the Slicing-by-8 algorithm to the
existing algorithms already included. The new algorithm is very closely
related to the existing algorithm so the extension requires small changes
to implement.  Additionally it cleans up some warnings in the existing
code and adds a kernel mode optional self test to replace the existing
user mode self test.

A description of the existing and new algorithm is included in
Documentation/crc32.txt.


             reply	other threads:[~2011-08-31 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 22:29 Bob Pearson [this message]
2011-09-02 23:50 ` [PATCH v6 00/10] crc32 Andrew Morton
2011-09-03  9:32   ` Joakim Tjernlund
2011-09-06 16:02   ` Bob Pearson

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=4E5EB5CC.1010605@systemfabricworks.com \
    --to=rpearson@systemfabricworks.com \
    --cc=akpm@linux-foundation.org \
    --cc=fzago@systemfabricworks.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    /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