From: "K.R. Foley" <kr@cybsft.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt1
Date: Wed, 22 Mar 2006 14:51:54 -0600 [thread overview]
Message-ID: <4421B8EA.3020505@cybsft.com> (raw)
In-Reply-To: <1143048688.9127.2.camel@localhost.localdomain>
Daniel Walker wrote:
> On Wed, 2006-03-22 at 10:10 -0600, K.R. Foley wrote:
>
>> Found something interesting. Having Wakeup latency timing turned on
>> makes a HUGE difference. I turned it off and recompiled and now I am
>> seeing numbers back in line with what I expected from 2.6.16-rt4. Sorry,
>> but I had no idea it would make that much difference. I don't have a
>> complete run yet, but I have seen enough to know that I am not seeing
>> tons of missed interrupts and the highest reported latency thus far is
>> 61 usec.
>
> Just Wakeup latency timing , and not latency tracing ?
>
> Daniel
>
>
Unfortunately I can't say for sure because I don't remember turning it
off, but looking at the log it appears as though latency tracing was
turned on
--
kr
next prev parent reply other threads:[~2006-03-22 20:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 8:51 2.6.16-rt1 Ingo Molnar
2006-03-21 4:24 ` 2.6.16-rt1 K.R. Foley
2006-03-21 21:16 ` 2.6.16-rt1 Ingo Molnar
2006-03-22 2:26 ` 2.6.16-rt1 K.R. Foley
2006-03-22 6:29 ` 2.6.16-rt1 Ingo Molnar
2006-03-22 14:18 ` 2.6.16-rt1 K.R. Foley
2006-03-22 16:10 ` 2.6.16-rt1 K.R. Foley
2006-03-22 17:31 ` 2.6.16-rt1 Daniel Walker
2006-03-22 20:51 ` K.R. Foley [this message]
2006-03-23 3:13 ` 2.6.16-rt1 Steven Rostedt
2006-03-21 13:30 ` 2.6.16-rt1 Serge Noiraud
2006-03-21 13:59 ` 2.6.16-rt1 Jan Altenberg
2006-03-21 17:01 ` 2.6.16-rt1 Ingo Molnar
2006-03-21 18:36 ` 2.6.16-rt1 Michal Piotrowski
2006-03-21 20:24 ` 2.6.16-rt1 Ingo Molnar
2006-03-21 23:22 ` 2.6.16-rt1 Michal Piotrowski
2006-03-22 9:59 2.6.16-rt1 Sébastien Dugué
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=4421B8EA.3020505@cybsft.com \
--to=kr@cybsft.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome