visão geral do hardware do servidor system z e linux on z - concurso mainframe

© IBM Corporation, 2014

Visão geral do hardware do servidor System z e Linux on z

Anderson [email protected] técnico de pré-vendas – System z

2 © IBM Corporation, 2014

Apresentação realizada no dia 04/Setembro/2014 durante o evento de premiação do Concurso Mainframe 2014.

Local: IBM Tutóia, São Paulo.


Servidor IBM Mainframe – System z

Linux on z

O que o System z faz que outras plataformas não conseguem fazer ?

Exemplo de um caso real de um Independent Software Vendor (ISV)


InternalBatteries(option)

PowerSupplies

2 x SupportElements

PCIe I/O drawers

(Maximum 5 for zEC12)

Overhead Power Cables

(option)

Processor Books with Flexible Support Processors (FSPs), PCIe and HCA I/O fanouts

Radiator with N+1 pumps, blowers and motors

Optional FICON LX Fiber Quick Connect (FQC) not shown

PCIe I/O interconnect cables and Ethernet cables FSP cage controller cards

Overhead I/O feature is a co-req for overhead power option

zEC12 New Build Radiator-based Air cooled – Under the covers (Model H89 and HA1) Front view


IBM System z – Virtual Tourhttp://ibmtvdemo.edgesuite.net/servers/z/demos/zEnterprise_Radiator_Product_Tour/index.html


InternalBatteries(optional)

PowerSupplies

I/O Drawer

2 x CPC Drawers, Memory & HCAs

FQC for FICON LX only

Ethernet cables for internal System LAN connecting Flexible Service Processor

(FSP) cage controller cards (not shown)

PCIe I/O drawers

Rear View Front View

2 x SupportElements

zBC12 Model H13 – Under the covers


zEC12 Continues the CMOS Mainframe Heritage Begun in 1994

770 MHz

1.2 GHz

1.7 GHz

4.4 GHz

5.2 GHz5.5 GHz

1000

0

2000

3000

4000

5000

MH

z/G

Hz

6000

2000z900

189 nm SOI16 CoresFull 64-bit

z/Architecture

2003z990

130 nm SOI32 Cores

SuperscalarModular SMP

2005z9 EC

90 nm SOI54 Cores

System level scaling

2012zEC12

32 nm SOI101 Cores

OOO and eDRAMcache improvements

PCIe FlashArch extensions

for scaling

2010z196

45 nm SOI80 CoresOOO core

eDRAM cacheRAIM memoryzBX integration

2008z10 EC

65 nm SOI64 Cores

High-freq core3-level cache


zEnterprise EC12 Book and Frame

MCMMCM

EC12 Book

4-Book EC12 System

MemMem

MemMem


MCM @ 1800WWater Cooled

3 DCA Power Supplies 14 DIMMs100mm High

16 DIMMs100mm High

Rear

I/OFanoutCards

Cooling connector

MCM

Memory

Memory

Front

zEC12 Book Layout


Front ViewFanouts

zEC12Hexa-core PU CHIP

MCM

BOOKSide View

L3

C 0

L3

C 1

GXMC

U

Core0

Core1

Core2

Core3

Core4

Core5

L4Q

L4Q

L4Q L4Q

L4CL4B L4B

PU 0PU 2

SC 0SC 1

PU 1

V00

V01

PU 5PU 3 PU 4

V10

V11

zEC12 PU chip, SC chip and MCM


Cores Can be Configured for Different Needs


Arquitetura – Processadores Especializados

Sistema Operacionale Aplicação – Total de 120 Pus

(Cores) sendo até 101processadores configuráveis

Sistema Operacionale Aplicação – Total de 120 Pus

(Cores) sendo até 101processadores configuráveis

Processadores Especializados

CP (IBM System z Central Processor) – zOS, zTPF e zVSE. zAAP (IBM System z Application Assist Processor) – Java. zIIP (IBM System z Integrated Information Processor) – XML e DB2 Calls

IFL (IBM System z Integrated Facility for Linux) - Linux

