Proc论文计划:《TDCS: a new scheduling framework for real-time multimedia OS》（一）-CSDN博客

本文链接：https://blog.csdn.net/z384478961/article/details/108303343

READING TIPS

论文的每一句用不同颜色标示出，可以按句阅读，防止英语不好的同学看到满篇的英文头大
部分单词下带有双虚线，会带有注解，将鼠标悬停会有中文解释
每一部分会有中文注解，但并不是一句一句的翻译，只是对上段英文进行了内容概括描述，顺便加入博主的理解，没有按句翻译，是因为论文重要的是思想，和英文报纸等不太一样
有的论文很长，会分成几篇Blog，标题会标示出。
新手发博，有错误欢迎指出，共同进步

ABSTRACT

The emerging real-time hyper-physical system(CPS), such as autonomous vehicle and live interactive media application, requires time deterministic behaviour. This is challenging to achieve by using the traditional general purpose operating system(GPOS). This paper presents a new design of the real-time operating system scheduling mechanism called ‘time deterministic cyclic scheduling’(TDCS) mainly for live multimedia tasks processing. This new scheduler shares a similar philosophy as classsic cyclic execution but with flexibility and dynamic configuration. This hybrid design is based on both time-reserved based cyclic execution and priority-based pre-emptive scheduling for mixed criticality applicaitons. The simulation results show that this scheduling scheme can achieve predicatable timing behaviour of task delay and jitter under high CPU utilisation. This shows that the proposed scheme is promising for low latency high-performance multimedia censoring tasks that occur in a periodic manner.

随着实时应用的不断发展，比如自动驾驶，可交互的媒体应用等，如果使用传统操作系统来控制的话，在高性能和低延迟的要求下，会有很大的挑战，所以作者提出了一种新的实时调度的操作系统叫做TDCS（时间确定性的循环调度系统），这个时间确定性的意思应该是说一个任务执行的周期是确定的，比如每5s执行一次这样，这个系统的调度策略是混合了时间预留机制和优先级机制，（这两个机制能保证在实时任务调度中，能合理运用时间，又不会让实时任务超时，后面会详细讲），所以该系统对时间确定性的多媒体任务能够实现低延迟和高性能，有着较大的灵活性和可配置性，非常适合于多媒体操作任务，简单说一下什么是实时任务，一般我们日常用的计算机对实时性要求不高，启动个程序卡一点，慢一点不会有什么影响，但是在工业生产中的系统，如果执行的操作卡了，慢了一点点，那么对于工业生产来说，就有可能造成很大的损失，比如钢筋生产该降温的时候程序卡住了（或者CPU再调度别的进程，没执行降温操作），则可能温度过高，发生爆炸。所以实时系统多用于工业生产等场景

Introduction

The trend is to use the digital audio workstation (DAW) to perform live music on stage or as the mixer for the front of the house(FOH) system or as the mixer for in-ear monitoring, because of the versatile functionalities, flexible configurations, and expandability that DAW can achieve. On the other hand, audio processing becomes increasingly multifunctional and complex. It is incorporated with the advancement of computation, digital signal processing (DSP) and networking technologies such as high-resolution multichannel audio processing, feature extraction, machine learning and intelligent audio production.

主要介绍一下数字音频处理的背景，目前数字音频的处理一般使用DAW，可以理解为编程使用的集成IDLE，或者绘图领域使用的PS软件等，这些软件提供了强大的功能，帮助人们方便快捷地处理数字音频，但另一方面，随着技术的发展，现代音频处理也融入了大量的新技术，比如特征提取，机器学习，智能音频生成等等

Using DAW in a live or interactive environment is bounded by the responsiveness and temporalperception of audio signals. Systems are restrained by interactions of the computational components with the physical processes and are commonly referred to as cyber-physical systems(CPS). UsingDAWs in live or with interaction is an example of CPS..

这里主要说了一下使用DAW类软件，虽然功能强大但还是受限于其底层电信号和物理层面的一些限制，这里有个名词是CPS（信息物理系统），简单来讲就是通过传感器等一些设备，将现实物理世界的一些信息和数据传送给计算机，计算机根据程序进行处理，之后返回结果，并作用于真实物理世界，音频处理其实就是CPS的一个例子，因为它收集了真实世界的声音，通过加工，又返回给了真实世界（传说中的百万调音师）

DAWs are the software systems running on a general purpose operating systems (GPOS). Thoughit is widely accepted compared with the real time (RT) system. GPOS does not have timing constraintsor time criticality. However, there are movements of GPOS towards the mixed criticality system. GPOS has been widely used in various pseudo or soft RT situation, such as multimedia live streaming. An OS that deals with the different levels of time criticality is called the mixed criticality (MC) system. It is worth noting the concept of MC implies some trade-off between isolation and integration of resource sharing, whereas systems solely focusing on isolation of tasks are regarded as multiple-criticality systems.

