Cross-Chip Flow Control via Original Ingress Port Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current switching technologies face challenges in managing data flow across multiple switch devices, particularly when some ports are configured with flow control enabled and others disabled, leading to congestion and incorrect handling of data frames due to the reliance on local ingress port flow control modes rather than the original ingress port modes.
Innovation Solution
A system and method that account for both egress port and original ingress port flow control configurations, using a queue controller to manage cross-chip data flow, ensuring robust and flexible data transfer by considering the flow control modes of both ports.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the queue controller uses the local ingress port flow control mode to manage cross-chip data flow, then the local port can be simplified in operation, but incorrect flow control decisions are made when the original ingress port has different flow control configuration
Solution Approach 1:
The patent introduces a flow control mode tracking mechanism that acts as an intermediary between the local ingress port and the original ingress port. The system tracks the flow control mode of the original ingress port and uses this information to make accurate flow control decisions, thereby resolving the contradiction between local operation simplicity and accurate flow control decisions.
2Reliability
If flow control is enabled on all ports to ensure uninterrupted data frames, then data frame loss is prevented, but system complexity increases due to need to track multiple port modes
Solution Approach 1:
The patent applies local quality by enabling flow control selectively based on the specific conditions of each data flow path. Instead of uniformly enabling flow control on all ports, the system evaluates the flow control mode of the original ingress port and the congestion status of the egress queue to determine whether flow control should be applied, thereby reducing unnecessary complexity while maintaining reliability where needed.
Solution Approach 2:
The system dynamically adjusts flow control behavior based on real-time conditions. The queue controller monitors the flow control mode of the original ingress port and the congestion state of the egress queue, and dynamically decides whether to apply flow control pause or backpressure mechanisms, making the system adaptable rather than static.
3Ease of manufacture
If the queue controller applies flow control based on local ingress port configuration, then implementation is simpler, but cross-chip data flow is mishandled when original ingress port has different configuration
Solution Approach 1:
The patent implements preliminary action by tracking the flow control mode of the original ingress port before the data frame reaches the local egress port. This preliminary tracking allows the queue controller to prepare the correct flow control behavior in advance, ensuring that the data frame receives appropriate handling throughout its journey across multiple chips.
Data Source
AI summary
A system and method of controlling data flow may take into account an egress port flow control configuration as well as an original ingress port flow control configuration. A queue controller may execute a flow control algorithm or a quality of service algorithm responsive to the flow control modes at either or both of the original ingress port and the egress port.