From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: kernel@kolivas.org
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
bert hubert <bert.hubert@netherlabs.nl>,
linux-kernel@vger.kernel.org, george@mvista.com
Subject: Re: gettimeofday order of magnitude slower with pmtimer, which is default
Date: Tue, 21 Mar 2006 11:59:29 +0900 [thread overview]
Message-ID: <87acbk33la.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <1142901656.441f4b98472e5@vds.kolivas.org> (kernel@kolivas.org's message of "Tue, 21 Mar 2006 11:40:56 +1100")
kernel@kolivas.org writes:
> Quoting OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
>
> 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 <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2006-03-21 2:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 12:24 bert hubert
2006-03-20 14:50 ` Andreas Mohr
2006-03-20 15:24 ` Con Kolivas
2006-03-21 1:26 ` OGAWA Hirofumi
2006-03-21 0:40 ` kernel
2006-03-21 2:59 ` OGAWA Hirofumi [this message]
2006-03-21 3:09 ` Con Kolivas
2006-03-21 8:53 ` Andreas Mohr
2006-03-21 9:06 ` Arjan van de Ven
2006-03-21 11:58 ` Con Kolivas
2006-03-21 12:04 ` Arjan van de Ven
2006-03-21 12:07 ` Con Kolivas
2006-03-21 19:23 ` john stultz
2006-03-21 21:19 ` OGAWA Hirofumi
2006-03-22 0:21 ` Con Kolivas
2006-03-22 18:49 ` [PATCH] PM-Timer: doesn't use workaround if chipset is not buggy OGAWA Hirofumi
2006-03-22 21:46 ` Andrew Morton
2006-03-23 7:31 ` OGAWA Hirofumi
2006-03-23 7:49 ` Andrew Morton
2006-03-23 17:04 ` Andreas Mohr
2006-03-23 18:21 ` OGAWA Hirofumi
2006-03-30 11:53 ` Andreas Mohr
2006-03-30 15:37 ` OGAWA Hirofumi
2006-03-30 16:02 ` Andreas Mohr
2006-03-25 12:00 ` bert hubert
2006-03-22 19:12 ` gettimeofday order of magnitude slower with pmtimer, which is default Avi Kivity
2006-03-22 19:54 ` OGAWA Hirofumi
2006-03-22 20:05 ` john stultz
2006-03-21 19:34 ` john stultz
2006-03-21 5:33 Albert Cahalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87acbk33la.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=bert.hubert@netherlabs.nl \
--cc=george@mvista.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®