From: Mikael Pettersson <mikpe@csd.uu.se>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: RE: [patch] prefer TSC over PM Timer
Date: Wed, 17 Nov 2004 11:43:26 +0100 [thread overview]
Message-ID: <16795.11086.38315.444645@alkaid.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.61.0411161738370.13681@twinlark.arctic.org>
dean gaudet writes:
> On Tue, 16 Nov 2004, Pallipadi, Venkatesh wrote:
>
> > I think trying to remove repeated inl()'s in read_pmtmr is a better
> > fix for this issue. As John mentioned in other thread, we should do
> > repeated reads only when something looks broken. Not always.
>
> that would be a nice improvement... then timer_pm will only be 3x as slow
> as timer_tsc instead of 10x slower :) it's still a lot of unnecessary
> overhead for many systems, and unfortunately this is a real performance
> problem (albeit exaggerated by code which is overzealous in its use of
> gettimeofday()).
>
> on a tangent... has the local apic timer ever been considered? it's fixed
> rate, and my measurements show it in the same performance ballpark as TSC.
>
> i know that all p3, p-m, p4, k8 and efficeon have local APIC, but i'm not
> sure if k7 (other than k7 smp parts of course) have local apics... so i'm
> not sure how widespread it is compared to pm-timer.
All K7/K8s except the very first K7 Model 1 have local APICs.
There is no difference between UP and MP parts in this respect.
/Mikael
next prev parent reply other threads:[~2004-11-17 10:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 18:27 Pallipadi, Venkatesh
2004-11-17 1:50 ` dean gaudet
2004-11-17 10:43 ` Mikael Pettersson [this message]
2004-11-17 14:19 ` Dmitry Torokhov
2004-11-17 15:31 ` Alan Cox
2004-11-17 17:48 ` summary (Re: [patch] prefer TSC over PM Timer) dean gaudet
2004-11-17 22:30 ` George Anzinger
2004-11-17 23:09 ` john stultz
2004-11-17 23:24 ` George Anzinger
2004-11-18 2:01 ` [patch] prefer TSC over PM Timer Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 15:08 Pallipadi, Venkatesh
2004-11-16 0:23 dean gaudet
2004-11-16 1:38 ` john stultz
2004-11-16 3:21 ` dean gaudet
2004-11-16 9:50 ` john stultz
2004-11-16 20:29 ` Dominik Brodowski
2004-11-16 21:06 ` john stultz
2004-11-16 8:11 ` Arjan van de Ven
2004-11-16 9:36 ` john stultz
2004-11-17 15:25 ` Alan Cox
2004-11-17 15:25 ` Alan Cox
2004-11-17 17:23 ` Chris Friesen
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=16795.11086.38315.444645@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=dean-list-linux-kernel@arctic.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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®