From: Ben Greear <greearb@candelatech.com>
To: root@chaos.analogic.com
Cc: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Ethernet Error Correction
Date: Tue, 25 Sep 2001 14:19:04 -0700 [thread overview]
Message-ID: <3BB0F4C8.124B6576@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010925164155.11921A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
>
> On Tue, 25 Sep 2001, Karel Kulhavy wrote:
>
> > What about implementing an Ethernet error correction in Linux kernel?
> >
>
> Ethernet uses hardware error detection. Only good packets get through.
> Therefore there is nothing that a driver in the kernel could do to
> recover an otherwise errored packet because the packet doesn't exist.
>
That's probably the default of most chipsets, but I wonder if you could
tell it to send the busted packets up the stack anyway. Then, the driver
could make the decision in software whether or not to correct/foward, or
discard the packet... I assume that in order to detect a CRC error,
the NIC already has the packet in it's buffers somewhere...
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-09-25 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 20:34 Ethernet Error Correction Karel Kulhavy
2001-09-25 20:57 ` Richard B. Johnson
2001-09-25 21:19 ` Ben Greear [this message]
2001-09-26 12:37 ` Richard B. Johnson
2001-09-25 21:43 ` Matti Aarnio
2001-09-27 14:22 ` Pavel Machek
2001-10-02 9:29 ` Vojtech Pavlik
2001-10-02 9:48 ` Pavel Machek
2001-10-02 9:55 ` Vojtech Pavlik
2001-10-04 21:34 ` Rob Landley
2001-10-02 9:56 ` Matti Aarnio
2001-09-26 16:51 ` Alan Cox
2001-09-27 5:26 ` Albert D. Cahalan
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=3BB0F4C8.124B6576@candelatech.com \
--to=greearb@candelatech.com \
--cc=clock@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 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.