Date: Thu, 10 May 2001 00:40:22 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> 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 Message-ID: <Pine.BSF.4.21.0105100033380.18886-100000@besplex.bde.org> In-Reply-To: <xzpvgnaha6m.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0105100033380.18886-100000>