From: Arjan van de Ven <arjan@infradead.org>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: Con Kolivas <kernel@kolivas.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
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 10:06:27 +0100 [thread overview]
Message-ID: <1142931987.3077.50.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060321085352.GA17642@rhlx01.fht-esslingen.de>
On Tue, 2006-03-21 at 09:53 +0100, Andreas Mohr wrote:
> Hi,
>
> On Tue, Mar 21, 2006 at 02:09:50PM +1100, Con Kolivas wrote:
> > On Tue, 21 Mar 2006 01:59 pm, OGAWA Hirofumi wrote:
> > > Yes. However, if machines uses buggy chip, I guessed TSC/PIT would be
> > > more proper as time source.
> >
> > Oh yes but there has been an epidemic of timer problems (fast/slow, lost ticks
> > etc) lately meaning the pm timer is being relied upon more and more.
>
> I think it's reasonable to question whether to use unlikely or not,
> but IMHO omitting unlikely here will not reward well-behaving systems and
> not punish buggy systems, and this doesn't seem quite right from an
> evolutionary point of view
rdtsc is not reliable for any SMP system or any system doing frequency
scaling or C3 state power saving states.
(exception is newest generation processors where that appears to be
changing now)
You can say "but it appears to work on my SMP system".. but are they
still synced after 200 days of uptime? or are they skewed by then by too
much.
next prev parent reply other threads:[~2006-03-21 9:06 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
2006-03-21 3:09 ` Con Kolivas
2006-03-21 8:53 ` Andreas Mohr
2006-03-21 9:06 ` Arjan van de Ven [this message]
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=1142931987.3077.50.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=bert.hubert@netherlabs.nl \
--cc=george@mvista.com \
--cc=hirofumi@mail.parknet.co.jp \
--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®