linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: "Nikita V. Youshchenko" <yoush@cs.msu.su>
Cc: Vladimir Cotfas <vladc@mantatest.com>,
	linux-rt-users@vger.kernel.org,
	Scott Gilbertson <scottg@mantatest.com>
Subject: Re: Latency Problems with 2.6.31/PREEMPT_RT on a 1.2GHz Celeron
Date: Mon, 21 Dec 2009 05:05:53 -0500	[thread overview]
Message-ID: <4B2F4881.1070203@cfl.rr.com> (raw)
In-Reply-To: <200912211216.20588@zigzag.lvk.cs.msu.su>

On 12/21/2009 04:16 AM, Nikita V. Youshchenko wrote:
>> On 12/18/2009 11:56 AM, Vladimir Cotfas wrote:
>>> All,
>>>
>>> I have a a driver that must process an interrupt every 100 uS without
>>> missing any. I am having latency issues and I am looking for some help
>>> debugging my problem.
>>
>> You'll probably never get this working reliably with the RT kernel.
>> Latencies are more deterministic with the RT kernel but slightly higher.
>> You'll have better luck with a vanilla kernel running your app in run
>> level 4. And then even better luck running on an SMP machine isolating
>> your process and IRQ to a single processor. And stay away from the VGA
>> console. You have better luck with faster hardware too.
> 
> We have seen <20us avg latencies on RT kernel on slower powerpc-based SoC.
> 
> The only problem is that sometimes we got single-shot latency >150 us - 
> that happened when sched tick was running for >100 us with interrupts 
> disabled.
> 

Averages are one thing. Guaranteeing he doesn't miss _any_ and still has
time to do whatever he needs to do before the next one, is different. Local
timer interrupts alone are enough to kill ya.

Mark

  reply	other threads:[~2009-12-21 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <abe060d60912171537j10fe194r5f0cd1aca85475df@mail.gmail.com>
2009-12-18 16:56 ` Latency Problems with 2.6.31/PREEMPT_RT on a 1.2GHz Celeron Vladimir Cotfas
2009-12-19 11:34   ` Mark Hounschell
2009-12-21  9:16     ` Nikita V. Youshchenko
2009-12-21 10:05       ` Mark Hounschell [this message]
2009-12-21 20:36         ` Carsten Emde

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=4B2F4881.1070203@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=scottg@mantatest.com \
    --cc=vladc@mantatest.com \
    --cc=yoush@cs.msu.su \
    /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;
as well as URLs for NNTP newsgroup(s).