News for hackers. Stuff that matters.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by ac29 on Monday November 26, 2018 @11:42PM (#18539442)
Any idea what ARM cores these are based on? A5x? A7x?

A76 would be pretty interesting...

Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by sidereal on Monday November 26, 2018 @11:49PM (#18539479)
Looks like A72. Here's the cpuinfo:

  processor	: 0
  BogoMIPS	: 166.66
  Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
  CPU implementer	: 0x41
  CPU architecture: 8
  CPU variant	: 0x0
  CPU part	: 0xd08
  CPU revision	: 3
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by ac29 on Tuesday November 27, 2018 @12:15AM (#18539608)
Too bad, A72 is the sort of thing found in $49 SBC's these days. For the price, it would have been nice to see at least A73, but at least its not an A53.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by wmf on Tuesday November 27, 2018 @01:11AM (#18539898)
A73 isn't for servers and I don't see any server/embedded SoCs with A75 yet, so Amazon isn't exactly behind.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by ac29 on Tuesday November 27, 2018 @01:34AM (#18540015)
True, most server ARM processors that come to mind are custom (or at least semi-custom): Ampere, Centriq, ThunderX2. Trying to map them to A72/73/75/76 is perhaps short sighted since those are primarily smartphone cores - we'll have to wait and see how they perform in real world tests.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by floatboth on Tuesday November 27, 2018 @01:39PM (#18545236)
> at least its not an A53

Indeed. A72 is like the minimum viable core :) It's no eMAG or ThunderX2, but it's kinda comparable to the original ThunderX.

Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by baybal2 on Tuesday November 27, 2018 @12:54AM (#18539808)
Jeff has to make take his cut from somewhere after all
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by StillBored on Tuesday November 27, 2018 @05:37PM (#18547517)
Probably should have done a lscpu instead. On recent arm distro's lscpu knows how to decode the part/variant/etc and it also pays attention to the cache and numa topology.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by mrslave on Tuesday November 27, 2018 @06:07AM (#18541318)
What does cpuinfo display when the CPU lacks the cpuid feature?
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by Liquid_Fire on Tuesday November 27, 2018 @08:19AM (#18542040)
Arm processors don't have a cpuid instruction, but they do have a number of ID registers that provide similar information (e.g. MIDR_EL1, REVIDR_EL1).
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by dis-sys on Tuesday November 27, 2018 @01:31AM (#18539997)
lscpu output:

Architecture: aarch64

Byte Order: Little Endian

CPU(s): 8

On-line CPU(s) list: 0-7

Thread(s) per core: 1

Core(s) per socket: 4 Socket(s): 2

NUMA node(s): 1

Vendor ID: ARM

Model: 3

Model name: Cortex-A72

Stepping: r0p3

BogoMIPS: 166.66

L1d cache: 32K

L1i cache: 48K

L2 cache: 2048K

NUMA node0 CPU(s): 0-7

Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid

Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by oavdeev on Tuesday November 27, 2018 @03:27AM (#18540551)
Here's lstopo output for the largest one, for good measure: https://instaguide.io/info.html?type=a1.4xlarge#tab=lstopo though there's nothing terribly surprising.
Re:EC2 Instances Powered by Arm-Based AWS Graviton Processors by StillBored on Tuesday November 27, 2018 @05:40PM (#18547542)
That seems unlikely, ARM topology has been a bit messed up. So lstopo is confusing what are probably cpu clusters with sockets.