9th annual workshop on
Operating Systems Platforms for Embedded Real-Time applicationsJuly 9, 2013. Paris, France
May 3, 2013:
Submission Deadline (extended!)
May 24, 2013:
June 14, 2013:
Submission of camera-ready papers
July 9, 2013:
SYSGO AG, Germany
Nagoya University, Japan
Björn B. Brandenburg
Max Planck Institute for Software Systems
Hochschule RheinMain University of Applied Sciences
George Washington University
University of Waterloo
University of York
|Tuesday, July 9th 2013|
Keynote Talk by Frederic Weisbecker (Red Hat):
Title: Present and Future of Linux dynticks
Abstract: Linux has been able to stop the tick for a few years now. This feature is known as dynticks. Although it was limited to idle CPUs, this was a great step towards enabling power-saving solutions. Now, the 3.10 Linux Kernel can extend this dynamic tick behavior not only to idle CPUs, but also to busy CPUs. This time, power-saving is not the only target, but rather latency and performance. For now the benefit is mostly to be expected in extreme real-time and High Performance Computing, but it may extend to more general purposes in the long run. This talk aims at diving into dynticks internals and speculates about its future improvements.
Biography: Frederic Weisbecker is a Linux Kernel developer working for Red Hat. His involvement and role in the Linux community has evolved over time: he has been working on tracing with ftrace and perf events subsystems, on timers and dynticks-mode, and he helped to remove the big kernel lock. In 2010, he took up the challenge of disabling the tick interrupt on non-idle processors. Eventually, after many changes and helps from other Linux Kernel developers, his work has been merged into the 3.10 kernel.
|11:30-13:00||Session 1: Implementation and Performance Evaluation
|14:30-16:00||Session 2: Power-Management and Open-Source Projects
|16:30-18:00||Session 3: Resource Sharing and Locking
|17:30-18:00||Discussion and Closing Thoughts|
Research on innovative RTOS architectures and services is a hot topic. Developers of Real-Time Operating Systems (RTOS) are faced with many challenges arising from two opposite needs: extreme optimization of resource usage (processor, energy, network bandwidth, etc.) vs. dynamic configuration and upgrading, flexible scheduling, component-based development and deployment, etc. While real-time systems continue to be used in many small embedded applications, real-time services are being introduced and used in general- purpose operating systems. Notable examples are the various flavors Linux that provide support to time-sensitive applications.
This workshop is intended as a forum for researchers and practitioners of RTOS to discuss the recent advances in RTOS technology and the challenges that lie ahead. The workshop will consist of three categories of submitted papers:
Upon acceptance, a complete version of the paper must be prepared and submitted. All papers will be made available to all participants a week before the workshop so that contributions can be examined prior to the workshop.
Topics include but are not limited to:
Submitted papers should follow the IEEE conference format (2 columns, 10 pt, single-line spacing) and should not exceed the page limit listed above for the three submission categories respectively. On the title page, the submission should clearly state which category of papers the submission is for. Papers may be submitted in either PDF or Postscript format. The papers will be reviewed by the workshop Program Committee. All accepted papers will be made available to all participants one week before the workshop so that contributions can be examined prior to the event.
We want to encourage scientific reproducibility, and discourage redundant work within the community. Thus, code relevant to each submission must be publicly available, and a link to it included in the submission. If you require an exception, please contact the chairs. If your submission does not include an implementation, there are no such restrictions.
Papers should be submitted by using the START Conference Manager system. The system acknowledges receipt of each submission by sending an e-mail to the contact author, and it allows to revise a submission till the deadline.
If a paper is accepted, at least one author should register for the workshop following indications sent in the notification of acceptance, and present the paper at the workshop in person.
To submit a paper, visit the submission page.