ARM SERVER STANDARDIZATION

Transcription

1 ARM SERVER STANDARDIZATION (and a general update on some happenings at Red Hat) Jon Masters, Chief ARM Architect, Red Hat

2 6+ YEARS OF ARM AT RED HAT Red Hat ARM Team formed in March 2011 Bootstrapped ARMv8 architecture for RHEL (and Fedora, and CentOS, etc.) Co-created ARM server industry standards along with Linaro Enterprise Group (LEG) Collaborated with every ARM server chip semiconductor during design and verification Shipped Red Hat Enterprise Linux Server for ARM (Development Preview) Watch this space

3

4 Source: By Dr-text - Datacenter, CC BY-SA 3.0

5

6 Source: By Alan Chia - Lego Color Bricks, CC BY-SA 2.0

7 Source: By Arp -

8

9 Source: ( Open, by Rod Canion)

10 SERVER BASE SYSTEM ARCHITECTURE

11 SYSTEM ON CHIP CPU Core Cluster Interconnect

12 SYSTEM ON CHIP Memory Controller

13 SYSTEM ON CHIP Serdes (PCIe, Fabric, SATA )

14 SYSTEM ON CHIP Workload Customized IP Compression Engine

15 SILICON COMPLIANCE Adherence to the ARM Server Base System Architecture (SBSA) Core compliance is (well) handled by ARM s architecture validation Uncore components sometimes need work (PCIe IP example) PCIe quirks are common across arches but need upstreaming Always design with backward compatibility in mind

16 SERVER BASE BOOT REQUIREMENTS

17

18 FIRMWARE COMPLIANCE Real servers are built using standard platforms. In the ARM community, we defined the ARM Server Base Boot Requirements (SBBR). We use UEFI and ACPI because they offer the necessary pieces for platform abstraction required in general purpose OSes. There is one driver for the Real Time Clock (RTC) in RHEL We have defined interfaces for provisioning ARMv8 servers (not your ARMv8 server), and for upgrading firmware easily over time

19 VALIDATION AND COMPLIANCE

20 OUT OF BOX EXPERIENCE Having a high performance server core isn t the first step to world domination Things need to just work in the way that users already expect them to Unbox, plug into rack, provision via the network using standard tooling Practice good hygiene by giving users a boring experience Use the Linaro Enterprise Reference Platform, other examples as a base

21 WHAT NOT TO DO Don t ship some hack with your custom hacked up distro and kernel of the day Don t ship a special OS for ARMv8 server X that has no upgrade path By all means pre-install an example, but make sure it isn t a hack (if it says it is RHEL it needs to actually be RHEL) If you are unable to avoid a hack, have a good plan and work it through upstream

22 Source: By Rob Young, Bluff Sign Post, CC BY-SA 2.0

23 WORKLOAD OFFLOAD ACCELERATORS Traditional compute tasks replaced with CPU managed data movement to dedicated or reconfigurable accelerators ARMv8 servers integrate many workload accelerators including network packet processors, compression engines, and security/crypto processors Use otherwise dark silicon more effectively (e.g. phone all day battery) Source: Cavium Networks (ThunderX)

24 RECONFIGURABLE COMPUTING FPGAs allow for custom logic to be tailored to a specific VM, attached onchip/package, interconnect (e.g. CCIX) Logically coherent or non-coherent with regard to host system memory Coherent is easier to program (e.g. CUDA) but requires cache snoop hw Non-coherent device memory access using OS DMA primitives Unified Memory (CUDA) (transparent migration), memory hierarchy (OpenCL)

25 RECONFIGURABLE COMPUTING Red Hat Trilby is a simple Red Hat PCIe FPGA platform developed for research Implements a trivial search algorithm (not for high performance) Uses hand-written Verilog, a custom DMA engine, and a custom drivers Interfacing to Apache Spark is possible through a native (JNI) library etc. Red Hat Trilby PCIe-attached FPGA

