aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorArnd Bergmann <[email protected]>2016-11-10 16:21:20 +0100
committerGreg Kroah-Hartman <[email protected]>2016-11-14 15:56:18 +0100
commitb8cb86fd95bb461c3496e1f4b4083b198c963a9c (patch)
treebf7b28c5c630434b58eb7322031ee8723344a035 /tools/perf/scripts/python
parent46468f03c155eb427c9bad5b54632acbf5ee2dbc (diff)
staging: lustre: ldlm: pl_recalc time handling is wrong
James Simmons reports: > The ldlm_pool field pl_recalc_time is set to the current > monotonic clock value but the interval period is calculated > with the wall clock. This means the interval period will > always be far larger than the pl_recalc_period, which is > just a small interval time period. The correct thing to > do is to use monotomic clock current value instead of the > wall clocks value when calculating recalc_interval_sec. This broke when I converted the 32-bit get_seconds() into ktime_get_{real_,}seconds() inconsistently. Either one of those two would have worked, but mixing them does not. Staying with the original intention of the patch, this changes the ktime_get_seconds() calls into ktime_get_real_seconds(), using real time instead of mononic time. Cc: [email protected] # v4.4+ Fixes: 8f83409cf238 ("staging/lustre: use 64-bit time for pl_recalc") Reported-by: James Simmons <[email protected]> Signed-off-by: Arnd Bergmann <[email protected]> Reviewed-by: James Simmons <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions