aboutsummaryrefslogtreecommitdiff
path: root/fs/gfs2/mount.c
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2009-05-10 13:37:36 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2009-05-21 15:44:24 +1000
commit8d165db10772f238103c3e8f955c54145e5c07f3 (patch)
tree54f287e003df92f2d7b237a2382e4f68db9821cd /fs/gfs2/mount.c
parent9aa4e7b1699d0fa197778da96de7e03fa2374f0a (diff)
powerpc: Improve decrementer accuracy
I have been looking at sources of OS jitter and notice that after a long NO_HZ idle period we wakeup too early: relative time (us) event timer irq exit 999946.405 timer irq entry 4.835 timer irq exit 21.685 timer irq entry 3.540 timer (tick_sched_timer) entry Here we slept for just under a second then took a timer interrupt that did nothing. 21.685 us later we wake up again and do the work. We set a rather low shift value of 16 for the decrementer clockevent, which I think is causing this issue. On this box we have a 207MHz decrementer and see: clockevent: decrementer mult[3501] shift[16] cpu[0] For calculations of large intervals this mult/shift combination could be off by a significant amount. I notice the sparc code has a loop that iterates to find a mult/shift combination that maximises the shift value while keeping mult under 32bit. With the patch below we get: clockevent: decrementer mult[35015c20] shift[32] cpu[15] And we no longer see the spurious wakeups. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'fs/gfs2/mount.c')
0 files changed, 0 insertions, 0 deletions