suse and arm - open source conference | susecon · storage and hot/warm/cold storage type...

SUSE® and ARMARM and 64-bit ARM Update 2014

Andrew WafaaPrincipal EngineerARM Ltdandrew.wafaa@arm.com

Dirk MülleropenSUSE ARM TeamSUSEdmueller@suse.com

2

openSUSE® Runs on ...

… your laptop

… your desktop

… your server

3

openSUSE® Runs on ...

… your laptop

… your desktop

… your server

x86

x86x86

Is There More?

5

(open)SUSE® Runs on ...

155,656 x86_64 Cores with 300 TB of RAM

6

SUSE® Runs on ...

9728 ia64 Cores, 30 TB RAM

7

SUSE® Also Runs on ...

2880 Power7 (ppc64) cores

8

SUSE® Runs on Mainframe

IBM zSeries

Nothing More?

10

openSUSE® on This?

11

What About openSUSE® on This?

CuBox-I Cortex A9 (IMX.6), 1GB RAM

12

openSUSE® on “Supercomputers” ;-)

•

13

ARM and Servers?

14

Data Centers are Evolving

Today Next 3 Years 5 Years +

Throughput Workloadoptimized

Total costof

ownership

Data center workload characteristics are scaling out

15

ARM and Servers?

•

What is ARM?

17

What is ARM?

• Most popular CPU architecture:

‒ More than 40,000,000,000 CPUs are ARM based

‒ 16,000,000 processors sold every day

• “Low power leadership”

• Optimized for “System on a Chip”

18

System on Chip

19

System On Chip

20

System On Chip

21

System On Chip

22

System On Chip

23

System On Chip

SoC

24

ARM's “Cortex – A“ Series

ARMv8 (A57/A53)

ARMv7 (A15/A7)

ARMv7 (A8/A9)

25

ARM v5/6/7/8

VFPv2

Jazelle

ARMv5 ARMv6 ARMv7-A/R ARMv8-A

Thumb-2

TrustedZone

SIMD

VFPv3/v4

NEONAdv SIMD

A32+T32 ISAsIncluding:• Scalar FP

(SD and DP)

• Adv SIMD(SP Float)

AArch32

CRYPTO CRYPTO

A64 ISAIncluding:• Scalar FP

(SD and DP)

• Adv SIMD(SP & DP Float)

AArch64

Key featureARMv7-A

compatibility

ARM in the Enterprise

27

Target Workloads

• Storage– SDS (Ceph/OrangeFS)

• Scale out (Hyperscale)– Cloud– Big Data– HPC

• Networking– NFV– SDN– Base stations– Routers

• Web– Gateways/Frontends

28

Faster CPU is Better!

• High CPU power is not needed everywhere

‒ Static web serving/CDN, caching

‒ Batch analytics / “Big data”

‒ Cloud, dynamic web content serving (to some extend)

‒ Block storage, warehousing/cold,

29

Pick Your BattlesOne Size Does Not Fit All

0% 25% 50% 75% 100%

Web NoSQL/Big Data

Hosting – Static content

Hosting – Dynamic content

Caching

Front-end Load Balancing, Proxy

Social Media Content

Email

Web: Light SQL

Distributed Block Storage

Cold Storage

IO MEM CPU

30

Server Ecosystem - ODM

31

Server Ecosystem - OEM

32

Does My Workload Run on ARM?

• Java - OpenJDK & Oracle JVM

• Web - Apache / NGINX / NodeJS*

• Virtualization - KVM & Xen

• DataBase - Postgres / MariaDB / MySQL / MongoDB* / CouchDB

• Containers - LXC & Docker*

• Big Data - Hadoop

• Storage - Ceph

33

Is It A Pipe Dream?

• Used in the real world on HP Moonshot by:

– Paypal - Distributed Apache Flume

– Sandia National Labs - Green Exascale HPC

ARM Server Hardware Overview

35

Why ARM Servers ? Why now?

http://www.google.com/about/datacenters/

36

Why ARM Servers? Why now?

http://www.google.com/about/datacenters/

• Workload optimized solutions significantly increased TCO

– One size doesn’t fit all (anymore) – TCO is king at large scale

– New workloads and scale forced re-evaluation of what’s optimal

37

Why ARM Servers? Why now?

http://www.google.com/about/datacenters/

• Value chain is seeking increased innovation and choice

– Many ARM solutions coming to market - competition is healthy!

– Faster innovation needed by cloud & web leaders

38

Why ARM Servers? Why now?

http://www.google.com/about/datacenters/

• ARM business model enables innovation & differentiation

– It’s not just about a low power core – it’s what you put around it

– ARM cores already used in networking & storage components

– Experts in those fields can leverage their existing IP

39

ARM Server Hardware Overview

40

AMD ‚Seattle‘ @ OCP V - 01/2014

42

HP Moonshot System

Static & dynamic web Data mining, analyticsMobile Apps eCommerce,eBusiness

Online gaming Streaming media

Online sharing and collaboration

The new style of IT drives business revenue

HP Moonshot System

Software defined servers45 individually serviceable hot-plug cartridges

Moonshot 1500 ChassisSupports shared components including

power, cooling, and management and fabric

43

Increased Density – Reduced TCO

8.27”

2.9”

19”

26”

44

Cavium „Thunder-X“

• Up to 48 64-bit ARM cores @ 2.5 GHz

• Up to 1 TB RAM

Up to 48 2.5GHzARM64 Cores

16MBCache

SubSyste

m

Cavium CoherentProcessor Interconnect (CCPI™)Workload AcceleratorsOther IO

