One-Shot Time Management Analysis in EPOS

One of the tasks of an operating system is to handle time events. Traditionally, time management is based on periodic interrupts from one of the system's hardware timers (ticks). However, this approach has some limitations, as lack of precision, large overhead, and large power consumption. These limitations have motivated the use of non-periodic timers (e.g. one-shot timers), specially in specific-purpose operating systems with timing restrictions, such as embedded, real-time, and multimedia systems. This work presents a comparison between one-shot and periodic time implementations in the time management abstractions in EPOS (embedded parallel operating system). We compare both implementations in terms of memory footprint, number of context switches, number of interrupt handler executions and run time in different execution scenarios.

[1]  Antônio Augusto Fröhlich,et al.  Hardware Mediators: A Portability Artifact for Component-Based Systems , 2004, EUC.

[2]  G. G. Stokes "J." , 1890, The New Yale Book of Quotations.

[3]  Jonathan Walpole,et al.  Supporting time-sensitive applications on a commodity OS , 2002, OSDI '02.

[4]  Antônio Augusto Fröhlich,et al.  Application oriented operating systems , 2001 .

[5]  Wolfgang Schröder-Preikschat,et al.  Scenario Adapters: Efficiently Adapting Components∗ , 2002 .

[6]  Bruce Jacob,et al.  Hardware support for real-time operating systems , 2003, First IEEE/ACM/IFIP International Conference on Hardware/ Software Codesign and Systems Synthesis (IEEE Cat. No.03TH8721).

[7]  P. Druschel,et al.  Soft timers: efficient microsecond software timer support for network processing , 2000, OPSR.

[8]  D. Feitelson,et al.  General-Purpose Timing : The Failure of Periodic Timers , .

[9]  Antônio Augusto Fröhlich,et al.  Operating Systems Portability: 8 bits and beyond , 2006, 2006 IEEE Conference on Emerging Technologies and Factory Automation.