From: Stanislav Meduna <stano@meduna.org>
To: linux-kernel@vger.kernel.org
Subject: CRC32 - computed or table-driven?
Date: Sun, 5 May 2002 09:44:12 +0200 (CEST) [thread overview]
Message-ID: <200205050904.g4594GV05355@meduna.org> (raw)
Hello,
I need to compute a crc32 in my small not-ready-for-the-prime-time
patch against 2.4.19-pre. I do not (yet) follow the 2.5 development.
There is <linux/crc32.h> that does what I want, but not quite
effectively and with comments that it is unsuitable for bulk data
and that it will migrate to net/core/crc.c.
There are table-driven /usr/src/linux-2.4.19/fs/jffs2/crc32.*, but
this code is hidden in a filesystem subtree.
Any plans to do it "the right way" in 2.4? Is net/core (mentioned
in the crc32.h) the right place? - as we see it is used also
in the filesystem code and lib would be probably a better place.
I can post a patch, but I cannot test whether it breaks jffs2
and as this adds 1 kB to the kernel that might not be needed
I would like to ask first. Who is hacking these parts?
Regards
--
Stano
next reply other threads:[~2002-05-05 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 7:44 Stanislav Meduna [this message]
2002-05-06 20:55 Matt_Domsch
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=200205050904.g4594GV05355@meduna.org \
--to=stano@meduna.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®