All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Kaya, Sinan" <sinan.kaya@siemens.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: periodic bursts
Date: Mon, 01 Oct 2007 19:40:46 +0200	[thread overview]
Message-ID: <4701311E.3000204@siemens.com> (raw)
In-Reply-To: <725A29F6B5035C45A40BDE230A5B92190F8DB322@TRISTK010MSX.tr001.siemens.net>

Kaya, Sinan wrote:
> Hello all,
> My realtime system experiences periodic bursts every 4 hours. How can
> i find the reason for this  ? I know the traceit tool but it dumps
> so much data and it is useless under this case. I need to find what 
> happened at the exact time of burst.

The trace-it tool is a demo, you need to adopt it to your scenario, 
specifically make it trigger the stop once you detected some burst. 
Means, you need to put its code into your application. Did you do this?

> 
> I use rtai_smi module to disable SMI interrupts

Then you will probably like this tool even more:
http://www.rts.uni-hannover.de/rtaddon/#smictrl

> and set my network interface driver priorities to 99. So it should be
> something non maskable but what ?

Out-of-the-box NIC drivers are generally not suited for more than
soft-RT. They allocate memory (skbs) from global pools which takes
varying time (or may even fail if your are short on memory), sometimes
they try to pile up packets first before they raise an IRQ, and they
often contain hardware/link state watchdogs that can inject latencies 
right at the wrong time. If you need low latency by design, more work is 
required.

In any case, understanding this particular problem comes first, and
collecting the right traces will help.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

      reply	other threads:[~2007-10-01 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  6:51 periodic bursts Kaya, Sinan
2007-10-01 17:40 ` Jan Kiszka [this message]

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=4701311E.3000204@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sinan.kaya@siemens.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 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.