English
Transitioning to multicore processing
Rob Oshana and Shuai Wang, Freescale Semiconductor
EETimes (8/31/2011 4:13 PM EDT)
Hesitating to make the shift from single- to multiple-core processing in your design? Here's a guide to making the transition.
The transition to multicore processing requires changing the software programming model, scheduling, partitioning, and optimization strategies. Software often requires modifications to divide the workload among cores and accelerators, to use all available processing in the system and maximize performance. Here's how you and your team can make the switch.
Networking systems, for example, normally include control-plane and data-plane software (shown in Figure 1). The control plane is responsible for managing and maintaining protocols (such as OSPF, SNMP, IPSec/IKE) and other special functions such as high-availability processing, hot plug and play, hot swap, and status backup. Control-plane functions include management, configuration, protocol hand-shaking, security, and exceptions. These functions are reliability sensitive but not extremely time sensitive. Normally, control-plane data packets/frames only occupy ~5% of the overall system load.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Achieving higher performance in a multicore-based packet processing engine design
- Putting Multicore Processing in Context: Part 2
- Putting multicore processing in context: Part One
- Network require multi-gigabit processing? Try multi-core FPGAs
- Casting a wide safety net through post processing Checking
New Articles
Most Popular
- Streamlining SoC Design with IDS-Integrate™
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- PCIe error logging and handling on a typical SoC