Partition-Based Network Routing for InfiniBand QoS Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large InfiniBand fabrics, the limitation of 48K address space restricts the number of alternative routes for Quality of Service (QOS) in network communication, making it difficult to manage QOS effectively across thousands of nodes.
Innovation Solution
The method involves generating an index value from a destination identifier for network packets, using a routing table to select physical port numbers, and employing a partition key table to determine a direction selector signal for routing, allowing for more efficient route selection and management of network packets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple addresses per node are assigned to provide alternative routes for QOS, then the number of alternative routes increases, but the available address space is quickly consumed within the 48K limit
Solution Approach 1:
The patent segments the routing function into two independent components: a routing table that maps destination identifiers to index values, and a port redirection table that maps index values to multiple physical port numbers. This segmentation allows the system to provide multiple alternative routes without requiring multiple addresses per node, thereby resolving the contradiction between route diversity and address space consumption.
Solution Approach 2:
The patent introduces a new dimension to the routing architecture by adding the index value as an intermediate mapping layer between destination identifiers and physical port numbers. This dimensional change enables the system to expand the number of alternative routes beyond the traditional address space limitation, as the port redirection table can contain multiple port numbers for each index value without consuming additional address space.
2Device complexity
If the address space is limited to 48K, then the system maintains simplicity and standard compliance, but the ability to manage QOS in large fabrics with thousands of nodes is restricted
Solution Approach 1:
The patent segments the routing functionality into distinct tables (routing table and port redirection table) with separate responsibilities. The routing table handles destination identifier to index value mapping, while the port redirection table handles index value to physical port number mapping. This segmentation allows the system to maintain simplicity and standard compliance while enhancing QOS management capability through the additional port redirection layer.
Solution Approach 2:
The patent introduces an index value as an intermediary element between the destination identifier and the physical port number. This intermediary allows the system to decouple the address space limitation from the route selection capability, enabling enhanced QOS management in large fabrics without violating the 48K address space constraint.
3Reliability
If traditional routing methods are used, then the system follows standard protocols, but efficient route selection and multiple path management become difficult in large fabrics
Solution Approach 1:
The patent performs preliminary actions by pre-computing and storing the mapping relationships in two separate tables: the routing table stores destination identifier to index value mappings, and the port redirection table stores index value to multiple physical port number mappings. This preliminary action enables efficient route selection during packet forwarding, as the switch element can quickly retrieve pre-computed routes without performing complex calculations in real-time, thereby improving productivity while maintaining standard protocol compliance.
Data Source
AI summary
Method and system for routing a network packet received at a port within a network is provided. The method includes (a) generating an index value based on a destination identifier for the network packet; (b) generating one or more physical port numbers based on the index value generated in step (a); wherein each port number identifies a port for sending and receiving network packets; and (c) selecting one of the physical port numbers to route the network packet; wherein the port number is selected based on reaction selector signal that is generated from a partition key table based on a partition key value embedded in the network packet.