The state of ARM® A 64bit view of what does/doesn't work Andrew Wafaa [email protected]/[email protected] 

2 I am ... • Senior Principal Engineer, Open Source 

3 I am ... • Involved with openSUSE for a long time 

4 I am ... • Known to have questionable fashion choices 

5 I am ... • Known to have questionable fashion choices 

6 I am ... • Known to have questionable fashion choices 

7 I am ... • European 

What am I going to talk about? 

9 Topics • What is AArch64? ‒ AKA ARM64 • Software Status ‒ What’s built, known to work, optimized, broken, missing • Hardware Status ‒ What can you run your software on • How well does it all work ‒ Benchmarking • Next Steps 

What is AArch64? 

11 What is AArch64 • Known in some parts of the world as ARM64 • Part of the ARMv8 architecture • Designed from the ground up • Cortex-A53/57/72 

Software Status 

13 Mostly Working • Almost everything builds 

14 “If it builds, it’s done!” - Anonymous build engineer 

15 AArch64 vs x86_64 

16 Mostly done • The obvious things people care about are done • Number of things that need porting are much smaller ‒ Those that need porting are harder to port 

17 Does it run? • If it has integrated unit tests, then it should run • Much has not been tested • It may not run optimally 

18 What’s been optimized? • Languages ‒ C, C++, Java (OpenJDK 8 & 9), Python, Perl, PHP6, Ocaml, Javascript (v8), Haskell (ghc), Lisp, • Compilers ‒ GCC & LLVM • Kernel ‒ Raid6, crypto • Applications ‒ OpenSSL, Ceph, Hadoop, Xen (much smaller codebase) 

19 What’s the difference between optimized and non-optimized? • Simple example from our friends at Debian using ‘botch’ • Generic ocaml – 4hrs 52m • Native ocaml – 1hr 15m • X86_64 – 37m 

20 Ported but not Optimized • Lua, R, Rust, GoLang, Julia, Perl6, Pascal (fpc), Javascript (Spidermonkey/Ionmonkey), Mono, OpenCV, LibreOffice 

21 “Removing is often better than ‘fixing’ ” - Wookey • 1000 bits of assembler: ‒ https://wiki.linaro.org/Platform/DevPlatform/ArmSoftwareLi st ‒ http://performance.linaro.org/ 

22 What’s missing? • LuaJit to be ported – being worked on ‒ Linaro working with upstream • GoLang SSA backend – being worked on ‒ Expected in GoLang 1.8 • Mono has been ported but not packaged ‒ Most of the unresolvable list are Mono packages 

Hardware Status 

24 No space, no problem • Runabove from OVH ‒ runabove.com using ThunderX • OBS ‒ Mix of Xgene1, Seattle A1100 

25 I have space and I like blinky lights • HP Moonshot • ARM Juno • APM C1 • SoftIron Overdrive 1000, 3000 • Gigabyte MP30, D120, H270, R120, R150, R270 • 96 Boards, HiKey, Dragonboard, Cello • Pine64 • RaspberryPi 3 

26 How much for your blinky lights? • $10,000+ ‒ HP Moonshot 

27 How much for your blinky lights? • $5,000+ ‒ Gigabyte H270 

28 How much for your blinky lights? • $3,000 ‒ Gigabyte R270 

29 How much for your blinky lights? • $2,500 ‒ SoftIron Overdrive 3000 

30 How much for your blinky lights? • $2,500 ‒ Applied Micro XC1 

31 How much for your blinky lights? • $2,500 ‒ Gigabyte R150 

32 How much for your blinky lights? • $2,000 ‒ Gigabyte R120 

33 How much for your blinky lights? • $1,000 ‒ Gigabyte MP30 

34 How much for your blinky lights? • $600 ‒ SoftIron Overdrive 1000 

35 How much for your blinky lights? • $300 ‒ 96Boards Cello 

36 How much for your blinky lights? • $75 - $99 ‒ 96Boards HiKey (1G/2G) 

37 How much for your blinky lights? • $75 ‒ 96Boards Dragonboard 410C 

38 How much for your blinky lights? • $35 ‒ RaspberryPi 3 

39 How much for your blinky lights? • $15 - $30 ‒ Pine64 (0.5G/1G) 

Benchmarking 

41 Benchmarking is difficult • Too easy to game • Need roughly equivalent platforms • Need to look for changes over a period of time • Need to pick a real & common metric • If you know of good benchmarks let me know! 

Questions? 

Thank you. Join the conversation, contribute & have a lot of fun! www.opensuse.org 

44 Have a Lot of Fun, and Join Us At: www.opensuse.org 

General Disclaimer This document is not to be construed as a promise by any participating organisation 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. openSUSE 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 openSUSE products remains at the sole discretion of openSUSE. Further, openSUSE 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 openSUSE marks referenced in this presentation are trademarks or registered trademarks of SUSE LLC, in the United States and other countries. All third-party trademarks are the property of their respective owners. License This slide deck is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license. It can be shared and adapted for any purpose (even commercially) as long as Attribution is given and any derivative work is distributed under the same license. Details can be found at https://creativecommons.org/licenses/by-sa/4.0/ Credits Template Richard Brown [email protected] Design & Inspiration openSUSE Design Team http://opensuse.github.io/branding- guidelines/