public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Eugeny S. Mints" <emints@ru.mvista.com>
Cc: Andrew Lewis <andrew-lewis@netspace.net.au>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	"Dwalker@Mvista. Com" <dwalker@mvista.com>
Subject: Re: ARM Linux Suitability for Real-time Application
Date: Wed, 22 Jun 2005 10:02:31 +0100	[thread overview]
Message-ID: <20050622100231.A28181@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42B92791.9060800@ru.mvista.com>; from emints@ru.mvista.com on Wed, Jun 22, 2005 at 12:55:45PM +0400

On Wed, Jun 22, 2005 at 12:55:45PM +0400, Eugeny S. Mints wrote:
> The bottom line is that interrupt and preemption latencies for a kernel 
> with RT patch are inbetween 15-150us. But of course even with real-time 
> patch you have to perform _real_ fine tuning of your system to achieve 
> such hard constraints you identified.

If you're just after some background process to run off interrupts with
minimal interrupt latency, the good news is that you don't have to modify
the kernel on ARM, and you certainly don't need any RT patches.

If you use the FIQ, then your FIQ latency will be the time it takes the
CPU to enter your FIQ function.  Since the kernel _never_ disables FIQs
in any way, FIQs have ultimate priority over everything else in the
system.

This does mean that you have to be careful if you want data to cross
the boundary between FIQ and the rest of the kernel since you can't use
any of the normal locking functions from FIQ mode.  Also, note that FIQ
code can not reside in modules.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-06-22  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42B8F6FB.2090203@netspace.net.au>
2005-06-22  8:55 ` ARM Linux Suitability for Real-time Application Eugeny S. Mints
2005-06-22  9:02   ` Russell King [this message]
2005-06-22 16:52     ` Daniel Walker
2005-06-22 17:22       ` Russell King
2005-06-23  3:44         ` Andrew Lewis

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=20050622100231.A28181@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=andrew-lewis@netspace.net.au \
    --cc=dwalker@mvista.com \
    --cc=emints@ru.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