Core Viewpoint - The Unified Bus (UB) protocol aims to bridge the gap between bus and network architectures, addressing the limitations of both in high-performance computing environments, particularly in the context of deep learning and large-scale data processing [2][3][9]. Group 1: Necessity of UB - The necessity for UB arises from the fundamental contradiction in computer architecture between bus and network systems, which have historically operated as isolated entities [2]. - Traditional bus technologies like PCIe offer high performance within a limited physical scope, while network technologies provide scalability at the cost of increased latency and complexity [2][3]. Group 2: Architecture and Design Philosophy - UB's core mission is to create a unified interconnect that combines the ease of programming and performance of bus systems with the scalability of network systems [3]. - The protocol proposes a peer-to-peer architecture where all devices can access each other's memory directly, bypassing the CPU, thus achieving zero-copy data transfer and ultra-low latency [5][6]. Group 3: Key Features of UB - UB provides a unified memory semantic that abstracts the physical differences between bus and network technologies, allowing applications to access remote memory as if it were local [7][8]. - The protocol introduces innovative operations like "Write with Immediate" and "Send with Immediate," which combine data transfer and notification into single atomic operations, reducing overhead [17][18]. Group 4: Jetty Abstraction - The Jetty abstraction replaces traditional connection models with a more flexible, connectionless approach, allowing multiple applications to share resources efficiently [22][23]. - This model simplifies the management of communication states and enhances scalability by treating requests as independent entities rather than requiring dedicated connections [27][28]. Group 5: Transaction Ordering - UB distinguishes between execution order and completion order, allowing for flexible optimization in distributed systems while maintaining consistency [42][45]. - The protocol supports various transaction service modes, enabling applications to choose between performance and consistency based on their specific needs [45].