From: Nix <nix@esperi.org.uk>
To: John Drescher <drescherjm@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Venkatesh Pallipadi <venki@google.com>,
Damien Wyart <damien.wyart@free.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Fri, 10 Sep 2010 00:57:19 +0100 [thread overview]
Message-ID: <87iq2e8o80.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <AANLkTinSr0xoRrtZ6R+sRyQbf0LXhqBJisQTcdHc+A8+@mail.gmail.com> (John Drescher's message of "Thu, 9 Sep 2010 19:44:55 -0400")
On 10 Sep 2010, John Drescher spake thusly:
>> John, Damien, you seem to be experiencing this: are you using HPET as
>> your clocksource? Do you also have ICH10 82801JIs, or is this more
>> widespread?
>>
> I am not using hpet as my clocksource.
>
> jmd1 ~ # uname -a
> Linux jmd1 2.6.35-std160-amd64 #2 SMP Fri Aug 13 18:42:02 UTC 2010
> x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
> jmd1 ~ # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
Hm, interesting. Perhaps the HPET is needed anyway? (That would explain
why my other system, with identical specs to those above and using tsc
as clocksource, was seeing intermittent problems in this area.)
But 82801JI looks like a common factor.
next prev parent reply other threads:[~2010-09-09 23:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 0:51 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?) Nix
2010-09-06 5:32 ` Damien Wyart
2010-09-06 20:27 ` Nix
2010-09-07 5:36 ` Damien Wyart
2010-09-08 21:24 ` Nix
2010-09-08 21:35 ` John Drescher
2010-09-08 22:25 ` Nix
2010-09-09 22:34 ` [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) Nix
2010-09-09 23:44 ` John Drescher
2010-09-09 23:57 ` Nix [this message]
2010-09-10 0:08 ` John Drescher
2010-09-10 0:14 ` John Drescher
2010-09-10 0:59 ` Artur Skawina
2010-09-10 5:36 ` Damien Wyart
2010-09-10 7:42 ` Nix
2010-09-10 7:47 ` Damien Wyart
2010-09-10 8:37 ` Thomas Gleixner
2010-09-10 9:41 ` Jiri Slaby
2010-09-10 13:22 ` Artur Skawina
2010-09-10 20:13 ` Nix
2010-09-10 20:12 ` Nix
2010-09-14 10:09 ` Thomas Gleixner
2010-09-14 20:17 ` Nix
2010-09-14 22:18 ` Thomas Gleixner
2010-09-14 22:23 ` Artur Skawina
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=87iq2e8o80.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=damien.wyart@free.fr \
--cc=drescherjm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venki@google.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