Bridge-Node NoC Interoperability for DVM and Cache Messaging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network-on-chip (NoC) systems struggle to facilitate communication between different NoCs under various AMBA specifications, particularly in achieving distributed virtual memory operations and other advanced functionalities.
Innovation Solution
A bridge node is introduced in the first NoC to support transactions from multiple channels, and a request node in the second NoC is linked to this bridge node, enabling communication through a protocol that can convey messages such as snoop, cache maintenance, PCIe Ordered Write Observation, and distributed virtual memory messages, while additional user bits are used to carry extra protocol information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a standard NoC protocol is used for linking two different NoCs, then basic communication can be achieved, but advanced functionalities such as distributed virtual memory operations cannot be delivered
Solution Approach 1:
The patent introduces a bridge node as an intermediary component between two different NoCs. This bridge node translates and forwards messages between different NoC protocols, enabling advanced functionalities like distributed virtual memory operations to be delivered across NoC boundaries while maintaining compatibility with standard protocols.
Solution Approach 2:
The bridge node is designed to handle multiple message types including snoop messages, cache maintenance operations, cache stashing messages, PCIe Ordered Write Observations, and distributed virtual memory messages. This multi-functional design allows a single component to support various advanced functionalities across different NoC architectures.
2Adaptability or versatility
If the existing NoC architecture is used without modifications, then device complexity remains low, but the ability to support multiple AMBA specifications and advanced operations is limited
Solution Approach 1:
The patent segments the NoC architecture by introducing a dedicated bridge node that handles protocol translation and message forwarding. This segmentation allows the existing NoC to maintain its simplicity while the bridge node provides the necessary complexity to support multiple AMBA specifications and advanced operations.
Solution Approach 2:
The bridge node acts as an intermediary layer between different NoC domains, handling the complexity of protocol translation and message routing. This isolates the complexity within a single component while keeping the rest of the NoC architecture relatively simple and maintainable.
3Reliability
If protocol messages are extended to carry additional information such as DVM messages and PCIe OWO messages, then functional capability increases, but message protocol complexity increases
Solution Approach 1:
The bridge node serves as an intermediary that manages the complexity of extended protocol messages. It parses, translates, and forwards messages containing additional information such as DVM and PCIe OWO messages, thereby enabling enhanced functional capability while containing protocol complexity within the bridge node rather than spreading it throughout the entire system.
4Adaptability or versatility
If a bridge node is introduced to enable communication between different NoCs, then compatibility and operational efficiency improve, but device complexity increases
Solution Approach 1:
The bridge node is designed as a universal component that can handle multiple message types and protocol translations. By consolidating these diverse functions into a single multi-functional component, the patent improves NoC interoperability while minimizing the increase in overall system complexity compared to having separate dedicated components for each function.
Data Source
AI summary
A network-on-chip (NoC) communication method includes providing a first NoC and a second NoC, determining a protocol of linking the first NoC and the second NoC, setting a bridge node in the first NoC to support transactions from a plurality of channels according to the protocol, setting a request node in the second NoC, and linking the request node to the bridge node for communicating with the bridge node through the plurality of channels. The protocol is capable of conveying at least one of a snoop message, a cache maintenance operation (CMO) message, a cache stashing message, a peripheral component interconnect express (PCIe) Ordered Write Observation (OWO) message, or a distributed virtual memory (DVM) message.