From owner-freebsd-arch Sun Jan 13 17:49: 3 2002 Delivered-To: freebsd-arch@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 1D06337B400 for ; Sun, 13 Jan 2002 17:49:02 -0800 (PST) Received: from pool0611.cvx21-bradley.dialup.earthlink.net ([209.179.194.101] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16PwFA-0007Bs-00; Sun, 13 Jan 2002 17:49:00 -0800 Message-ID: <3C42390A.F9E9F533@mindspring.com> Date: Sun, 13 Jan 2002 17:48:58 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Hurst Cc: arch@freebsd.org Subject: Re: 64 bit counters again References: <3C41F3FD.4ECC8CD@mindspring.com> <20020113231459.GA30349@voi.aagh.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thomas Hurst wrote: > How about keeping them at 32 bit and also counting the number of times > they've overflowed? User level stuff can then do potentially slow 64 > bit ops if needed. And make it adjacent anyway? Maybe using a union to avoid byte/word order issues? This is much less expensive, I think, since the math doesn't go 64 bit, though it does cost another compare, per over just doing 32 bits. My personal opinion is that the utility of the counters is mostly in the examination of small deltas, or delta measurement over intervals (c.v. the recent "sar" discussion); is there a particular reason that making them more expensive to get 64 bits of accuracy is needed to fulfill? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message