All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: kus Kusche Klaus <kus@keba.com>
Cc: mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
Date: Thu, 29 Dec 2005 10:25:13 -0800	[thread overview]
Message-ID: <1135880714.19492.5.camel@localhost.localdomain> (raw)
In-Reply-To: <AAD6DA242BC63C488511C611BD51F367323307@MAILIT.keba.co.at>


Do you have any power management features turned on?

I've seen some traces that look like this on buggy intel x86 hardware.
When a small two line function with no loops lasts for 10ms . One of
your traces showed irq_exit() lasting 9ms . It's like the process just
stops.

Daniel

On Thu, 2005-12-29 at 16:08 +0100, kus Kusche Klaus wrote:
> I took some latency traces on our sa1100 (see attachment) running
> 2.6.15-rc7-rt1 with full preemption.
> They look very bad at the first glance, but I cannot interpret them in
> detail.
> 
> Trace 3, 4 and 5 seem to have obvious reasons: FPU emulation,
> Framebuffer console updates, and compression/decompression of flash data
> for jffs2.
> 
> Moreover, if I read these traces correctly, they just disable
> preemption, but still allow interrupts. Is that correct? Can anything be
> done against these latencies, i.e. do they really need to disable
> preemption for such a long time?
> 
> However, traces 1, 2, 6 and 7 are completely mysterious to me.
> Interrupts seem to be blocked for milliseconds, while nothing is going
> on on the system? Moreover, there are console-related function names in
> traces 6 and 7, although I've unconfigured the framebuffer console for
> these runs!
> 
> Many thanks in advance for any help!
> 
> Klaus Kusche
> Entwicklung Software - Steuerung
> Software Development - Control
> 
> KEBA AG
> A-4041 Linz
> Gewerbepark Urfahr
> Tel +43 / 732 / 7090-3120
> Fax +43 / 732 / 7090-6301
> E-Mail: kus@keba.com
> www.keba.com
> 
> 


  reply	other threads:[~2005-12-29 18:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29 15:08 Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) kus Kusche Klaus
2005-12-29 18:25 ` Daniel Walker [this message]
2005-12-30  7:29 ` Lee Revell
2005-12-30  7:36   ` Ingo Molnar
2005-12-30  7:44   ` Ingo Molnar
2005-12-30 13:07     ` Daniel Walker
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30  6:35 kus Kusche Klaus
2005-12-30  7:42 Kai Geek
2005-12-30 18:46 ` Lee Revell
2005-12-30  8:02 kus Kusche Klaus
2005-12-30 10:35 kus Kusche Klaus
2005-12-30 10:59 kus Kusche Klaus
2005-12-30 11:18 kus Kusche Klaus
2005-12-30 12:40 kus Kusche Klaus
2005-12-30 13:35 ` Daniel Walker
2006-01-02  7:57 kus Kusche Klaus
2006-01-02 14:14 ` Daniel Walker
2006-01-02 14:39 kus Kusche Klaus
2006-01-02 14:44 ` Daniel Walker
2006-01-02 14:55 kus Kusche Klaus
2006-01-02 15:36 ` Daniel Walker
2006-01-02 16:07 ` Daniel Walker
2006-01-03  7:27 kus Kusche Klaus
2006-01-03  8:00 kus Kusche Klaus
2006-01-03 14:16 ` Daniel Walker
2006-01-03 14:57 kus Kusche Klaus
2006-01-03 15:01 ` Daniel Walker
2006-01-03 15:40 kus Kusche Klaus
2006-01-04  9:28 kus Kusche Klaus
2006-01-05 14:30 ` Daniel Walker
2006-01-05 15:32 kus Kusche Klaus

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=1135880714.19492.5.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=kus@keba.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 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.