System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPU• one UART for low level debugThe independent, embedded controller for the Power Management (IBMC) allows the monitoring of eachperformance parameters, such as temperatures, voltages, etc. Access to these parameters can be doneby the Power Node applications, locally and remotely over the network. The IBMC provides an SNMPinterface to the Power Node and allows setting traps for specific events. It can also trigger and monitor thePower-On-Self-Test. In terms of remote control, the embedded IBMC permits the remote configuration ofthe Power Node through the network and additional remote configurability can be done through theFPGA.The overall architecture of the Power Node is represented in the next figure.Figure 21 - Power Node architecture: high level description.The FPGA Processor is responsible for some security aspects. It includes a core logic that monitors thesecurity of the Power Node. Tampering with the node triggers a protection mechanism in the securitynode that:• physically disconnects any I/O and network• deletes any data resident on the node• initiates the physical destruction of the device itself by driving the power supplyPUD2.3.2Issue 5 Page 86 of 122
pSHIELDSystem Architecture DesignPU• provides security features such as cryptographic capabilities through a dedicated core embeddedin the FPGA• more in general, the hardware supports the Intel AES-NI technologyThe Power Node architecture has been conceived thinking also “composability”, in order to provide thepossibility to build network of Power Nodes depending on the specific requirements of the specificapplication context. The Infiniband interface allows creating virtual 3D torus networks of Power Nodes,which are very efficient in terms of bandwidth and latency, and are capable of scaling up with noperformance penalty. The torus network is managed by a network processor implemented in the FPGA ofeach Power Node, which interfaces to the system hub through two x8 PCI Express Gen 2 connections, fora total internal bandwidth of 80Gbs. Thanks to the FPGA implementation, the torus network processorpermits standard, ad-hoc and application-dependent collective communications. Finally, the I-O andnetwork interfaces are programmable, in order to permit interfacing the system to multiple network andbus technologies and protocols, increasing in this way the potential scalability of the network.The possibility to aggregate multiple identical units has an impact also on dependability, providingredundancy. The execution segregation through hardware virtualization allows for protection, monitoring,disabling and replacement of malfunctioning or compromised nodes. Moreover, in case of a fault,redundant hardware provides dependable operations. This is accomplished at the hardware level throughduplication of the resource and at a functional level through aggregation of resources (spare PowerNodes).6.1.3.3 Power Node ReconfigurabilityThe capability of the Power Node to reconfigure itself, at runtime, is offered by the use of “in-systemprogrammable” devices such as an FPGA. This means that according to an environmental request, notonly the software libraries can be dynamically loaded, but also the hardware accelerator configuration canbe modified at any time. With configuration we intend the hardware logic previously programmed in theFPGA.As shown in the following image, hardware silicon internal part of the FPGA are based on SRAM LogicElements which consist of combinational logic attached to memory elements and they can be combined toimplement any type of hardware function.Figure 22 – Internal structure of an FPGA logic element.Complex hardware functionalities can be designed with high level hardware description languages suchas VHDL or Verilog or through schematic entry tools provided by development IDE.Once the design has been completed and synthesized, the development tools provide a binary file whichcan be written to the target device (FPGA) to update the configuration to the newer one.PUD2.3.2Issue 5 Page 87 of 122
Page 1 and 2:
Project no: 100204pSHIELDpilot embe
Page 3 and 4:
Contents1 Executive Summary .......
Page 5 and 6:
FiguresFigure 1 - A generic embedde
Page 7 and 8:
Figure 45 - pSHIELD Security Agent
Page 9 and 10:
MGFMIPSMLNeLNFMRFPNMPNMPSNoLNVMOLOS
Page 11 and 12:
Issue 5Page xi
Page 13 and 14:
pSHIELDSystem Architecture DesignPU
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
pSHIELDSystem Architecture Design3.
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
pSHIELDSystem Architecture Design
Page 33 and 34:
Page 35 and 36: pSHIELDSystem Architecture DesignPU
Page 39 and 40: pSHIELDSystem Architecture Design
Page 47 and 48: pSHIELDSystem Architecture Designen
Page 75: pSHIELDSystem Architecture DesignPU
Page 82: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?