Re: kern/54102: Multiple values from "vmstat -s" are broken

[Kamil Rytarowski <n54%gmx.com@localhost>]

The following reply was made to PR kern/54102; it has been noted by GNATS.

From: Kamil Rytarowski <n54%gmx.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/54102: Multiple values from "vmstat -s" are broken
Date: Sat, 6 Apr 2019 23:08:36 +0200

 On 06.04.2019 20:25, Michael van Elst wrote:
 > The following reply was made to PR kern/54102; it has been noted by GNAT=
 S.
 >
 > From: mlelstv%serpens.de@localhost (Michael van Elst)
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: kern/54102: Multiple values from "vmstat -s" are broken
 > Date: Sat, 6 Apr 2019 18:20:19 -0000 (UTC)
 >
 >  n54%gmx.com@localhost writes:
 >
 >  >Multiple values from "vmstat -s" are unreliable and appear to overflow=
 .
 >  >E.g.
 >  >18446744073091529768 pagealloc desired color avail
 >  >18446744072282190447 pagealloc desired color not avail
 >
 >  The kernel uses a signed 'int' to count such events, reports these
 >  as signed 'int64_t' and vmstat prints them as u64. That's true
 >  for a large number of values in uvmextern.
 >
 >  Changing this to use unsigned would be the first thing to do.
 >  64bit values may not be atomic enough on some architectures.
 >
 >
 
 These numbers rather don't need to be super accurate, it just matters to
 reflect the state. Right now part of the values look random and they
 aren't useful for any benchmarking.