From owner-freebsd-arch Sun Jan 13 15:15: 7 2002 Delivered-To: freebsd-arch@freebsd.org Received: from voi.aagh.net (pc1-hart4-0-cust168.mid.cable.ntl.com [62.254.84.168]) by hub.freebsd.org (Postfix) with ESMTP id CB8E137B402 for ; Sun, 13 Jan 2002 15:15:04 -0800 (PST) Received: from freaky by voi.aagh.net with local (Exim 3.34 #1) id 16Ptq7-0007x8-00 for arch@freebsd.org; Sun, 13 Jan 2002 23:14:59 +0000 Date: Sun, 13 Jan 2002 23:14:59 +0000 From: Thomas Hurst To: arch@freebsd.org Subject: Re: 64 bit counters again Message-ID: <20020113231459.GA30349@voi.aagh.net> Mail-Followup-To: arch@freebsd.org References: <3C41F3FD.4ECC8CD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C41F3FD.4ECC8CD@mindspring.com> User-Agent: Mutt/1.3.25i Organization: Not much. X-Operating-System: FreeBSD/4.5-PRERELEASE (i386) X-Uptime: 11:08PM up 24 days, 7:53, 3 users, load averages: 2.01, 2.04, 2.00 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 * Terry Lambert (tlambert2@mindspring.com) wrote: > So it seems to me that the utility of this on 32 bit machines is > incredibly limited (e.g. shell programs). The utility of the counters on anything but, perhaps, dialup, is practically zero, since they reset every 4.2GB - even my single user cable gateway exceeds that in a few days. Even if some things will break (how badly?), I'd rather have potentially useful counters over known useless ones. 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. -- Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/ - It's better to burn out than to fade away. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message