até +2 processadores “Spare”

até 16 SAPs - System Assist Processors

Placas de I/O (FICON/FCP) ou OSA

Até 320 Processadores RISC

. Enviar/Receber requisições de I/O (Discos e Fitas)

I/OI/O

Processadores RISC/Power

. FICON – z/OS, zVSE e zVM / Linux

. FCP – zVM e Linux

até 16 CPU’s para Criptografia

- alta escalabilidade para transações SSL

É um “Datacenter in a Box”

System z tem muitos processadores, porém cada um executa o seu papel.

Integrated Firmware Processor


Microprocessador

Arquitetura – Demais plataformas de hardware

Comparar esse design com servidores RISC / Unix ou x86

Todas as funções de um computador

por software

I/O DeviceDrivers Criptografia, etc

Código de Aplicação

OS e Gerenciamentode Recurso

* Monotarefa eMonousuário

* Licenciamento de Software


IBM System z Redbookshttp://www.redbooks.ibm.com/portals/systemz


Helping clients reduce costs and improve control of their IT infrastructure Virtualization Consolidation Automation Workload management

• Logical Partitioning (LPAR) and z/VM are complementary technologies

– Both employ great hardware and firmware (PR/SM) innovations developed over the years

– Virtualization is a part of the basic componentry of the System z platform

• LPAR

– Host a relatively small number of very high-performance virtual servers

– Very low overhead, hardware-based virtualization through partitioning

• z/VM

– Host large numbers of high-performance virtual servers

– Low overhead, hardware-based, true virtualization with extreme levels of software augmentation

World-Class Server Virtualization:System z LPAR and z/VM

Together, System z LPAR and z/VM technology provide:

– High performance “on the metal” virtual servers for larger, performance-critical workloads

– The ability to provision 1000s of additional virtual servers flexibly and on demand


Security

I/OArchitecture On/Off Capacity

on Demand

ServerProvisioning

SoftwareLicensing

SystemsManagement

ProcessorDesign

WorkloadManagement

Partitioning andVirtualization


Anatomia de um Sistema Linux

O'Reilly, Charting the Linux Anatomy by Ed Stephensonhttp://www.oreillynet.com/pub/a/oreilly/linux/news/linuxanatomy_0101.html


• 0.28 % platform specific code in GCC 4.1

• 0.55 % of platform specific code in Glibc 2.5

• 1.81 % platform specific code in Linux Kernel 2.6.25

GNU C compiler

GNU binutils

Backend

Backend

Linux applications

BackendGNU runtime environmentLinux Kernel

Generic drivers

HW dependent drivers

System z instruction set and I/O hardware

Network Protocols File systems

MemoryMgmt

ProcessMgmt

arch arch

Architectureindependent

code

System z dependent code

Virtualization layer

Estrutura do Linux no Servidor System zMuitos pacotes de software Linux não requerem qualquer alteração de código para ser executado no Linux para System z

Note:Every supported Linux platform requires platform specific code in GCC, Glibc and the Linux kernel

Note:Every supported Linux platform requires platform specific code in GCC, Glibc and the Linux kernel


The Linux’s all look the same (on different architectures)

and have the same Linux kernel source.

But they have different personalities, qualities, features and options derived from the architectures.

z zBX x86


Versões de Linux atualmente suportadas no System z


SHARE – www.share.org

Who We Are SHARE Inc. is an independent, volunteer run association providing

enterprise technology professionals with continuous education and training, valuable professional networking and effective industry influence.

Our Mission SHARE is an independent volunteer-run information technology

association that provides education, professional networking and industry influence.

Link da apresentação: https://share.confex.com/share/121/webprogram/Session13557.html


Enterprise Linux Server

Priority Workload– No throughput reduction– No response time increase

Low Priority Workload– Soaks up remaining processor minutes

Unused processor minutes 1.9%0.00

10.00

20.0030.00

40.0050.0060.00

70.0080.00

90.00100.00

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57

Too much resource given to Low Priority workload

