Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!LARRY.CS.WASHINGTON.EDU!randy
From: randy@LARRY.CS.WASHINGTON.EDU (Randy)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: CRC calculation costs (was Re: SLIP working group? )
Message-ID: <8803302136.AA02360@larry.cs.washington.edu>
Date: 30 Mar 88 21:36:42 GMT
References: <QWI7n8y00UoJ41lq40@andrew.cmu.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15

Drew:

I'm interested by your statements that checksuming is a very small part of
the procotcol processing. "Common wisdom" I've always heard, and 
Cabrera et.al. in "User-Process Communication Performance in Networks of
Computers" (IEEE Trans. on Software Eng. Jan. 88) say that data copying and
checksumming are the two biggest components of protocol processing in
BSD4.2 Unix implementations.

Have you done any instrumentation of your code to get performance statistics
of which parts of the protocol processing account for the bottlenecks?

Randy Day.
Internet (ARPA): randy@cs.washington.edu
CSNET: randy%washington@relay.cs.net
UUCP: {decvax|ihnp4}!uw-beaver!uw-june!randy