From: Ben Hutchings <bhutchings@solarflare.com>
To: thomas yang <lampsu@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Ethernet CRC questions
Date: Wed, 30 Dec 2009 17:29:35 +0100 [thread overview]
Message-ID: <1262190575.5685.8.camel@localhost> (raw)
In-Reply-To: <f4f837ab0912300819i5fd35ee4o3e0ff4b16362ba0b@mail.gmail.com>
On Thu, 2009-12-31 at 00:19 +0800, thomas yang wrote:
> >>
> >> Does the Ethernet frame CRC (generate and verify in hardware) make
> >> the TX / RX rate a little smaller , and a longer end-to-end delay ?
> >
> > Relative to what?
> >
>
> Relative to the Ethernet frame without CRC appending / verifying .
>
>
> In IEEE 802.3 standard, all network devices should append/verify CRC?
Not 'should' but 'must'.
> >> Could I disable CRC appending / verifying in the network card driver
> >> on all of my nodes (machines) ?
> >
> > Maybe if you want switches to discard everything you send...
> >
>
> So, I should disable CRC appending / verifying on all kinds of network
> devices in my network?
> In this way I will TX/RX packets more faster ?
You will probably not be able to disable CRC validation on switches
because it is not a sensible thing to do. So if you disable CRC
generation on NICs then your network will notwork.
Really, 32 bit-times is not much to worry about (only 320 ns even at
100M). There are likely to be much bigger sources of latency to attack.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2009-12-30 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 17:17 Ethernet CRC questions thomas yang
2009-12-29 17:39 ` Ben Hutchings
2009-12-30 5:53 ` thomas yang
2009-12-30 6:43 ` Matti Aarnio
2009-12-30 10:37 ` Ben Hutchings
2009-12-30 16:19 ` thomas yang
2009-12-30 16:29 ` Ben Hutchings [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=1262190575.5685.8.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=lampsu@gmail.com \
--cc=netdev@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 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.