From owner-freebsd-bugs  Wed May  9  7:42: 9 2001
Delivered-To: freebsd-bugs@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id AF8A437B422; Wed,  9 May 2001 07:42:03 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA19356;
	Thu, 10 May 2001 00:41:52 +1000
Date: Thu, 10 May 2001 00:40:22 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@besplex.bde.org
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: dwmalone@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/27215: when cat'ing /compat/linux/proc/stat, we have negative
 numbers
In-Reply-To: <xzpvgnaha6m.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.21.0105100033380.18886-100000@besplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On 9 May 2001, Dag-Erling Smorgrav wrote:

> Bruce Evans <bde@zeta.org.au> writes:
> > It mainly obscures the bug, by moving obvious overflow after LONG_MAX/100
> > statclock ticks to unobvious overflow after ULONG_MAX/100 statclock ticks.
> > Overflow thresholds for some cases:
> > 
> > i386, stathz = 128: before: 1.94 days; after : 3.88 days
> > alpha, stathz = 1024: before: 2.85 million years; after: 5.71 million years
> 
> Argh.  What are the chances of making cp_time an array of uint64_ts
> instead of longs?  Would that break any existing binary interfaces?

Mainly the "interface" given by the type of cp_time.  systat and vmstat,
etc., depend on it being an array of longs.  systat uses a sysctl to
read the array, but this doesn't help much because it assumes that the
array elements have the same types as in the kernel.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message