From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
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 09:19:53 -0500 [thread overview]
Message-ID: <d120d500041117061998c310b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411161738370.13681@twinlark.arctic.org>
On Tue, 16 Nov 2004 17:50:42 -0800 (PST), dean gaudet
<dean-list-linux-kernel@arctic.org> wrote:
> 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.
>
At least Dell laptops will die horrible death if you enable lapic,
probably others.
--
Dmitry
next prev parent reply other threads:[~2004-11-17 14:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 18:27 [patch] prefer TSC over PM Timer Pallipadi, Venkatesh
2004-11-17 1:50 ` dean gaudet
2004-11-17 10:43 ` Mikael Pettersson
2004-11-17 14:19 ` Dmitry Torokhov [this message]
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=d120d500041117061998c310b@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=dtor_core@ameritech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.