26

27 ARM SERVER STANDARDIZATION (and a general update on some happenings at Red Hat) Jon Masters, Chief ARM Architect, Red Hat

28 6+ YEARS OF ARM AT RED HAT Red Hat ARM Team formed in March 2011 Bootstrapped ARMv8 architecture for RHEL (and Fedora, and CentOS, etc.) Co-created ARM server industry standards along with Linaro Enterprise Group (LEG) Collaborated with every ARM server chip semiconductor during design and verification Shipped Red Hat Enterprise Linux Server for ARM (Development Preview) Watch this space

29

30 Source: By Dr-text - Datacenter, CC BY-SA 3.0

31

32 Source: By Alan Chia - Lego Color Bricks, CC BY-SA 2.0

33 Source: By Arp -

34

35 Source: ( Open, by Rod Canion)

36 SERVER BASE SYSTEM ARCHITECTURE

37 SYSTEM ON CHIP CPU Core Cluster Interconnect

38 SYSTEM ON CHIP Memory Controller

39 SYSTEM ON CHIP Serdes (PCIe, Fabric, SATA )

40 SYSTEM ON CHIP Workload Customized IP Compression Engine

41 SILICON COMPLIANCE Adherence to the ARM Server Base System Architecture (SBSA) Core compliance is (well) handled by ARM s architecture validation Uncore components sometimes need work (PCIe IP example) PCIe quirks are common across arches but need upstreaming Always design with backward compatibility in mind

42 SERVER BASE BOOT REQUIREMENTS

43

44 FIRMWARE COMPLIANCE Real servers are built using standard platforms. In the ARM community, we defined the ARM Server Base Boot Requirements (SBBR). We use UEFI and ACPI because they offer the necessary pieces for platform abstraction required in general purpose OSes. There is one driver for the Real Time Clock (RTC) in RHEL We have defined interfaces for provisioning ARMv8 servers (not your ARMv8 server), and for upgrading firmware easily over time

45 VALIDATION AND COMPLIANCE

46 OUT OF BOX EXPERIENCE Having a high performance server core isn t the first step to world domination Things need to just work in the way that users already expect them to Unbox, plug into rack, provision via the network using standard tooling Practice good hygiene by giving users a boring experience Use the Linaro Enterprise Reference Platform, other examples as a base

47 WHAT NOT TO DO Don t ship some hack with your custom hacked up distro and kernel of the day Don t ship a special OS for ARMv8 server X that has no upgrade path By all means pre-install an example, but make sure it isn t a hack (if it says it is RHEL it needs to actually be RHEL) If you are unable to avoid a hack, have a good plan and work it through upstream

48 Source: By Rob Young, Bluff Sign Post, CC BY-SA 2.0

49 WORKLOAD OFFLOAD ACCELERATORS Traditional compute tasks replaced with CPU managed data movement to dedicated or reconfigurable accelerators ARMv8 servers integrate many workload accelerators including network packet processors, compression engines, and security/crypto processors Use otherwise dark silicon more effectively (e.g. phone all day battery) Source: Cavium Networks (ThunderX)

50 RECONFIGURABLE COMPUTING FPGAs allow for custom logic to be tailored to a specific VM, attached onchip/package, interconnect (e.g. CCIX) Logically coherent or non-coherent with regard to host system memory Coherent is easier to program (e.g. CUDA) but requires cache snoop hw Non-coherent device memory access using OS DMA primitives Unified Memory (CUDA) (transparent migration), memory hierarchy (OpenCL)

51 RECONFIGURABLE COMPUTING Red Hat Trilby is a simple Red Hat PCIe FPGA platform developed for research Implements a trivial search algorithm (not for high performance) Uses hand-written Verilog, a custom DMA engine, and a custom drivers Interfacing to Apache Spark is possible through a native (JNI) library etc. Red Hat Trilby PCIe-attached FPGA

52