All of lore.kernel.org
 help / color / mirror / Atom feed
* Realtime on top of Adeos (Was: Re: [Adeos-main] [ANNOUNCE] Adeos M2)
@ 2002-07-17 21:44 Timothy_J_Massey/TheModernMerchant
  2002-07-18  1:44 ` Karim Yaghmour
  0 siblings, 1 reply; 2+ messages in thread
From: Timothy_J_Massey/TheModernMerchant @ 2002-07-17 21:44 UTC (permalink / raw)
  To: Philippe Gerum; +Cc: adeos-main

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

Hello!

Quick question:  how does Adeos affect real-time response?  Wouldn't Adeos 
have to be real-time itself, and wouldn't the (guaranteed) latency of 
Adeos be added to the latency of the upper level RTOS?

Tim Massey





Philippe Gerum <rpm@xenomai.org>
Sent by: adeos-main-admin@domain.hid
07/17/2002 05:38 PM

 
        To:     linux-kernel@domain.hid
        cc:     adeos-main@gna.org, 
xenomai-main@domain.hid
        Subject:        [Adeos-main] [ANNOUNCE] Adeos M2
(*) Xenomai is a development framework for real-time systems which
includes a collection of emulators mimicking APIs of traditional RTOS
such as VxWorks, pSOS+ and VRTXsa. These emulators run over a single
"generic" RTOS core which have been ported over Adeos.

[-- Attachment #2: Type: text/html, Size: 1471 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Realtime on top of Adeos (Was: Re: [Adeos-main] [ANNOUNCE] Adeos M2)
  2002-07-17 21:44 Realtime on top of Adeos (Was: Re: [Adeos-main] [ANNOUNCE] Adeos M2) Timothy_J_Massey/TheModernMerchant
@ 2002-07-18  1:44 ` Karim Yaghmour
  0 siblings, 0 replies; 2+ messages in thread
From: Karim Yaghmour @ 2002-07-18  1:44 UTC (permalink / raw)
  To: Timothy_J_Massey/TheModernMerchant; +Cc: Philippe Gerum, adeos-main

Timothy_J_Massey/TheModernMerchant@domain.hid wrote:
> Quick question:  how does Adeos affect real-time response?  Wouldn't Adeos have to be real-time itself, and wouldn't the (guaranteed) latency of
> Adeos be added to the latency of the upper level RTOS?

Adeos doesn't know anything about real-time. All it sees are hardware
resources that client OSes need to share. Currently, Adeos allows the
most basic resource required to run OSes, interrupts, to be shared.
As is done in many nanokernels before it (see Exokernel paper), Adeos
provides for an orderly delivery of hardware resources.

If an RTOS is indeed running on top of Adeos, then it certainly does
have to contend with the fact that Adeos' code will always run before
the RTOS' interrupt handler. This code delivers the interrupts in the
order of domains found in the interrupt pipeline, which is pretty
much up to the system designer. If Linux is first, then it gets it
first. If a kernel debugger is first, then it gets it first. If an
RTOS is first, then it gets if first.

If we are talking about real-time on conceptual grounds, however, note
that "real-time" is not so much an issue of speed as it is an issue of
guaranteed deterministic behavior.

I had some interesting discussions at the OLS with Daniel Phillips about
Adeos. He was pointing out that one interesting application for Adeos
was to run 2 RTOSes side-by-side, each responsible for tasks running at
a different resolution. For example, the first RTOS in the pipeline
would be responsible for tasks that need microsecond resolution, while
the second RTOS in the pipeline would be responsible for tasks that
need millisecond resolution.

Karim

===================================================
                 Karim Yaghmour
               karim@domain.hid
      Embedded and Real-Time Linux Expert
===================================================


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-07-18  1:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-17 21:44 Realtime on top of Adeos (Was: Re: [Adeos-main] [ANNOUNCE] Adeos M2) Timothy_J_Massey/TheModernMerchant
2002-07-18  1:44 ` Karim Yaghmour

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.