[lkml]   [2006]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: gettimeofday order of magnitude slower with pmtimer, which is default
Date writes:

> Quoting OGAWA Hirofumi <>:
> What I mean is that I've seen profiles of the worst (from Andi) showing up to 5%
> cpu time on some workloads! That's a heck of a lot slower than when it's
> latched.

I see. Thanks.

>> + if (unlikely(pmtmr_need_workaround)) {
> I would not put this in an unlikely because on the machines where
> pmtmr_need_workaround is true this will always be true.

Yes. However, if machines uses buggy chip, I guessed TSC/PIT would be
more proper as time source. But probably you are right, timer_pit.c
seems more slow usually (it uses many I/O port).

I'll remove unlikely(), and also will remove "Use other timer source"
from warning.

BTW, this patch is still quick hack.

At least, we would need to check the ICH4 which says in comment.
However, I couldn't find the PM-Timer Errata in ICH4 spec update.

Do you/anyone know about a ICH4 error?
OGAWA Hirofumi <>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-03-21 04:02    [W:0.138 / U:1.000 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site