From: Ben Greear <greearb@candelatech.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: RFC: Enabling ethernet drivers to return FCS in the skb?
Date: Wed, 19 Nov 2003 07:33:53 -0800 [thread overview]
Message-ID: <3FBB8D61.6010106@candelatech.com> (raw)
In-Reply-To: <20031119123556.A7622@sygehus.dk>
Rask Ingemann Lambertsen wrote:
> On Mon, Nov 17, 2003 at 01:52:17PM -0800, Ben Greear wrote:
>
>>Is there any interest in adding an Ethtool command to tell the driver to
>>push the extra 4 bytes of CSUM into the skb?
>>
>>When enabling this feature, I'd also like to allow drivers to receive
>>frames with bad FCS as well.
>
> [cut]
>
>>At least some hardware appears
>>to support receiving bad FCS frames (e1000, evidently), but I am not sure
>>how wide-spread this feature is...
>
>
> The Intel i82586 and i82596 and can be told to receive frames with a bad FCS.
> They can also be told to send a precomputed FCS rather than computing it on
> the fly. The i82596 and tulip can also transfer the FCS to memory when
> receiving frames. I guess all of this is also supported on the i82557/8/9.
If you have a patch or example code that shows how to do this, I'd love to
see it. I have code that should RX bad CSUM from the Intel folks, but I can't
get it to generate bad CRC (it does framing errors instead with my attempt),
so I can't test the RX code properly!
I have the path from user-space to the NIC written, so just need to tweak the
drivers a bit...
Do you know if tulip can be told to accept bad FCS and/or if it can generate
a frame with bad FCS somehow?
Thanks!
Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2003-11-19 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 21:52 RFC: Enabling ethernet drivers to return FCS in the skb? Ben Greear
2003-11-19 11:35 ` Rask Ingemann Lambertsen
2003-11-19 13:20 ` Maciej W. Rozycki
2003-11-19 15:33 ` Ben Greear [this message]
2003-11-20 16:34 ` Rask Ingemann Lambertsen
2003-11-23 9:02 ` Ben Greear
2003-11-24 0:05 ` Rask Ingemann Lambertsen
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=3FBB8D61.6010106@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
/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;
as well as URLs for NNTP newsgroup(s).