High Priority workload gets less resource than needed

Priority Workload– 31% throughput reduction– 45% response time increase

Low Priority Workload– Soaks up more CPU minutes

Unused CPU minutes 21.9%

Leading x86 HypervisorLeading x86 Hypervisor

What is Different about the Enterprise Linux ServerVirtualization enables mixing of high and low priority workloads without penalty


Priority Workload With Varying Demand Running Standalone On System z PR/SM

0

10

20

30

40

50

60

70

80

90

100

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57

Priority Workload MetricsTotal Throughput: 9.125M Avg Response Time: 140ms

Capacity UsedHigh Priority - 72.2% CPU MinutesUnused (wasted) - 27.8% CPU Minutes

Priority WorkloadPriority Workload

% C

PU

Usa

ge

Time (mins.)

High Priority Workload Demand Curve High Priority Workload Demand Curve


0.0010.00

20.0030.00

40.0050.0060.00

70.0080.00

90.00100.00

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57

Donor Workload

Priority Workload

Priority Workload On System z Does Not Degrade When Low Priority Donor Workload Is Added

Priority Workload MetricsTotal Throughput: 9.125MAvg Response Time: 140ms

Capacity Used High Priority - 74.2% CPU Minutes Low Priority - 23.9% CPU MinutesWasted – 1.9% CPU Minutes

NO throughput leakage

NO response time

increase

NO throughput leakage

NO response time

increase

% C

PU

Usa

ge

Time (mins.)

Run High Priority And Low Priority Workloads Together



Priority Workload With Varying Demand Running Standalone On x86 Hypervisor

0

10

20

30

40

50

60

70

80

90

100

Capacity UsedHigh Priority - 57.5% CPU MinutesUnused (wasted) – 42.5% CPU Minutes


Priority WorkloadPriority Workload

% C

PU

Usa

ge

Time (mins.)

High Priority Guest CPU Demand High Priority Guest CPU Demand


0.00

10.00

20.00

30.00

40.00

50.00

60.00

70.00

80.00

90.00

100.00

Donor Workload

Priority Workload

Priority Workload On x86 Hypervisor Degrades Severely When Low Priority Workload Is Added

30.7%throughput leakage

45.1%response time increase

21.9%wasted CPU minutes

30.7%throughput leakage

45.1%response time increase

21.9%wasted CPU minutes

% C

PU

Usa

ge

Time (mins.)

Capacity Used High Priority - 42.3% CPU MinutesLow Priority – 35.8% CPU MinutesWasted – 21.9% CPU Minutes





System z Virtualization Enables Mixing Of High And Low Priority Workloads Without Penalty

0.0010.00

20.0030.00

40.0050.0060.00

70.0080.00

90.00100.00

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57

System zSystem z

Priority Workload No throughput reduction No response time increase

Low Priority Workload Soaks up remaining CPU minutes


Priority Workload 31% throughput reduction 45% response time increase

Low Priority Workload Soaks up more CPU minutes




x86 with common hypervisorx86 with common hypervisor


System z Virtualization Enables Mixing Of High And Low Priority Workloads Without Penalty

0.0010.00

20.0030.00

40.0050.0060.00

70.0080.00

90.00100.00

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57

System zSystem z x86 with common hypervisorx86 with common hypervisor

Perfect workload management

Consolidate workloads of different priorities on the same platform

Full use of available processing resource (high utilization)

Imperfect workload management

Forces workloads to be segregated on different servers

More servers are required (low utilization)




Um resumo de 5 principais diferenciais


Benchmark – MATERA SystemsParceria entre IBM e MATERA apresenta número inédito de transações bancárias - See more at: http://www.matera.com/br/2014/06/02/parceria-entre-ibm-e-matera-apresenta-numero-inedito-de-transacoes-bancarias/#sthash.yVGr5J3V.dpuf


Obrigado.

@andersonbassani br.linkedin.com/in/andersonbassani

http://www.slideshare.net/abassani

visão geral do hardware do servidor system z e linux on z - concurso mainframe

Technology