Inicio Nosotros Búsquedas
Buscar en nuestra Base de Datos:     
Sólo un registro cumplió la condición especificada en la base de información Bciucla.
Publicación seriada
Referencias AnalíticasReferencias Analíticas
Autor: Stewart, David B. dstewart@eng.umd.edu
Oprima aquí para enviar un correo electrónico a esta dirección ; Khosla, Pradeep K. pkk@cmu.edu
Oprima aquí para enviar un correo electrónico a esta dirección
Título: Mechanisms for Detecting and Handling Timing Errors.
Páginas/Colación: pp.87-93.; 28 cm.; il.
Communications of the ACM Vol. 40, no. 1 January 1997
Información de existenciaInformación de existencia

Resumen
Design and analysis of real-time systems is heavily based on knowing worst-case execution times of periodic threads and periodic servers. However, there has been little research into detecting and handling timing errors. These types of errors, which occur in real-time systems, are failures to meet the timing specifications of the system. Much research in real-time systems focuses on developing scheduling policies that can be used to guarantee that timing errors will not occur. The most common timing error is the missed deadline, where a real-time thread fails to complete its execution on time. Another timing error, which is perhaps just as common but not necessarily as obvious, is the incorrect estimate of execution time. Timing errors are detected jointly by the scheduler and the microkernel. An obvious use of the timing error detection and handling mechanism is to implement soft real-time threads. For example, one scheduling policy may be for a thread that misses deadlines to continue to execute, but to use up the time from its next cycle as wel

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno

Generados por el servidor 'bibcyt.ucla.edu.ve' (3.133.148.31)
Adaptive Server Anywhere (07.00.0000)
ODBC
Sesión="" Sesión anterior=""
ejecutando Back-end Alejandría BE 7.0.7b0 ** * *
3.133.148.31 (NTM) bajo el ambiente Apache/2.2.4 (Win32) PHP/5.2.2.
usando una conexión ODBC (RowCount) al manejador de bases de datos..
Versión de la base de información Bciucla: 7.0.0 (con listas invertidas [2.0])

Cliente: 3.133.148.31
Salida con Javascript


** Back-end Alejandría BE 7.0.7b0 *