linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Real Time response/latency question
Date: Tue, 30 Nov 1999 10:28:00 -0500	[thread overview]
Message-ID: <3843ED00.20D47DF4@netx4.com> (raw)
In-Reply-To: 19991130034844.1B3E0F380@elph.research.canon.com.au


Graham Stoney wrote:
> 
> Hi folks,
> 
> I'm looking at software architecture questions, and wondering how much
> application domain work I can move out of driver land and into user space,

I believe this is a good programming practice, and in many
cases I don't even write a driver when the application is
allowed to run with root privilege.

> .... Can anyone give me a rough idea of the maximum
> latency in user space I could expect on an 860T based system with multiple
> threads, where only one thread has SCHED_RR realtime scheduling priority?


You can't answer this question due to the design and implementation
of the kernel.  Most "real-time" systems can't either once you
throw protocol stacks, file systems, disk drives, and other
external devices or distributed services into the feature mix.

I have successfully written applications that required
sub-millisecond latency.  You just have to be careful about
other applications in the system, and remember that you can't
preempt the kernel.

If you have hard real-time requirements, check into the RT-Linux
features.  These are starting to mature, and can make scheduling
guarantees within the confined real-time domain.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-11-30 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-30  3:48 Real Time response/latency question Graham Stoney
1999-11-30 15:28 ` Dan Malek [this message]
1999-12-01  0:23   ` Claude Robitaille
1999-12-01  2:18     ` Dan Malek
1999-12-01 15:34   ` Marcus Sundberg

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=3843ED00.20D47DF4@netx4.com \
    --to=dan@netx4.com \
    --cc=greyham@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).