All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lewis <andrew-lewis@netspace.net.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Daniel Walker <dwalker@mvista.com>,
	"Eugeny S. Mints" <emints@ru.mvista.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: ARM Linux Suitability for Real-time Application
Date: Thu, 23 Jun 2005 11:44:13 +0800	[thread overview]
Message-ID: <42BA300D.9080106@netspace.net.au> (raw)
In-Reply-To: <20050622182250.A13976@flint.arm.linux.org.uk>

Russell King wrote:
> On Wed, Jun 22, 2005 at 09:52:40AM -0700, Daniel Walker wrote:
> 
>>On Wed, 22 Jun 2005, Russell King wrote:
>>
>>>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.
>>>
>>
>>Aren't FIQ's only on some ARM's ? 
> 
> 
> Yes, but please read the original mail.  I think you'll find my reply
> is completely relevant to the question being posed, which was based
> upon the AT91RM9200 SoC.

Thanks for the suggestions.  The FIQ solutions sounds like the one to 
use.  I'll probably do a little testing sometime in the next few weeks 
to determine the maximum loading I can place on the processor when 
running some of the other peripherals simultaneously.  If I have time 
I'll test the -RT patches as well and post up some numbers for this 
processor.


      reply	other threads:[~2005-06-23  3:44 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
2005-06-22 16:52     ` Daniel Walker
2005-06-22 17:22       ` Russell King
2005-06-23  3:44         ` Andrew Lewis [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=42BA300D.9080106@netspace.net.au \
    --to=andrew-lewis@netspace.net.au \
    --cc=dwalker@mvista.com \
    --cc=emints@ru.mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.