CPS-1616 16-Port Gen2 RapidIO Switch技术规格详解

需积分: 9 7 下载量 200 浏览量 更新于2024-07-15 收藏 2.87MB PDF 举报
"CPS-1616 16-Port, 16-Lane, 80Gbps, Gen2 RapidIO Switch 数据手册" 本文将深入探讨CPS-1616,这是一种基于RapidIO(快速输入/输出)规范(Rev.2.1)的中央包交换器,它在大数据、串口通信、高性能计算以及无线通信等多个领域有广泛应用。CPS-1616由Integrated Device Technology, Inc.制造,并于2017年发布。 核心特性 CPS-1616的核心特性在于其16个双向S-RIO(串行RapidIO)通道,每个通道支持1x, 2x, 和4x宽度,允许每个端口的速率最高可达20Gbps。用户可以根据需求选择6.25, 5, 3.125, 2.5, 或者1.25Gbaud的不同波特率。此外,该设备支持Level I定义的短或长途传输,以及Level II定义的短程、中程和长途传输,确保了不同物理速度下的灵活性。 错误管理与恢复 CPS-1616内置了错误管理扩展功能,支持软件辅助的错误恢复机制,这使得在系统中实现热插拔成为可能,增强了系统的稳定性和可靠性。这种设计允许系统在出现故障时能够快速自我修复,而不影响整个网络的运行。 I2C接口 I2C(Inter-Integrated Circuit)接口是CPS-1616的另一个重要组成部分,提供了用于维护和错误报告的端口。该接口既可以作为主设备,也可以作为从设备,从而在系统监控和调试方面提供便利。 典型应用 1. 高性能计算:在高性能计算环境中,CPS-1616可以高效地分配数据包到多个处理器、数字信号处理器(DSPs)和FPGAs,提升系统的并行处理能力。 2. 无线通信:在无线网络设备中,该交换器能有效地路由数据,优化通信链路,提高网络效率。 3. 国防与航空航天:在这些领域,高带宽、低延迟的通信至关重要,CPS-1616满足了这些严苛的要求。 4. 视频与成像:在视频处理和图像分析应用中,CPS-1616的高速交换能力有助于实时处理大量的图像数据。 CPS-1616是一款功能强大的RapidIO交换器,具备高性能、高可靠性和灵活配置的特性,尤其适用于需要高效数据交换的复杂系统。通过其丰富的端口选项、错误管理功能和适应多种应用场景的设计,CPS-1616在大数据和串口通信领域中扮演着关键角色。

4 Experiments This section examines the effectiveness of the proposed IFCS-MOEA framework. First, Section 4.1 presents the experimental settings. Second, Section 4.2 examines the effect of IFCS on MOEA/D-DE. Then, Section 4.3 compares the performance of IFCS-MOEA/D-DE with five state-of-the-art MOEAs on 19 test problems. Finally, Section 4.4 compares the performance of IFCS-MOEA/D-DE with five state-of-the-art MOEAs on four real-world application problems. 4.1 Experimental Settings MOEA/D-DE [23] is integrated with the proposed framework for experiments, and the resulting algorithm is named IFCS-MOEA/D-DE. Five surrogate-based MOEAs, i.e., FCS-MOEA/D-DE [39], CPS-MOEA [41], CSEA [29], MOEA/DEGO [43] and EDN-ARM-OEA [12] are used for comparison. UF1–10, LZ1–9 test problems [44, 23] with complicated PSs are used for experiments. Among them, UF1–7, LZ1–5, and LZ7–9 have 2 objectives, UF8–10, and LZ6 have 3 objectives. UF1–10, LZ1–5, and LZ9 are with 30 decision variables, and LZ6–8 are with 10 decision variables. The population size N is set to 45 for all compared algorithms. The maximum number of FEs is set as 500 since the problems are viewed as expensive MOPs [39]. For each test problem, each algorithm is executed 21 times independently. For IFCS-MOEA/D-DE, wmax is set to 30 and η is set to 5. For the other algorithms, we use the settings suggested in their papers. The IGD [6] metric is used to evaluate the performance of each algorithm. All algorithms are examined on PlatEMO [34] platform.

2023-05-24 上传

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 14: Invalid parameter "failFast", did you mean "unit"? @ line 14, column 50. eout(time: 48, unit: 'HOURS', failFast: ^ WorkflowScript: 16: Invalid step "parallel" used - not allowed in this context - The parallel step can only be used as the only top-level step in a stages step block @ line 16, column 6. parallel { ^ WorkflowScript: 18: Invalid step "stage" used - not allowed in this context - The stage step cannot be used in Declarative Pipelines @ line 18, column 7. stage('version-A35-2290000204') { ^ 3 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1107) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:624) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:602) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:579) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:323) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:293) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox$Scope.parse(GroovySandbox.java:163) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:190) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:175) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:568) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:518) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:336) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Finished: FAILURE

2023-07-13 上传