All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Frey <jan.frey@nokia.com>
To: ext Shaheed <srhaque@iee.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] support for gzipped (ELF) core dumps
Date: Thu, 13 Jan 2005 12:51:32 +0100	[thread overview]
Message-ID: <1105617091.830.27.camel@borcx178> (raw)
In-Reply-To: <200501081727.52637.srhaque@iee.org>

Hi,

I tried to use those "in-kernel" functions, but they seem to do little
different CRC calculations. Unfortunately I don't have any experiences
with CRC stuff, anyone able to help here?

Regards,
Jan

>  >+/* This table is needed for efficient CRC32 calculation */
>  >+static const unsigned long crc_table[8][256] = {
>  >+ {
>  >+ 0x00000000UL, 0x77073096UL, 0xee0e612cUL, 0x990951baUL, 0x076dc419UL,
>  
> First, by using "unsigned long", you may be doubling the size on most 64 bit 
> platforms. Second, I'm pretty sure there is a standard implementation of 
> several CRCs already in the kernel - is there a reason not to use one of them 
> (e.g. a different polynomial)?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2005-01-13 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 17:27 [PATCH] support for gzipped (ELF) core dumps Shaheed
2005-01-13 11:51 ` Jan Frey [this message]
2005-01-13 13:29   ` Shaheed
2005-01-13 15:28   ` [PATCH] Updated: " Jan Frey
  -- strict thread matches above, loose matches on Subject: below --
2005-01-06 13:19 [PATCH] " Jan Frey
2005-01-06 13:30 ` linux-os
2005-01-06 13:43 ` Miquel van Smoorenburg

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=1105617091.830.27.camel@borcx178 \
    --to=jan.frey@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srhaque@iee.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.