Figure 3 - uploaded by Mojtaba Sabeghi
Content may be subject to copyright.
Average datalife time for messages with maximum 8 bytes data size  

Average datalife time for messages with maximum 8 bytes data size  

Source publication
Conference Paper
Full-text available
Real-time systems are being used increasingly in control applications such as in automobiles, aircraft and process control. Real-time communication protocols are designed in order to satisfy basic requirements of these systems such as reliability, safety and in time message delivery. One of the most important requirements of such critical systems i...

Contexts in source publication

Context 1
... Figure 3 and 4, results of the average datalife time and invalid data access ratio for messages with size less than 8 bytes are shown. In this case RDM+ and CAN results get closer to each other in both metrics, but RDM+ still obtains better results. ...
Context 2
... still, the effective bandwidth utilization in RDM+ and the longer transmission time in CAN cause the higher update rate of the real-time data in RDM+ [6,18,19]. As it is obvious in Figure 3 and 4, both RDM+ and CAN obtain better results than previous case. The reason is that shorter messages can be delivered faster. ...

Similar publications

Article
Full-text available
More and more, the use of real-time distribution middlewares programmed with high-level languages like Java is becoming of interest for industrial systems because this type of infrastructures reduce development efforts required to both design and maintain complex networked applications. In that way towards having better development tools, this pape...

Citations

Article
Multi-core processing platforms are one of the major steps forward in offering high-performance computing platforms. The idea is to increase the performance by employing more processing elements to perform a job. However, this creates a challenge for both hardware developers who build such systems and software designers who program those platforms. On the hardware side, we can mention the problems on the interconnects management, memory hierarchies complexities and cache coherency problem. While on the software side, problems mainly arise in resource management, resource sharing and synchronization. One more fundamental problem on the software side is the inability to program such platforms with the conventional programming models. This is mainly because programming such platforms requires in-depth knowledge of hardware design. In this dissertation, we address the software side problems by proposing a comprehensive runtime system which is responsible to manage the system resources and resolve all the conflicting issues when accessing computing resources. Furthermore, the runtime system offers the application developers with APIs and system primitives that abstract away the platform dependent details, and provides a consistent programming model. These primitives decouple the process of software development from hardware design and results in the software to be independent of the underlying hardware platform. The proposed runtime system consists of a scheduler, a profiler, a transformer, a JIT compiler and a kernel library. A detailed description of each component is presented and the performance of the whole system as well as the imposed overhead of the component is discussed.