Ethernet Fabric

Up to 4x 72-bit DDR3/4

ControllersPCIe Gen3 PCIe Gen3 PCIe Gen3

SATAv3

40 GbE/100 GbE40 GbE/

100 GbE10/40100GbE

Security

45

Cavium „Thunder-X“

Cloud, Web Serving

Secure Web Frontend Servers

Telecommunication Servers

Distributed Storage

46

Hardware Working for You

• ThunderX_CP™: Up to 48 highly efficient cores along with integrated virtSOC, dual socket coherency, multiple 10/40 GbE and high memory bandwidth. This family is optimized for private and public cloud web servers, content delivery, web caching, search and social media workloads.

• ThunderX_ST™: Up to 48 highly efficient cores along with integrated virtSOC, multiple SATAv3 controllers, 10/40 GbE & PCIe Gen3 ports, high memory bandwidth, dual socket coherency, and scalable fabric for east-west as well as north-south traffic connectivity. This family includes hardware accelerators for data protection/ integrity/security, user to user efficient data movement (RoCE) and compressed storage. This family is optimized for Hadoop, block & object storage, distributed file storage and hot/warm/cold storage type workloads.

• ThunderX_SC™: Up to 48 highly efficient cores along with integrated virtSOC, 10/40 GbEconnectivity, multiple PCIe Gen3 ports, high memory bandwidth, dual socket coherency, and scalable fabric for east-west as well as north-south traffic connectivity. The hardware accelerators include Cavium’s industry leading, 4th generation NITROX and TurboDPI technology with acceleration for IPSec, SSL, Anti-virus, Anti-malware, firewall and DPI. This family is optimized for Secure Web front-end, security appliances and Cloud RAN type workloads.

• ThunderX_NT™: Up to 48 highly efficient cores along with integrated virtSOC, 10/40/100 GbEconnectivity, multiple PCIe Gen3 ports, high memory bandwidth, dual socket coherency, and scalable fabric with feature rich capabilities for bandwidth provisioning , QoS, traffic Shaping and tunnel termination. The hardware accelerators include high packet throughput processing, network virtualization and data monitoring. This family is optimized for media servers, scale-out embedded applications and NFV type workloads.

SUSE® and ARM

48

openSUSE® Runs on ...

49

openSUSE® Runs on ...

… your laptop

… your desktop

… your server

x86

x86x86

50

ARM-based Machines

Smartphones

Tablets Tiny laptops

Cloud nodes and Low-Energy Servers

Netbooks

51

ARM-based Machines

Smartphones

Tablets Tiny laptops

Cloud nodes and Low-Energy Servers

Netbooks

52

openSUSE® on ARM Team

Virtual team of technical experts from SUSE® and the openSUSE community

GO!

Strong collaboration with technology providers

Started in Q3/2011

53

openSUSE 12.3ARM release

openSUSE 12.3AArch64 (port)

openSUSE® on ARM Timeline

openSUSE 13.1ARMv7 and ARMv8

20152014March 5

April 10

openSUSE 13.2ARM release

Nov

2013Nov 19th

54

openSUSE® Enabled Platforms

Foundation Model

55

Challenges

• Booting

• Deployment

56

Booting on x86

FirmwareBootloader

Kernel

OS

Grub 2

57

Booting on ARM

• Firmware is part of OS, not of hardware

• Sometimes hardware specific kernel

• Operating system with customizations

58

32-bit ARM Booting

• Many U-Boots

• Many Kernels

• One RepositoryOS

U-Boot

Kernel

OS

U-Boot

Kernel

OS

U-Boot

Kernel

OS

U-Boot

Kernel

OS

U-Boot

Kernel

OS

U-Boot

Kernel

59

32-bit ARM Booting with Multiarch

• Many U-Boots

• Many FDTs

• One Kernel

• One RepositoryOS

U-Boot

Kernel

+ FDT

OS

U-Boot

Kernel

+ FDT

OS

U-Boot

Kernel

+ FDT

OS

U-Boot

Kernel

+ FDT

OS

U-Boot

Kernel

+ FDT

OS

U-Boot

Kernel

+ FDT

60

64-bit ARM Booting

• One Kernel

• One Repository

• One Distribution

OS

Kernel

UEFI

61

Challenges

• Booting

• Deployment

openSUSE®, ARM, and Kiwi

63

Deployment Challenges

• Most ARM hardware does not have a CD drive

64

Deployment Challenges

• Single install media is currently not possible‒ Special bootloader for each SoC needed

‒ Kernel is also often still device specific

65

Deployment Solution

• Extended KIWI with extra targets for ARM‒ “Generic” Chroot target

‒ SoC specific u-boot based Appliances

66

Challenges

• Booting

• Deployment

67

Does It Run?

http://www.flickr.com/photos/alorenzi/6277701171

+YES!

68

Raspberry Pi

69

Samsung “Chromebook”

70

BeagleBoard.org

71

Pandaboard.org

72

Exynos 5 boards

73

64 bit ARM Server

75

Anything Else?

We're working on some other devices as well

You can help!‒ Test our machine images

‒ Provide us test hardware

‒ Help us with missing pieces for your individual device!

openSUSE® on ARMStatus and Outlook

77

openSUSE® 13.2

• ARMv6, ARMv7 and AArch64 is available

• Ready-to-use images are available for a few boards

• More will be added over the coming weeks

Question & Answer

79

Call to action line oneand call to action line twowww.calltoaction.com

80

Thank you

http://en.opensuse.org/Portal:ARM

opensuse-arm@opensuse.org

Unpublished Work of SUSE. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.