From: "Bob Pearson" <rpearson@systemfabricworks.com>
To: "'Joakim Tjernlund'" <joakim.tjernlund@transmode.se>,
"'George Spelvin'" <linux@horizon.com>
Cc: <akpm@linux-foundation.org>, <fzago@systemfabricworks.com>,
<linux-kernel@vger.kernel.org>, <rdunlap@xenotime.net>
Subject: RE: [patch v4 1/7] crc32: move-to-documentation.diff
Date: Tue, 9 Aug 2011 13:52:33 -0500 [thread overview]
Message-ID: <016e01cc56c5$800662f0$801328d0$@systemfabricworks.com> (raw)
In-Reply-To: <OF2A1D4C02.965787E8-ONC12578E7.005C021E-C12578E7.005C7904@transmode.se>
> -----Original Message-----
> From: Joakim Tjernlund [mailto:joakim.tjernlund@transmode.se]
> Sent: Tuesday, August 09, 2011 11:50 AM
> To: George Spelvin
> Cc: akpm@linux-foundation.org; fzago@systemfabricworks.com; linux-
> kernel@vger.kernel.org; rdunlap@xenotime.net;
> rpearson@systemfabricworks.com
> Subject: Re: [patch v4 1/7] crc32: move-to-documentation.diff
>
> "George Spelvin" <linux@horizon.com> wrote on 2011/08/09 13:45:04:
> >
> > Here's a hopefully-improved Documentation file, which explains the
slicing
> > algorithm as well. As long as you have a big diff, it seems worth
tweaking.
> >
> > You also might want to leave a pointer in lib/crc32.c to the relocated
docs.
> >
> > (I'm just inclding the whole changed file because I assume it's easier
> > to review that way; do you prefer a diff?)
>
> Nice, reading this once again I think I found an old typo. See below
>
> Perhaps Bob can add this addition to his patch series?
>
> >
> > === Cut here ===
> ...
> > Or in little-endian:
> > for (i = 0; i < input_bytes; i++) {
> > remainder ^= next_input_byte();
> > for (j = 0; j < 8; j++) {
> > multiple = (remainder & 1) ? CRCPOLY : 0;
> > remainder = (remainder << 1) ^ multiple;
>
> Should not above line be:
> remainder = (remainder >> 1) ^ multiple;
I agree. Will change in text.
> ?
>
> > }
> > }
> >
> > If the input is a multiple of 32 bits, you can even XOR in a 32-bit
> > word at a time and increase the inner loop count to 32.
next prev parent reply other threads:[~2011-08-09 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 5:59 [patch v4 1/7] crc32: move-to-documentation.diff Bob Pearson
2011-08-09 11:45 ` George Spelvin
2011-08-09 16:50 ` Joakim Tjernlund
2011-08-09 18:52 ` Bob Pearson [this message]
2011-08-09 21:08 ` Bob Pearson
2011-08-09 16:55 ` Bob Pearson
2011-08-09 19:45 ` George Spelvin
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='016e01cc56c5$800662f0$801328d0$@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 \
--cc=rdunlap@xenotime.net \
/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