From: Lee Revell <rlrevell@joe-job.com>
To: Voluspa <lista1@comhem.se>
Cc: randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
akpm@osdl.org, len.brown@intel.com, rdreier@cisco.com,
mingo@elte.hu
Subject: Re: [UBUNTU:acpi/ec] Use semaphore instead of spinlock
Date: Fri, 16 Jun 2006 22:57:08 -0400 [thread overview]
Message-ID: <1150513028.26252.28.camel@mindpipe> (raw)
In-Reply-To: <20060616112346.1d2050d0.lista1@comhem.se>
On Fri, 2006-06-16 at 11:23 +0200, Voluspa wrote:
> On Thu, 15 Jun 2006 12:27:03 -0400 Lee Revell wrote:
> > On Thu, 2006-06-15 at 13:03 +0200, Voluspa wrote:
> > > On Wed, 14 Jun 2006 18:14:54 -0700 Randy Dunlap wrote:
> > > > updated version:
> > >
> > > As a user, it's great if this fixes people's keyboards and mice. But it's
> > > not a panacea. Gkrellm reads CPU temperatures from
> > > /proc/acpi/thermal_zone/*/temperature and that disturbs a time-critical
> > > application like mplayer, both when reading normal video and hacked mms:
> > > sound streams (ogg sound is OK, though):
> > >
> >
> > It would be helpful to analyze this with Ingo's latency tracing patch.
>
> Do you mean proper in relation to ubuntu-patched, or just proper?
Not sure, I'm not familiar with the exact reason that reading CPU
temperatures would cause long latencies like this. The latency tracer
can tell you the exact code path responsible.
> And, hmmm,
> I do read a lot of archived lkml threads, but latency tracing patch... Is
> it buried in the -rt set?
It's part of the -rt set and also available broken out for 2.6.16:
http://people.redhat.com/mingo/latency-tracing-patches/latency-tracing-v2.6.16.patch
Lee
next prev parent reply other threads:[~2006-06-17 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 23:08 [UBUNTU:acpi/ec] Use semaphore instead of spinlock Voluspa
2006-06-15 0:26 ` Randy Dunlap
2006-06-15 1:14 ` Randy Dunlap
2006-06-15 5:45 ` Roland Dreier
2006-06-15 11:03 ` Voluspa
2006-06-15 16:27 ` Lee Revell
2006-06-16 9:23 ` Voluspa
2006-06-17 2:57 ` Lee Revell [this message]
2006-06-15 15:40 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-06-14 23:22 Randy Dunlap
2006-06-15 5:38 ` Bongani Hlope
2006-06-20 0:40 ` Andrew Morton
2006-06-20 0:41 ` Randy Dunlap
2006-06-20 1:10 ` Andrew Morton
2006-06-16 14:31 ` Luiz Fernando N. Capitulino
2006-06-16 17:43 ` Randy Dunlap
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=1150513028.26252.28.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@comhem.se \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rdreier@cisco.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