All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrice Kadionik <kadionik@enseirb-matmeca.fr>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: preempt rt in commercial use
Date: Wed, 15 Sep 2010 15:56:38 +0200	[thread overview]
Message-ID: <4C90D096.7070301@enseirb-matmeca.fr> (raw)
In-Reply-To: <4C90CF71.2050205@us.ibm.com>

  Le 15/09/2010 15:51, Nivedita Singhvi a écrit :
> Patrice Kadionik wrote:
>
>
>> Hi Nivedita;
>>> I would go further and say people need to stop using the terms
>>> "hard" and "soft". There isn't a binary yes/no answer to the real-time
>>> requirements spectrum.
>>>
>> I don't agree with that.
>> We are all OK to say that the application or the process to control 
>> fixes the timing constraints to the overall HW/SW system.
>>
>> If the application can NEVER miss an event or a deadline because it 
>> will be catastrophic, we MUST use a hard RTOS.
>> If the application supports to miss (from time to time) an event or a 
>> deadline without catastrophic consequence, we can use a soft RTOS (or 
>> a hard RTOS if we want).
>
> No, not really. The consequences may not be catastrophic, but people
> still want performance, latency, determinism, etc. For the majority
> of applications out there, this is true.  And they have specific
> requirements. So they _do_ need to ask, specifically, "can your OS
> do this?".
>
>
>> Not thinking hard nor soft realtime can have dramatic consequences.
>
> I think you missed my point. That's sort of exactly what I'm saying:
oops,

Sorry. I've misunderstood.

Cheers,

Patrice
>
> That customers/users need to think *VERY CAREFULLY* about their
> _specific_ requirements.
>
> i.e., it is never enough to ask "Is it a hard RTOS or soft"?
>
> If you have any specific requirements, the question needs to be:
>
> "can it do xxx in yyy when running zzz in ppp" etc.
>
> Followed by a whole heap of actual testing.
>
> i.e., the answer you get to the first question provides little
> value if you don't know how it is being defined, or worse, it's
> silently being defined differently than what you define it to be.
>
>
>> Until now, PREEMPT-RT is a nice solution as soft RTOS and offers no 
>> guaranty on an very big latency appeared in a particular case. 
>> Thinking that PREEMPT-RT is a hard RTOS is false.
>
> I'm not sure what this means, because most people I know are
> not making any kind of specific claims about PREEMPT_RT.
>
> thanks,
> Nivedita
>


-- 
Patrice Kadionik. F6KQH / F4CUQ
-----------

+----------------------------------------------------------------------+
+"Tout doit etre aussi simple que possible, pas seulement plus simple" +
+----------------------------------------------------------------------+
+ Patrice Kadionik             http://www.enseirb.fr/~kadionik         +
+ IMS Laboratory               http://www.ims-bordeaux.fr/             +
+ ENSEIRB                      http://www.enseirb.fr                   +
+ PO BOX 99                    fax   : +33 5.56.37.20.23               +
+ 33402 TALENCE Cedex          voice : +33 5.56.84.23.47               +
+ FRANCE                       mailto:patrice.kadionik@ims-bordeaux.fr +
+----------------------------------------------------------------------+

--
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

  parent reply	other threads:[~2010-09-15 13:56 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
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 [this message]
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=4C90D096.7070301@enseirb-matmeca.fr \
    --to=kadionik@enseirb-matmeca.fr \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=niv@us.ibm.com \
    /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.