From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: CRC-16 or CRC-32
Date: Fri, 23 Apr 2010 03:46:28 +0000 [thread overview]
Message-ID: <4BD11814.6090102@workingcode.com> (raw)
In-Reply-To: <291B2C7721AC7B49AD11449A2883992E2C4A9BDC3C@SINTEFEXMBX01.sintef.no>
On 4/21/2010 5:17 AM, Milan P. Stanic wrote:
> On Wed, 2010-04-21 at 10:10, Jan Just Keijser wrote:
>> the second problem is: if you want to add CRC32 support then you'd
>> have to get it into the linux kernel . that will take *quite* some
>> time (unless you can live with patched linux kernels).
>
> It wouldn't be so hard to push it to the kernel because Paul Mackerras
> is/was on this list and he is the ppp driver maintainer, I hope ;)
It's a little tricky to implement the feature *well*. You have to be
able to withstand your peer restarting -- which means that while you're
in CRC-32 mode, you have to be able to accept and process an LCP
Configure-Request frame with a CRC-16 FCS on it -- and you need to be
tolerant of peers that are unable to handle switching -- which means
sending LCP Configure-Request messages with more than one FCS.
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
prev parent reply other threads:[~2010-04-23 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 9:42 CRC-16 or CRC-32 Arne Lie
2010-04-20 14:16 ` Jan Just Keijser
2010-04-20 14:38 ` Arne Lie
2010-04-20 14:49 ` Jan Just Keijser
2010-04-20 15:10 ` Milan P. Stanic
2010-04-21 6:56 ` Arne Lie
2010-04-21 8:10 ` Jan Just Keijser
2010-04-21 9:08 ` Milan P. Stanic
2010-04-21 9:17 ` Milan P. Stanic
2010-04-23 3:46 ` James Carlson [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=4BD11814.6090102@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@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