GPOS就是我们常用的操作系统，Windows，Mac，IOS等等，这段大体意思是说我们用的DAWs类软件都是建立在GPOS上的，GPOS并不是实时性操作系统的，但是它确实为了实现实时性，做了很多有进步性意义的措施，在目前，GPOS广泛的用于伪实时和软实时环境中，MC系统，这个是说混合临界系统，意思是一个实时系统中有不同级别的任务，可以理解为优先级，当超时可能发生或者资源不足的时候，优先要让高级别的任务，进行处理。那么在有限时间内（毕竟要尽可能的减少任务超时的情况发生）如何保证所有任务都按时完成（这也是实时系统的本质），这其实是一个资源隔离和集成的平衡问题（不能让高优先的任务独占资源，也不能把资源无限制的放给低优先级的任务）

Most modern commodity GPOS such as Linux, Windows or MacOS all have some sort of hierarchical scheduling schemes that enable real-time tasks to be executed with minimum jitter and latency. Latest Windows OS has six different priority classes. Mac OS has four different priority bands. Linux by defaultuses Completely Fair Scheduler (CFS), but it can be configured to use the real-time scheduling policy such as First in First Out (FIFO), Round Robin (RR) and Earliest Deadline first (EDF) with a priority level of 99..

这段简单说明了一下现在商用的GPOS，使用了层次调度的机制来尽可能的让实时任务减少延迟，本段最后也介绍了几种调度算法（FIFO，RR，EDF）等，看名字都很好理解

Real-time systems are the systems that not only perform computation with logic correctness but also timing correctness. One of the applications of real-time systems is the multimedia systemthat supports low latency ‘live’ audio processing. There are classic real-time schedulers such as Cyclic Scheduling, Rate Monotonic Scheduling (RMS) and EDF. However, there is a trend to have RT extension of GPOS such as real-time Linux, since the wide adoption of using open source GPOS in the industry area. Most modern telecommunication platforms and professional live consoles have embedded Linux with RT extension in them to ensure RT performance.

实时系统除了要保证逻辑运算的准确，同时还要保证执行时间上的准确。目前的一种趋势是在GPOS上集成一些实时功能扩展，比如带有实时扩展的Linux系统，这种系统目前在工业领域也慢慢被使用

However, these modifications may not work for the hard RT system due to the non-deterministicattributes of a file system and device drivers such as the Virtual File System (VFS) framework. That is why traditional RTOS avoids using the file system. To be able to support hard RT in GPOS, one has to rewrite all the file system interfaces and device drivers, such as the proposed work from CMU’s RT Machand RT file system.

上段说了带了实时扩展的GPOS，但是这种系统不适用与硬实时任务，简单说一下硬实时和软实时的区别，软实时任务就是稍微晚点执行，超时一点点也没有关系；硬实时任务就是必须在指定时间执行，不许超时（阎王说你三更，你等不到五更）；不适用的原因主要是GPOS上的非实时性文件系统，读写数据的时候无法保证在规定的时间内读出或写入，为了能在GPOS上运行硬实时任务，则需要重写所有文件系统和设备驱动的接口，改为实时性的

There are fundamental differences between RTOS and GPOS from a design point of view. RTOSis optimised to be the worst case, whereas GPOS is optimised to be the average case; RTOS targetson predictable scheduling, whereas GPOS targets on efficient scheduling; RTOS is simple executive whereas GPOS has a wide range of services; RTOS tries to minimise the latency, whereas GPOS triesto maximise the throughput. The earlier work of hard RT Linux proposed by Yodaiken et al. was done by replacing all ‘cli’, ‘sti’ and ‘iret’ to the soft interrupt macros and using hardware-triggered interrupts to execute hard RT tasks. However, these hard real-time tasks have no access to Linux kernel services.

这里主要说了一下RTOS和GPOS的设计初衷的不同，比较好理解

Other effort tried to emulate RTOS within GPOS to provide soft RT performance. This paper predicts that the GPOS will be more popular for a soft real-time task such as telecommunication and finance transactions. This research direction is interesting since it is reappearing in the contemporary cloud and virtualisation trend.In this paper, we proposed a new set of the OS scheduling framework that is called (TDCS) that is specifically tailored for a real-time multimedia system with trading off mechanism of latency and predictable QoE requirements that aims to achieve the predictability of certain tasks using the systematic design approach. The performance evaluation based on simulation between TDCS and RMS is also given to show the pros and cons of it.