Upon reflection, at the point where the 'priming read'
was introduced, any possibility of history distortions
was also eliminated. This was true because all of the
'old' (zeroed) data will have been replaced with 'new'
data whenever a user finally calls get, select & reap.
Thus, any DELTA values will automatically reflect that
interval between 'new' and subsequent retrieval calls.
[ diskstats didn't actually employ a 1st time switch ]
[ like the others so we have changed a comment only. ]
[ but that module will retain something similar used ]
[ inside node_update whenever a new node is created. ]
Reference(s):
. priming read added to slabinfo
commit 5d5a52a3804f912f7be8c15f18bf87fe45bbcd99
. priming read added to diskstats
commit ecd64f444593a0badf6db6a27fcbc46a3888551d
. priming read added to meminfo, stat, vmstat
commit 1a2b62c7793f5f6865eec56a6f996e55495725bf
Signed-off-by: Jim Warner <james.warner@comcast.net>
e524e48138