Universal Network Interface Controller for Scalable Switch Fabric
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current server network infrastructures in enterprise and cloud computing lack scalability and symmetrical network throughput, with limited path selection and traffic capabilities extending into servers, relying on single or dual homed Ethernet interfaces and default route associations based on IP addresses.
Innovation Solution
The introduction of a universal network interface controller (UNIC) that extends network fabric into host endpoints, enabling path selection, congestion control, routing, and failover functions, and integrates with switch fabrics and packet networks to minimize switching hops, eliminate deep buffers, and provide virtual output queues for enhanced throughput.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If large multi-stage fabrics are applied to interconnect physical server infrastructure, then network scalability is improved, but network throughput symmetry and path selection capability deteriorate
Solution Approach 1:
The network interface is segmented into two distinct interfaces: a fabric interface for connecting to the switch fabric and a packet interface for connecting to packet networks. This segmentation allows each interface to be optimized for its specific function while working together to provide both scalability and path selection capability. The fabric interface handles high-speed fabric traffic while the packet interface handles traditional packet routing, enabling the system to scale without sacrificing adaptability.
Solution Approach 2:
The network interface is designed with universal functionality to perform multiple roles: it can operate as a fabric interface, a packet interface, or both simultaneously. The interface supports multiple modes of operation including fabric-only mode, packet-only mode, and dual-mode operation. This multi-functionality allows the same hardware architecture to serve different network requirements, providing both scalability through fabric connectivity and path selection through packet routing capabilities.
2Ease of operation
If server interface selection is based on default routes and physical interfaces to source IP addresses, then ease of operation is improved, but network throughput and path selection flexibility deteriorate
Solution Approach 1:
The interface selection mechanism transitions from static default route associations to dynamic path selection based on destination addresses. The network interface dynamically determines whether to forward traffic through the fabric interface or packet interface based on the destination IP address, enabling load balancing and optimized path selection. This dynamic behavior maintains operational simplicity while significantly improving network throughput through intelligent traffic distribution.
3Device complexity
If fabric path selection is not explicitly supported by the server, then device complexity is reduced, but network throughput and congestion control capability deteriorate
Solution Approach 1:
The network interface acts as an intermediary between the server and the network fabric, implementing path selection and congestion control functions at the interface level rather than requiring complex server-side implementation. The interface includes a path selection component that determines the optimal path through the fabric based on destination addresses, and a congestion control component that monitors and regulates traffic flow. This intermediary approach provides advanced throughput optimization without increasing server complexity.
Data Source
AI summary
A universal network interface controller (UNIC) is provided for interfacing a host computer to a switch fabric, a packet network, or both. The UNIC includes ingress transmit logic designed to transmit switch fabric data in memory associated with the host computer to a switch fabric. The UNIC further includes egress receive logic designed to receive switch fabric data from the switch fabric to store the received switch fabric data in the host memory associated with the host computer. As an option, the ingress transmit logic may be further designed to transmit packet network data in memory associated with the host computer to a packet network, such as Ethernet, and the egress receive logic may be further designed to receive the packet network data from the packet network and to store the received switch fabric data and the received packet network data in the host memory associated with the host computer.