You are here: Home / RTLWS 1999-2017 / RTLWS Submitted Papers / 
2022-07-06 - 02:22

Dates and Events:

OSADL Articles:

2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable Open Source real-time Ethernet has been reached

2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available

2016-11-12 12:00

Raspberry Pi and real-time Linux

Let's have a look at the OSADL QA Farm data

2016-09-17 12:00

Preemption latency of real-time Linux systems

How to measure it – and how to fix it, if it's too high?

Real Time Linux Workshops

1999 - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2011 - 2012 - 2013 - 2014 - 2015

15th Real Time Linux Workshop, October 28 to 31, 2013 at the Dipartimento Tecnologie Innovative, Scuola Universitaria Professionale della Svizzera Italiana in Lugano-Manno, Switzerland

Announcement - Call for participation (ASCII)Hotels - Directions - AgendaPaper Abstracts - Presentations - Registration - Abstract Submission - Sponsors - Gallery

Bare Metal Performance, Timekeeping, and Energy Efficiency

Paul McKenney, IBM Linux Technology Center

Real-timee, database, and high-performance computing (HPC) developers have often asked: "Can't you get the kernel out of the way?". Recent adaptive-idle work permits just that: Linux is there when you need it, but if you follow a few simple rules, it is out (almost) of your way otherwise. This approach will provide (almost) bare-metal multicore performance and scalability to databases as well as to HPC and (most importantly) real-time applications. However, timekeeping requires that at least one CPU continue receiving scheduling-clock interrupts in the presence of any non-idle execution, which is simply in appropriate from an energy-efficiency viewpoint. Unfortunately, simple code to determine if all CPUs are idle is not scalable. This talk will give an overview of adaptive idle and outline how to scalably determine whether scheduling-clock interrupts can be shut down across the full system while avoiding any embarrassing time-skew incidents.