| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: A case AGAINST checksum offload |
| From: | John Heffner <jheffner@xxxxxxx> |
| Date: | Fri, 12 Nov 2004 19:36:35 -0500 (EST) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20041112154945.63da5103.davem@xxxxxxxxxxxxx> |
| References: | <Pine.LNX.4.58.0411121644150.8989@xxxxxxxxxxxxxx> <20041112154945.63da5103.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 12 Nov 2004, David S. Miller wrote: > The data could just as easily be corrupted on the way to the CPU when > doing a copy+checksum operation. It's the same problem you say exists > with your networking card case except the path of the corruption is > RAM-->CPU instead of RAM-->PCI Controller-->Networking Card > > I really don't buy this. :-) Sure. But we can get a check on one point of failure nearly free. I've measured about a 1% difference in CPU use with checksum on vs. off at 1 gigabit. Probably not a big deal (yeah, somethings buggy anyway and needs to be fixed or replaced), but I thought it worth pointing out. -John |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: A case AGAINST checksum offload, David S. Miller |
|---|---|
| Next by Date: | Re: A case AGAINST checksum offload, David S. Miller |
| Previous by Thread: | Re: A case AGAINST checksum offload, David S. Miller |
| Next by Thread: | Re: A case AGAINST checksum offload, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |