Date: Thu, 27 Sep 2001 22:20:17 -0700 From: Julian Elischer <julian@elischer.org> To: Dan Nelson <dnelson@allantgroup.com> Cc: "Louis A. Mamakos" <louie@TransSys.COM>, Andrew Gallatin <gallatin@cs.duke.edu>, hackers@FreeBSD.ORG Subject: Re: TCP&IP cksum offload on FreeBSD 4.2 Message-ID: <3BB4088E.7B65FDB5@elischer.org> References: <Pine.LNX.4.33.0109270728220.26552-100000@snaresland.acl.lanl.gov> <200109271416.f8REGaZ64624@whizzo.transsys.com> <15283.14648.430630.163513@grasshopper.cs.duke.edu> <200109271631.f8RGVCZ65964@whizzo.transsys.com> <15283.23007.137091.883110@grasshopper.cs.duke.edu> <200109271717.f8RHHBZ66485@whizzo.transsys.com> <20010928000651.C6178@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote:
>
> Something to do would be to enable hardware checksumming on 1/2 your
> machines, and compare the bad packet counts at reported by netstat on
> the unchanged machines for (say) a 1-month period before and after the
> change. That should tell you whether you're gaining or losing
> reliability. It'll be really easy for me, as my current (software
> cksum) stats show no errors at all:
the trouble is that if you are trying to find errors between RAM and WIRE
then the checksums will be correct regardless of whether there is an error..
so the counts you are checking would be no use..
you need to know what the correct packet contents should be..
>
--
+------------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ julian@elischer.org +------>x USA \ a very strange
| ( OZ ) \___ ___ | country !
+- X_.---._/ presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BB4088E.7B65FDB5>