public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: "K.R. Foley" <kr@cybsft.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt1
Date: Wed, 22 Mar 2006 09:31:28 -0800	[thread overview]
Message-ID: <1143048688.9127.2.camel@localhost.localdomain> (raw)
In-Reply-To: <442176EB.1050403@cybsft.com>

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


  reply	other threads:[~2006-03-22 17:31 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             ` Daniel Walker [this message]
2006-03-22 20:51               ` 2.6.16-rt1 K.R. Foley
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
  -- strict thread matches above, loose matches on Subject: below --
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=1143048688.9127.2.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=kr@cybsft.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