{'fraction_non_alphanumeric': 0.022222222222222223, 'fraction_numerical': 0.001932367149758454, 'mean_word_length': 5.203592814371257, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Study and Comparison of the RTHAL-Based and ADEOS-Based RTAI Real-time Solutions for Linux

This paper tries to explain the rationales of two different key infrastructures of real time abstraction interface (RTAI): real time hardware abstraction layer (RTHAL) and adaptive domain environment for operating systems (ADEOS), and also makes a comparison with measurement to help understanding the difference between them. Our study shows that ADEOS as a virtual resource layer can intercept hardware interrupts like RTHAL which is essentially just a data structure. And through measurement, we found that both the RTHAL-based RTAI and the ADEOS-based RTAI offer maximum scheduling latencies in microseconds, while latencies of the latter are all slightly greater than those of the former under different situations. However, these differences are so trivial that ADEOS can be competent to replace RTHAL for RTAI. Moreover, ADEOS can help RTAI solve the patent problem with RTLinux, so it has already replaced RTHAL since RTAI 3.0 actually