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 commit5d5a52a380. priming read added to diskstats commitecd64f4445. priming read added to meminfo, stat, vmstat commit1a2b62c779Signed-off-by: Jim Warner <james.warner@comcast.net>
54 KiB
54 KiB