All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin Steinhoff <armin@steinhoff.de>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Jeff Angielski <jeff@theptrgroup.com>,
	"Nikita V. Youshchenko" <yoush@cs.msu.su>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Raz <raziebe@gmail.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: preempt rt in commercial use
Date: Wed, 15 Sep 2010 09:48:33 +0200	[thread overview]
Message-ID: <4C907A51.1050305@steinhoff.de> (raw)
In-Reply-To: <4C8FF52E.1030407@us.ibm.com>

  Nivedita Singhvi wrote:
> On 09/14/2010 07:49 AM, Jeff Angielski wrote:
>
>>> Isn't any case where preempt-rt does not behave as hard reatlime a 
>>> bug in
>>> preempt-rt, that should be reported to this list and eventually fixed?
>>
>> That is a philosophical question for the preempt-rt maintainers.
>>
>> I *believe* that the design goal for the preempt rt code is to minimize
>> kernel latency. It's not to make the kernel deterministic to support
>> hard realtime.
>
> Er, sort of, not quite.
>
> The design goal of the real-time kernel is most certainly to make the
> kernel more deterministic, to the extent we can in a general-purpose way.
>
> Determinism = capping max latencies.

   Capping max latencies doesn't help without a good real-time, event 
driven scheduler.

   But it helps to classify real-time operatings systems as so called 
hard or soft real-time operating systems.

   IMHO ... there is a common understanding that a RTOS can be 
considered as a hard-reatime OS if the
   max latency is < 15us  because it is able to server 80% (?) of all 
hard real-time applications in the field.
   All others are considered as soft real-time operating systems. From 
this point of view is PREEMPT_RT Linux
   a hard real-time OS ... if the hardware base is appropriate.

   BTW ... we use PREEMPT_RT Linux  as a base for our commercial 
solft-PLC called DACHSview: http://steinhoff-automation.com/Programming.htm

>
> It's better to have all hundred iterations of an operation take
> 45us each than to have 95 iterations take 30us and 5 iterations
> take 75us. You want to be able to say, "this operation will take
> at _most_ 50us" and have that be as true as possible.

   All these numbers have no meaning if you don't specify the hardware 
environment.

   --Armin

   http://www.steinhoff-automation.com



>
> We sacrifice overall throughput (ave latency) for determinism
> (low max latency).
>
> Not sure if that's what you intended to say, but hope that helps.
>
> thanks,
> Nivedita
>
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2010-09-15  7:46 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  8:10 preempt rt in commercial use Raz
2010-09-14  9:04 ` Rolando Martins
2010-09-14  9:10   ` Raz
2010-09-14  9:20     ` Rolando Martins
2010-09-14  9:17 ` Nikita V. Youshchenko
2010-09-14  9:24   ` Raz
2010-09-14  9:44     ` Robert Schwebel
2010-09-14 12:16       ` Armin Steinhoff
2010-09-14 13:04         ` Daniel James
2010-09-14 13:08         ` Pradyumna Sampath
2010-09-14 22:11           ` Nivedita Singhvi
2010-09-14 13:09         ` Klaas van Gend
2010-09-14 13:17         ` David Kastrup
2010-09-14 13:37           ` Darcy Watkins
2010-09-14 13:58         ` Patrice Kadionik
2010-09-14 14:21       ` Jeff Angielski
2010-09-14 14:30         ` Nikita V. Youshchenko
2010-09-14 14:49           ` Jeff Angielski
2010-09-14 22:20             ` Nivedita Singhvi
2010-09-15  7:48               ` Armin Steinhoff [this message]
2010-09-15 14:09                 ` Nivedita Singhvi
2010-09-15 14:45                   ` Pradyumna Sampath
2010-09-16 10:17                     ` Daniel James
2010-09-16 10:35                       ` Pradyumna Sampath
2010-09-16 15:19                       ` Raz
2010-09-15 15:38                   ` David Kastrup
2010-09-15 16:02                     ` Nivedita Singhvi
2010-09-15 16:20                       ` David Kastrup
2010-09-16  0:44                         ` Steven Rostedt
2010-09-16 15:27                           ` Nivedita Singhvi
2010-09-16 17:30                             ` Steven Rostedt
2010-09-16 19:27                               ` Armin Steinhoff
2010-09-16 19:38                                 ` Steven Rostedt
2010-09-15 13:33             ` Thomas Gleixner
2010-09-14 14:44         ` Pradyumna Sampath
2010-09-15 12:48           ` Sergio Ruocco
2010-09-15 12:53             ` Pradyumna Sampath
2010-09-15 14:58             ` Paul E. McKenney
2010-09-15 16:27             ` Sven-Thorsten Dietrich
2010-09-16  0:49               ` Steven Rostedt
2010-09-16  5:06                 ` David Kastrup
2010-09-14 14:56         ` Armin Steinhoff
2010-09-14 15:42         ` Patrice Kadionik
2010-09-14 17:38         ` Gregory Haskins
2010-09-14 22:09           ` Nivedita Singhvi
2010-09-15  6:22             ` Patrice Kadionik
     [not found]               ` <4C90CF71.2050205@us.ibm.com>
2010-09-15 13:56                 ` Patrice Kadionik
2010-09-15 14:08               ` Steven Rostedt
2010-09-14 10:06   ` Klaas van Gend
2010-09-14 11:00     ` David Kastrup
2010-09-14  9:28 ` Pradyumna Sampath
2010-09-14 14:13 ` Reagan Thomas
2010-09-15  7:09   ` AW: " Lukas Redlinger
2010-09-15  3:38 ` jordan
2010-09-15  8:59   ` Klaas van Gend
2010-09-15 11:03     ` TinxCore and PREEMPT_RT Armin Steinhoff
2010-09-16  9:38       ` Armin Steinhoff
2010-09-16 10:18         ` David Kastrup
2010-09-16 11:25           ` Mike Galbraith
2010-09-16 11:51           ` Armin Steinhoff
2010-09-15 14:03     ` preempt rt in commercial use Nivedita Singhvi
2010-09-15 17:29       ` Reagan Thomas
2010-09-16 10:39         ` Daniel James
2010-09-16 20:47           ` jordan
2010-09-16 10:07   ` Daniel James
2010-09-16 20:37     ` jordan

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=4C907A51.1050305@steinhoff.de \
    --to=armin@steinhoff.de \
    --cc=jeff@theptrgroup.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=niv@us.ibm.com \
    --cc=r.schwebel@pengutronix.de \
    --cc=raziebe@gmail.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 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.