Boosting Inter-process Communication with Architectural Support

Abstract

IPC (inter-process communication) is a critical mechanism for modern OSes, including not only microkernels like seL4, QNX and Fuchsia where system functionalities are deployed in user-level processes, but also monolithic kernels like Android where apps frequently communicate with plenty of user-level services. However, existing IPC mechanisms still suffer from long latency. Previous software optimizations of IPC usually cannot bypass the kernel which is responsible for domain switching and message copying/remapping across different address spaces; hardware solutions like tagged memory or capability replace page tables for isolation, but usually require non-trivial modification to existing software stack to adapt to the new hardware primitives. In this paper, we propose a hardware-assisted OS primitive, XPC (Cross Process Call), for efficient and secure synchronous IPC. XPC enables direct switch between IPC caller and callee without trapping into the kernel, and supports secure message passing across multiple processes without copying. We have implemented a prototype of XPC based on the ARM AArch64 with Gem5 simulator and RISC-V architecture with FPGA boards. The evaluation shows that XPC can reduce IPC call latency from 664 to 21 cycles, 14x–123x improvement on Android Binder (ARM), and improve the performance of real-world applications on microkernels by 1.6x on Sqlite3.

A study on impacts of hardware changes on performance of different multithreading libraries based on Gem5

“…• Providing insights and recommendations for choosing an appropriate multithreading library for a given application and hardware platform. In this paper, after introducing the research tool gem5, corresponding auxiliary tools, multithreading libraries and benchmarking strategies, design of experiments is presented [10]. Next, the results of experiments are analyzed and then discussed.…”

High performance microservice communication technology based on modified remote procedure call

“…Nevertheless, this approach introduces new challenges in communication between services because of the different data structures and technology types among the multiple services. Therefore, interprocess communication (IPC) 6 between services has become one of the important challenges facing microservice architecture 7 .…”