Switching Fabric Path Emulation for Cross-Domain EDA Traffic Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing EDA emulators face challenges in emulating data center switching fabric traffic with high-performance distributed processing tasks, as they struggle to efficiently address the challenges of efficiently handling the differences in timing domains and network path emulation, particularly in data center switching environments.
Innovation Solution
A path emulation element is introduced to modify emulated data center traffic, adding timing parameters and impairments to mimic real-world conditions, and is implemented as an inline device or component within the EDA emulator to synchronize timing domains and emulate complex network paths.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a path emulation element is introduced to modify emulated data center traffic and add timing parameters, then the fidelity of network condition emulation is improved, but the device complexity increases
Solution Approach 1:
A path emulation element is introduced as an intermediary component between the traffic generator and the EDA emulator. This element modifies emulated data center traffic by adding timing parameters and impairments to mimic real-world conditions. The intermediary handles the complexity of timing domain synchronization and network path emulation, allowing the main EDA emulator to focus on design verification while achieving high-fidelity network condition emulation.
2Adaptability or versatility
If the EDA emulator and traffic generation system operate in different timing domains, then the adaptability and reusability of the testing system is improved, but the difficulty of coordinating timing synchronization increases
Solution Approach 1:
The path emulation element serves as a timing intermediary that receives traffic from the generation system operating in one timing domain and outputs to the EDA emulator operating in a different timing domain. It handles the conversion and synchronization between timing domains, enabling the loosely coupled architecture to function correctly while maintaining adaptability for both pre-silicon and post-silicon testing environments.
Solution Approach 2:
The path emulation element dynamically adjusts timing parameters such as inter-arrival times, delays, and jitter to account for differences between timing domains. By modifying these parameters, the system achieves proper synchronization and impairment emulation despite operating with loosely coupled components in different timing environments.
3Reliability
If emulated impairments such as delays and dropped packets are added to mimic real traffic conditions, then the realism of the emulation environment is improved, but the complexity of traffic modification increases
Solution Approach 1:
The path emulation element acts as a dedicated intermediary specifically designed to handle traffic modification tasks. It implements impairment functions such as adding delays, introducing packet drops, and applying jitter to emulate real data center switching fabric conditions. By centralizing these modification functions in a specialized component, the system achieves high realism without distributing complexity throughout the entire testing architecture.
Data Source
AI summary
A method for data center switching fabric path emulation in an electronics design automation (EDA) environment includes generating emulated data center traffic. The method further includes, at a path emulation element, modifying the emulated data center traffic to emulate passing of the emulated data center traffic through a data center switching fabric. The method further includes outputting, by the path emulation element, the modified emulated data center traffic to an EDA emulator emulating an electronics design under test. The method further includes receiving and storing a response of electronics design under test to the modified emulated data center traffic.