Proceedings Real-Time Technology and Applications Symposium
DOI: 10.1109/rttas.1995.516189
|View full text |Cite
|
Sign up to set email alerts
|

Support for real-time computing within general purpose operating systems-supporting co-resident operating systems

Abstract: Distributed multimedia applications are typical of a new class of workstation applications that require realtime communication and computation services to be effective. Unfortunately, there remains a wide gap between the development of real-time computing technology in the research community and the deployment of real-time solutions in commercial systems. In this work we explore technology for allowing two operating systems, a general purpose operating system and a predictable real-time kernel, to co-exist on … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(10 citation statements)
references
References 15 publications
(21 reference statements)
0
9
0
Order By: Relevance
“…The kernel scheduler itself in a general-purpose operating system can be viewed as a hierarchical scheduler: a fixed-priority scheduler implemented in hardware schedules interrupts at the highest overall priority, a (usually) FIFO scheduler runs low-level kernel tasks at the middle priority, and application threads are run at the lowest priority using what is usually thought of as "the scheduler." Furthermore, when the co-resident operating system approach to real-time is used [11,93], the kernel scheduler for a general-purpose OS is no longer the root scheduler; this privilege is taken over by a small hard-real-time OS. …”
Section: Reasons To Use and Understand Hierarchical Schedulingmentioning
confidence: 99%
See 1 more Smart Citation
“…The kernel scheduler itself in a general-purpose operating system can be viewed as a hierarchical scheduler: a fixed-priority scheduler implemented in hardware schedules interrupts at the highest overall priority, a (usually) FIFO scheduler runs low-level kernel tasks at the middle priority, and application threads are run at the lowest priority using what is usually thought of as "the scheduler." Furthermore, when the co-resident operating system approach to real-time is used [11,93], the kernel scheduler for a general-purpose OS is no longer the root scheduler; this privilege is taken over by a small hard-real-time OS. …”
Section: Reasons To Use and Understand Hierarchical Schedulingmentioning
confidence: 99%
“…Very low dispatch latency can be achieved using co-resident operating systems [11,93]. This approach virtualizes the interrupt controller seen by a general-purpose operating system in order to allow a small real-time kernel to run even when the GPOS has "disabled interrupts."…”
Section: Practical Considerationsmentioning
confidence: 99%
“…SMART proposed by Nieh and Monica is a hierarchical CPU scheduling algorithm that supports both hard real time and conventional time sharing applications, adjusts well to overload, and can notify applications when their deadlines cannot be met [7]. Other scheduling work has been done in supporting clients with real-time requirements [8,9] and improving the response time of interactive clients [10,11]. …”
Section: Process Schedulingmentioning
confidence: 99%
“…One where both the real-time and non-realtime processing co-exist on the same platform [13] [12] [14] [15] [16]. The non-real-time processing uses the Windows NT operating system, and all real-time tasks run under a real-time extension to Windows NT.…”
Section: Windows Ntmentioning
confidence: 99%