Real-Time Performance and Response Latency Measurements of Linux Kernels on Single-Board Computers

Adam, George K.

doi:10.3390/computers10050064

Cited by 8 publications

(4 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some make a timing analysis of virtualized environments [8,24,25], others analyze the interrupt latency on an OS [26,27], and others analyze the interrupt latency on virtualized environments [28][29][30][31][32][33]. Finally, some propose new tools for analyzing latencies in embedded systems [34][35][36][37][38].…”

Section: Related Workmentioning

confidence: 99%

Interrupt Latency Accurate Measurement in Multiprocessing Embedded Systems by Means of a Dedicated Circuit

Alonso,

Muguira,

Garate

et al. 2024

Electronics

View full text Add to dashboard Cite

Modern multiprocessing embedded applications require, in many cases, two different environments on the same platform: one that meets real-time requirements and another one with a general purpose operating system. Although several technologies can be used, two of the most popular are virtualization based on hypervisors and asymmetric multiprocessing software. However, using these tools introduces latency, which must be measured to verify compliance with real-time requirements. With the aim of facilitating these measurements, this work provides a hardware tool that is more precise and easier to use than other existing software solutions. The paper also studies the interrupt latency generated by different hypervisors and asymmetric multiprocessing frameworks in a Zynq UltraScale+ platform. This research work facilitates the accurate study of the temporal response of multiprocessor embedded systems, which allows for evaluating their suitability for applications with real-time requirements.

show abstract

Section: Related Workmentioning

confidence: 99%

Interrupt Latency Accurate Measurement in Multiprocessing Embedded Systems by Means of a Dedicated Circuit

Alonso,

Muguira,

Garate

et al. 2024

Electronics

View full text Add to dashboard Cite

show abstract

“…2. The reason for using an MCU between the ADC and SBC is to guarantee that certain quick periodic or random events on the signals are sampled in time [20]. For example, the SBC is capable of running Linux, which brings some benefits but also results in some limitations.…”

Section: A Hardware and Data Acquisition Designmentioning

confidence: 99%

A SBC-Based Data Acquisition System: A Case Study on Smart Reclosers and Multiagent Systems

et al. 2023

View full text Add to dashboard Cite

Efficiently handling faults and analyzing signals in power distribution systems is a persistent challenge. Previous studies proposed using smart devices, but most evaluations considered simulated environments. In this paper, we propose a novel approach to address signal acquisition and processing using a single board computer (SBC) to provide more local computational capabilities to reclosers. This paper addresses the challenge of using multiple software programs to digitize signals, monitor faults, and communicate with other reclosers for fault handling. We show the high-level software on the SBC can meet the requirements of the data acquisition system and provide high computational power for various local data processing tasks. The proposed hardware enables real-time signal acquisition with low latency and a reduced probability of sample loss, which is vital for accurate signal detection and analysis. We evaluate our approach in an in-house embedded system with communication capabilities, taking into account the multi-agent approach for handling faults in power distribution systems. Our results demonstrate the proposed system provides signals to the application without sample loss. Regarding noise levels, we measured error lower than 1%, and harmonic distortions smaller than 5% of the 50/60 Hz waveform, indicating minimal circuitry impact. We measured latencies around a few microseconds, which is crucial for fault detection. Finally, we present an evaluation setup that demonstrates an efficient process for restoring energy service in power distribution systems. Therefore, the proposed hardware shows promising performance for smart reclosers and other real-time data acquisition systems that require intensive local computations.

show abstract

“…He demonstrated that the PREEMPT_RT patch overall improves the Linux kernel real-time performance compared to the standard one. The reduced worst-case latencies on such devices running Linux with real-time support could make them potentially more suitable for real-time applications as long as a latency value of about 160 μs, as an upper bound, is an acceptable safety margin [29].…”

Section: Related Workmentioning

confidence: 99%

Measurement of Kernel Preemption Time of Real Time Operating Systems

2023

MCET

View full text Add to dashboard Cite

In a Real Time System, when a high priority task is scheduled, it preempts ongoing lower priority tasks and sometimes it preempts even the kernel too. In normal cases, the time needed for the preemption is too small and hence is not considered in task scheduling. But, in some mission critical hard real time systems, even a small fraction of a second should be taken into account as it could affect the deadline. This research work proposes two models -embedded model and software model, among which the latter has been used for the experiment that calculates the kernel preemption time. The hardware model consists of a triangular wave generator called TRIANG that takes timer values from real time tasks and sends outputs to a comparator module. Finally, the comparator compares the time differences, and hence, calculates the kernel preemption time. Whereas the software model uses the RT-Linux architecture in which device drivers are used instead of hardware components. A high precision timer clock is also used to measure the task release times.The results from the experiments show that the release time jitter due to the kernel preemption is found to be fluctuating in the range of -94 and +93 microseconds in 3% of the cases. So, the kernel preemption time for the hard and mission critical real time systems is taken to be less than 99 microseconds. Whereas 85% of the cases have release time jitters of single digit only. So, the kernel preemption time in average case is considered to be less than 9 microseconds.

show abstract

Real-Time Performance and Response Latency Measurements of Linux Kernels on Single-Board Computers

Cited by 8 publications

References 29 publications

Interrupt Latency Accurate Measurement in Multiprocessing Embedded Systems by Means of a Dedicated Circuit

Interrupt Latency Accurate Measurement in Multiprocessing Embedded Systems by Means of a Dedicated Circuit

A SBC-Based Data Acquisition System: A Case Study on Smart Reclosers and Multiagent Systems

Measurement of Kernel Preemption Time of Real Time Operating Systems

Contact Info

Product

Resources

About