DOCSLIB.ORG

Llllllllllllllillllllllllllllllllllllillllllllllllllllllllll

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Llllllllllllllillllllllllllllllllllllillllllllllllllllllllll llllllllllllllIllllllllllllllllllllllIlllllllllllllllllllllllllllllllllllll US005253344A United States Patent [191 [11] Patent Number: 5,253,344 Bostick et al. [45] Date of Patent: Oct. 12, 1993 [54] METHOD AND APPARATUS FOR [56] References Cited DYNAMICALLY CHANGING THE S P A NT ENT CONFIG TION OF A LOGICALLY 4 541 04:1- 9l/l985rEBall DOCI-llM 5 364/200 §$§TEMONEDI‘III D ATA PROCESSING 4,779,194, , 10/1988 egeer et . ................. .. 4,8l5,03l 3/1989 _ 4,843,541 6/1989 [75] Inventors: James E. Bostick, Poughkeepsie; 4,853,117 g/19s9 Roger E. Hough, Highland; Suzanne 5,027,271 6/1991 M. John, Poughkeepsie; Jeffrey P. 5,155,837 10/1992 Kubala, Poughquag; Karen M. 53701472 12/1992 Noon“; Nofman E' Shift‘, both of Primary Examiner-Michael R. Fleming Poughkeepsie; Ira G. Siegel, New Assistant Examine,_Gopa1 c_ Ray Paul’ an of N-Y- Attorney, Agent, or Finn-William B. Porter CI‘ [73] Assignee: International Business Machines [57] _ _ _ _ Corp” Armonk, NY, A request is made by a system in a ?rst logical partition, within a logically partitioned data processing system, to _ dynamically change the I/O con?guration of the host [21] Appl' No" 755’246 system in a way that affects a system in a second logical partition. The hypervisor intercepts the request, ensures [22] Filed! sep- 5’ 1991 the serialization of such dynamic I/O requests, and allows dynamic recon?guration to proceed. Subse [51] Int. Cl.5 ............................................ .. G06F 13/00 quently, the hypervisor determines the effect of the [52] US. Cl. .................................. .. 395/275; 395/325; recon?guration on the second partition, and notifies the 364/9494; 364/D1G. 2 second partition of the change. [58] Field of Search ............. .. 395/725, 325, 650, 200, 395/425, 275; 340/825.5; 370/852 12 Claims, 8 Drawing Sheets SET UP CONFIGURATION MODE P01 DYNAMIC I/O COMMAND AND suaszousm PROCESSING / PROCESS DYNAMIC l/O COMMAND DETERMINE THE EFFECT or / conncummu ounces ON ALL LOGICAL PARTITTONS l NOTIFY AFFECTED LOGICAL PARTITIONS 0F DELETED SUBCHANNELS VIA CHANNEL REPORTS NO ——L EXIT CONFIGURATION MODE YES NOTIFY AFFECTED LOGICAL PARTITIONS OF ADDED OR MODIFIED SUBCHANNELS VIA CHANNEL REPORTS US.‘ Patent 0a. 12, 1993 Sheet 1 of 8 5,253,344 FIG.1 1m SET UP CONFIGURATION MODE / 102 SE FIGs 2-5 DYNAMIC I/O COMMAND AND / FOR DETAILS SUBSEQUENT PROCESSING 102A PROCESS DYNAMIC I /o COMMAND 102B DETERMINE THE EFFECT OF / ' CONFIGURATION CHANGES on ALL LOGICAL PARTITIONS 1D2c NOTIFY AFFECTED LOGICAL / PARTITIONS 0F DELETED SUBCHANNELS VIA CHANNEL REPORTS N0 103 EXIT CONFIGURATION MODE / YES 104 NOTIFY AFFECTED LOGICAL / PARTITIONS 0F ADDED DR MODIFIED ' SUBCHANNELS VIA CHANNEL REPORTS US. Patent Oct. 12, 1993 Sheet 2 of 8 5,253,344 FIG. 2 201 \ PRE-CHECK N0 REQUEST VALID 202 \ POST CONDITION cons N0 v - COMMAND OK > 203 \ PASS REQUEST 20s . TO 10p \ ANALYZE CHANGES 204 \ WAIT FOR 206 COMPLETION \ UPDATE INTERRUPTION I/O nzvrce CONTROL BLOCKS 207 SET up FOR POST CRW POSTING COMPLETION CODE US. Patent Oct. 12, 1993 Sheet 3 of 8 5,253,344 FIG.3 301 \ PRE-CHECK N0 N0 VALID REQUEST > COMMAND 0K 302 306 \ POST \ UPDATE coumnow CODE CONFIGURATION INFORMATION 303 - 307 i \ INVOKE v \ POST PROCESSOR -— —-—+- COMPLETION 3 CONTROLLER ‘ CODE YES ERROR 304 \ PASS REQUEST To IOP 305 \ wAIT FOR COMPLETION INTERRUPTION US. Patent Oct.12,1993 Sheet 4 of 8 5,253,344 F I G . 4 \ PREI-CHECK VALID REQUEST \ PASS REQUEST TO IOP \ POST CONDITION cons \ WAIT FOR COMPLETION INTERRUPTION \ POST i COMPLETION cone US. Patent Oct. 12, 1993 Sheet 5 of 8 5,253,344 F l G . 5 ‘ \ PRE-CHECK V COMMAND OK > CLEAN UP / CONTROL BLOCKS N0 5o7\ VALID REQUEST > POST -4——-| COMPLETION CODE \ UPDATE LPAR CONTROL BLOCKS \ PASS REQUEST TO IOP \ POST CONDITION CODE ses \ WAIT FOR COMPLETION INTERRUPTION US. Patent 0¢¢.12,199s Sheet 6 of 8 5,253,344 501 YES 605’\ \ PRE-CHECK > COMMAND ox > UPDATE LPAR . CONTROL N0 60? BLOCKS VALID REQUEST 7 POST COMPLETION cone <-——-' 502 \ PASS COMMAND T0 IOP FIG.6 e03 \ POST common CODE 60:: \ WAIT FOR COMPLETION INTERRUPTION FIG.7 I I 0 NUMBER OF I POSSIBLE SUBCHANNELS SUBCHANNELS US. Patent Oct. 12,1993 Sheet 7 of 8 5,253,344 FIG.9B STATE TYPE DESCRIPTION O OPEN , DISABLED(AND IDLE) CLOSED BEING ENABLED OR DISABLED OPEN ENABLED AND IDLE CLOSED MAKE FUNCTION ACTIVE OPEN FUNCTION PENDING WAITING FOR LOCKS CLOSED CHECK COUNT CLOSED MAKE REAL FUNCTION ACTIVE CLOSED ISSUE SERVICE PROCESSOR REQUEST AND IGNORE UNSOLICITED INTERRUPTIONS OPEN FOR REAL STATUS SUBCHANNEL OPEN WAITING FOR REAL STATUS FUNCTION PENDING 0 CLOSED DRAIN ANY REAL STATUS. UPDATE FUNCTION PENDING CLOSED REBUILD SYSTEM CONTROL BLOCKS CLOSED FILTER RESPONSE AND MAKE STATUS PENDING CLOSED UNLOCK PICLs OPEN STATUS PENDING CLOSED CHECK FOR ADDITIONAL REAL PENDING STATUS CLOSED UNABLE TO OBTAIN PICLs-CHECK COUNT CLOSED MAKE INVALID RESPONSE PENDING CLOSED MAKE UNSOLICITED STATUS PENDING CLOSED MAKE ERROR PENDING FOR SERVICE PROCESSOR REQUEST FAILURE CLOSED CHECK FOR ANY PENDING UNSOLICITED STATUS NOTE: AN OPEN STATE IS ONE FROM WHICH MORE THAN ONE ' PROCESS CAN ATTEMPT TO MAKE A TRANSITION. A CLOSED STATE IS ONE FROM WHICH ONLY ONE PROCESS CAN ATTEMPT TO MAKE A TRANSITION. COMPARE AND SWAP IS REQUIRED TO MAKE SUCH A TRANSITION . NOTE: ANY PROCESS WHICH CHANGES THE STATE FROM AN OPEN ONE IS DOCUMENTED WITH A LIST OF STATES AND WHAT TO DO FOR EACH. TAMCCODE AMCLPNUM AMCDLSNM FIG, 8 US. Patent Oct. 12, 1993 Sheet 8 of 8 5,253,344 Irpt or MIH Reset M F IG. 9A Dis- Make <-— Lock abled any V100, and L> unsol . Clear 4 ldle r> status any pend ‘ status < 0 20 15 ’ l A I A A Reset v I v I ITSCH PNCW Idle > Status Unlock Filter CDLRB, being — and Pend. PICLs Resp & attach up- Ena- ignore if Make detach - e dated <-> bled irpts <—- held. <- Status <-— CRUS, Reset Pend ignore <- waits. < irpts 1 2 14 13 12 11 | A A A A A V! l l ‘—1 I Reset Hake Make Make Set Drain func status Status Resp. Any pend. pend. Pend. Make Uns Real Bump Err Set Set Uns <- Status — - Count —> resp fail Status Check Resp. Pend. Resp. 3 17 19 18 10 [cm A A AAAA V I [Err (2C0 Func PICL Issue Make pend Time- reqst Real CCZ — await out. to —> CHSC ing Check Proc. Active > locks count. Cntrlr > 6 cm! V V V Wait Wait I for for real real status status func subch pend active 9 8 5,253,344 1 2 The IODF contains the I/O de?nition. The dynamic METHOD AND APPARATUS FOR con?guration feature provides the user with an ACT I DYNAMICALLY CHANGING THE VATE capability. When the user wants to run with a CONFIGURATION OF A LOGICALLY new I/O con?guration, he enters the ACTIVATE PARTITIONED DATA PROCESSING SYSTEM 5 command in the HCD and speci?es the IODF he wishes to use. The HCD compares the current active FIELD OF THE INVENTION con?guration with the target con?guration and builds a This invention relates to the ?eld of computers and list of changes required. MVS/ESA then validates the computer system complexes comprising a logically changes, requests I/O con?guration changes, updates partitioned processor governed by a hypervisor. More MVS/ESA control blocks, and downloads a new particularly, this invention provides a mechanism for IOCDS to the Processor Controller DASD. In a hyper handling dynamic I/O recon?guration requests in a visor environment in which the operating systems in the logically partitioned environment. partitions are capable of dynamic modi?cations to the BACKGROUND ART physical system’s I/O con?guration, novel situations 15 are presented which call for decisions as to how the In a logically partitioned computer processor, such as hypervisor will react to the proposed dynamic changes. IBM's PR/SM-LPAR, a plurality of operating systems It is therefore an object of the present invention to operate in logical partitions, with the partitions con provide a method and apparatus by which a hypervisor trolled by a hypervisor. Such an approach is described can control and respond to dynamic I/O recon?gura in US. Pat. No. 4,843,541, "Logical Resource Partition tions by an operating system in a partition. ing of a Data Processing System”, by Bean, et al., as It is a further object of this invention to permit con signed to the assignee of the present invention, and tinued operation by systems in other partitions during incorporated herein by reference. In such an environ dynamic changes to a system’s I/O con?guration by a ment, each operating system operates to a very large system in a then controlling partition. degree independently, with its own resources, and with 25 the hypervisor intercepting requests for certain privi theIt involvement is still a further of theobject hypervisor of this invention in dynamic to changes leged operations, and reissuing them (perhaps in a changed form) on behalf of the requesting operating to a systems con?guration by a then controlling parti system/partition. tion, until after the changes have been effected. In most prior art environments, the physical I/O 30 SUMMARY OF THE INVENTION con?guration (channels, channel paths, devices, etc.) is “static” in that major con?guration changes/redefmi In operation, the PR/ SM hypervisor ?rst ensures that tions could only be made by stopping active work on dynamic recon?guration requests are serialized (i.e., the system, rede?ning the con?guration, then reinitial that only one logical partition at a time can perform izing (IPLing) the system with the new con?guration.
Load more

Recommended publications
  • Introduction to Virtualization
    z Systems Introduction to Virtualization SHARE Orlando Linux and VM Program Romney White, IBM [email protected] z Systems Architecture and Technology © 2015 IBM Corporation Agenda ° Introduction to Virtualization – Concept – Server Virtualization Approaches – Hypervisor Implementation Methods – Why Virtualization Matters ° Virtualization on z Systems – Logical Partitions – Virtual Machines 2 z Systems Virtualization Technology © 2015 IBM Corporation Virtualization Concept Virtual Resources Proxies for real resources: same interfaces/functions, different attributes May be part of a physical resource or multiple physical resources Virtualization Creates virtual resources and "maps" them to real resources Primarily accomplished with software or firmware Resources Components with architecturally-defined interfaces/functions May be centralized or distributed - usually physical Examples: memory, disk drives, networks, servers Separates presentation of resources to users from actual resources Aggregates pools of resources for allocation to users as virtual resources 3 z Systems Virtualization Technology © 2015 IBM Corporation Server Virtualization Approaches Hardware Partitioning Bare-metal Hypervisor Hosted Hypervisor Apps ... Apps Apps ... Apps Apps ... Apps OS OS OS OS OS OS Adjustable partitions Hypervisor Hypervisor Partition Controller Host OS SMP Server SMP Server SMP Server Server is subdivided into fractions Hypervisor provides fine-grained Hypervisor uses OS services to each of which can run an OS timesharing of all resources
    [Show full text]
  • Logical Partitioning
    Power Systems Logical partitioning Power Systems Logical partitioning Note Before using this information and the product it supports, read the information in “Notices” on page 233. This edition applies to IBM AIX Version 6.1, to IBM AIX 5L™ Version 5.3, to IBM i 6.1 (product number 5722-SS1) , to IBM Virtual I/O Server version 2.1.2.0, and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. © Copyright IBM Corporation 2007, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Logical partitioning ...............................1 What's new in Logical partitioning ............................1 Logical partition overview ...............................2 Benefits of logical partitioning ............................2 Sharing resources between logical partitions ........................3 Managed systems.................................5 Manufacturing default configuration ..........................5 Logical partitioning tools ..............................6 Hardware Management Console ...........................6 Partition profile ...............................7 System profile ...............................11 Partitioning with the Integrated Virtualization Manager ..................11 Virtual Partition Manager.............................13 Physical and virtual hardware resources .........................14
    [Show full text]
  • IIP (System Z9 Integrated Information Processor) Computer CEC (Central Electronics Complex) Server
    IBM System z z/VM Basics Arwed Tschoeke Systems Architect [email protected] © 2009 IBM Corporation © 2008 IBM Corporation Introduction We'll explain basic concepts of System z: – Terminology – Processors – Memory – I/O – Networking We'll see that z/VM virtualizes a System z machine: – Virtual processors – Virtual memory – … and so on Where appropriate, we'll compare or contrast: – PR/SM or LPAR – z/OS – Linux 2 z/VM: The Very Basics z/VM: The Very Basics 1 IBM System z © 2008 IBM Corporation System z Parts Nomenclature x86, UNIX, etc. System z Memory Storage (though we are moving toward "memory") Disk, Storage DASD – Direct Access Storage Device Processor Processor, Engine, PU (processing unit) IOP (I/O processor) CPU (central processing unit) CP (central processor) SAP (system assist processor) Specialty engines –IFL (Integrated Facility for Linux) –zAAP (System z Application Assist Processor) –zIIP (System z9 Integrated Information Processor) Computer CEC (central electronics complex) Server 3 z/VM: The Very Basics © 2008 IBM Corporation IBM System z Virtualization Genetics Over 40 years of continuous innovation in virtualization – Refined to support modern business requirements System z10 . – Exploit hardware technology for economical growth , .. ity System z9 z/VM V5 bil – LPAR, Integrated Facility for Linux, HiperSockets xi 64-Bit Fle – System z Application Assist Processors s, zSeries es VM/ESA Virtual Switch – System z Information Integration stn 9672 bu ESA Guest LANs Set Observer Ro Processors y, 9x21 ilit VM/XA Virtual Machine
    [Show full text]
  • Let's Build a Z Environment
    Let’s Build a z Environment - 101 z/OS Session 23330 Tuesday, August 14 at 10:00-11:00 AM STL CC, Room 242 Presented by Paul R. Robichaux NewEra Software, Inc. [email protected] 1 Abstract – Let’s Build a z Environment! The two presentations in this series focus on the building of a z Environment – Hardware, Software, Security – with the goal of establishing a ‘Trusted Computing Base’. A z/OS System that can provide the reliability needed to meet demanding service levels, integrity and security objectives. All are necessary to execute mission critical applications. This is Intended for those new to z Systems or just beginning their careers with organizations that capitalize on systems anchored to the power and reliability of the IBM Mainframe. In – 101 – the focus will be on the platform, in this case a z14, hardware divisions of the Central Processing Complex (CEC), its various channel pathways and related devices that define a UCW (Unit Control Work), the front half of the z System Device Chain. This segment continues with the definition of an associated Operating System configuration, its various I/O devices and related features that define a UCB (Unit Control Block), the back half of the z System Device. Detailing both the Power-On and IPL process will join UCWs and UCBs to form a fully addressable device across which data (encrypted or not) may flow to and from the CEC. In – 102 – the focus will shift to a discussion of Multiple Virtual Storage (MVS), what is z/OS, how to get it, install it, support it and upgrade/migrate from release to release.
    [Show full text]
  • Systems Management Logical Partitions Version 6 Release 1
    IBM System i Systems management Logical partitions Version 6 Release 1 IBM System i Systems management Logical partitions Version 6 Release 1 Note Before using this information and the product it supports, read the information in “Notices,” on page 135. This edition applies to version 6, release 1, modification 0 of and IBM i5/OS (product number 5761–SS1) to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. © Copyright IBM Corporation 1999, 2008. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Logical partitions........... 1 Ordering a new server or upgrading an PDF file for Logical partitions ........ 1 existing server with logical partitions .... 45 Partitioning with a System i ......... 1 Providing hardware placement information Logical partition concepts ......... 1 to service providers......... 45 How logical partitioning works ...... 2 Designing your logical partitions ..... 46 How logical partitioning can work for you .. 3 Deciding what runs in the primary and Hardware for logical partitions ...... 4 secondary partition ......... 46 Bus .............. 5 Capacity planning for logical partitions .. 47 Bus-level and IOP-level I/O partitions ... 7 Using the System Planning Tool .... 47 Dynamically switching IOPs between Examples: Logical partitioning ...... 47 partitions ............ 7 Creating logical partitions ........ 48 IOP .............. 9 Managing logical partitions ........ 49 SPD and PCI ........... 11 Managing logical partitions by using System i Processor ............ 11 Navigator, DST, and SST ........ 50 Memory ............ 14 Starting System i Navigator ...... 53 Disk units ............ 15 Starting SST and DST for logical partitions 53 Removable media device and alternate Logical partition authority .....
    [Show full text]
  • Logical Partitioning Feature of CB Series Xeon Servers Suitable for Robust and Reliable Cloud
    Hitachi Review Vol. 61 (2012), No. 2 65 Logical Partitioning Feature of CB Series Xeon Servers Suitable for Robust and Reliable Cloud Hitoshi Ueno, Ph. D., PE.jp OVERVIEW: LPAR is Hitachi’s own server virtualization feature for Shinichi Matsumura Hitachi Compute Blade servers. LPAR stands for logical partitioning used by mission-critical systems such as mainframes and offers excellent performance, including reliability, stability, and maintaining virtual server separation. The implementation of logical partitioning on Xeon*1 servers significantly expands the scope for applying virtualization in private clouds because it means that virtualization of mission-critical systems can be used even on Xeon servers. Hitachi is currently developing new solutions that improve ease-of-operation and simplify installation, and the number of sites using LPAR for cloud is increasing. LPAR is already a proven virtualization feature and Hitachi intends to continue with development to make further improvements in performance and reliability. INTRODUCTION is that, compared to the VM (virtual machine) method, HITACHI aims to create new value through its next it is easier to configure systems with higher reliability generation of IT (information technology) platforms and performance. However, very few virtualization and virtualization is a key technology for implementing products support the use of logical partitioning on the infrastructure clouds that will support this Xeon processors and other Xeon servers (see Table 1). endeavor. Within this, Hitachi Compute Blade (CB) Virtualization based on logical partitioning has logical partitioning feature (LPAR) provides a server been widely used for mission-critical applications virtualization feature critical to data processing. in the past and, unlike virtualization software from This article describes the characteristics of the other vendors, Hitachi’s LPAR feature also extends LPAR, a server virtualization feature that enhances this capability to Xeon servers.
    [Show full text]
  • PR/SM Planning Guide Level 01A
    zEnterprise System Processor Resource/Systems Manager Planning Guide SB10-7155-01 Level 01a zEnterprise System Processor Resource/Systems Manager Planning Guide SB10-7155-01 Level 01a Level 01a Note Before using this information and the product it supports, read the information in “Safety” on page xi, Appendix D, “Notices,” on page 217, and IBM Systems Environmental Notices and User Guide, Z125-5823. This edition, SB10-7155-01, applies to the IBM zEnterprise 196 and zEnterprise 114 servers. This edition replaces SB10-7155-00. There might be a newer version of this document in a PDF file available on Resource Link.Goto http://www.ibm.com/servers/resourcelink and click Library on the navigation bar. A newer version is indicated by a lowercase, alphabetic letter following the form number suffix (for example: 00a, 00b, 01a, 01b). © Copyright IBM Corporation 2010, 2011. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Level 01a Contents Figures ..............vii Chapter 2. Planning considerations . 31 Overview ...............33 Tables ...............ix Planning the I/O configuration ........33 Planning considerations .........33 Safety ...............xi Maximum number of logical partitions ....35 Managing logical paths for ESCON and FICON Safety notices ..............xi channels ..............36 World trade safety information .......xi Managing the establishment of logical paths . 40 Laser safety information ..........xi Shared channel overview .........49 Laser compliance ...........xi Unshared ESCON or FICON channel recommendations ...........55 About this publication ........xiii Dynamically managed CHPIDs.......55 What is included in this publication ......xiv IOCP coding specifications ........56 Related publications ...........xv Coupling facility planning considerations ....66 z/Architecture ............xv Test or migration coupling configuration .
    [Show full text]
  • Introduction to the System Z Hardware Management Console
    Front cover Introduction to the System z Hardware Management Console Large scale hardware systems management concepts Design and implementation of a management controller Practical operational techniques and scenarios Merwyn Jones HMC & SE Development Team ibm.com/redbooks International Technical Support Organization Introduction to the System z Hardware Management Console February 2010 SG24-7748-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (February 2010) © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xiii The team who wrote this book . xiii Acknowledgements . xvi Become a published author . xvi Comments welcome. xvi Chapter 1. Introduction to System z Hardware. 1 1.1 General introduction: Mainframes in our midst . 2 1.2 System z hardware architecture . 3 1.2.1 Consolidation of mainframes . 3 1.2.2 An overview of the early architectures . 4 1.2.3 Early system design . 5 1.2.4 Current architecture . 7 1.3 The raised floor . 7 1.4 Hardware management console . 9 1.5 Frames and cages . 9 1.6 Processor units . 10 1.6.1 Multiprocessors. 10 1.6.2 Processor types . 11 1.7 Memory hierarchy . 13 1.8 Networking the mainframe . 14 1.9 Disk devices . 14 1.9.1 Types of DASD . 16 1.9.2 Basic shared DASD . 17 1.10 I/O connectivity (channels) . 18 1.10.1 Channel subsystem .
    [Show full text]
  • IBM POWER Virtualization Best Practice Guide
    IBM Power Systems Performance IBM POWER Virtualization Best Practices Guide Version 4.0 March 2020 Copyright © 2020 by International Business Machines Corporation. IBM Power Virtualization Best Practices Guide CONTENTS 1 INTRODUCTION .................................................................................................................... 7 2 VIRTUAL PROCESSORS .......................................................................................................... 7 2.1 Sizing/configuring virtual processors ......................................................................................................... 9 2.2 Entitlement vs. Virtual processors ........................................................................................................... 10 2.3 Matching entitlement of an LPAR close to its average utilization for better performance ....................... 10 2.4 When to add additional virtual processors .............................................................................................. 11 2.5 How to estimate the number of virtual processors per uncapped shared LPAR ...................................... 11 3 AIX VIRTUAL PROCESSOR MANAGEMENT - PROCESSOR FOLDING ....................................... 11 3.1 VPM folding example .............................................................................................................................. 12 3.2 Tuning Virtual Processor Management Folding ....................................................................................... 13 3.3
    [Show full text]
  • PR/SM Planning Guide Operational Considerations
    IBM IBM Z Processor Resource/Systems Manager Planning Guide SB10-7169-02 Level 02a IBM IBM Z Processor Resource/Systems Manager Planning Guide SB10-7169-02 Note: Before you use this information and the product it supports, read the information in “Safety” on page xi, Appendix C, “Notices,” on page 199, and IBM Systems Environmental Notices and User Guide, Z125-5823. This edition, SB10-7169-02, applies to the IBM Z and IBM LinuxONE servers. This edition replaces SB10-7169-01. There might be a newer version of this document in a PDF file available on Resource Link. Go to http://www.ibm.com/servers/resourcelink and click Library on the navigation bar. © Copyright IBM Corporation 2017, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures .............. vii Extended TOD-clock facility ........ 26 Clock Comparator on Shared Processors.... 27 Tables ............... ix Chapter 2. Planning considerations .. 29 Safety ............... xi Planning the I/O configuration ........ 29 Maximum number of logical partitions .... 31 Safety notices .............. xi Managing logical paths for FICON channels .. 31 World trade safety information ....... xi Managing the establishment of logical paths .. 33 Laser safety information .......... xi Shared channel overview ......... 42 Laser compliance ............ xi Unshared ESCON or FICON channel recommendations ........... 48 About this publication ........ xiii Dynamically managed CHPIDs....... 48 What is included in this publication ...... xiii IOCP coding specifications ........ 49 Related publications ........... xiv 25GbE RoCE Express2 planning considerations .. 58 z/Architecture ............ xiv 10Gb RoCE planning considerations ...... 58 Enterprise Systems Architecture/390 (ESA/390) xiv Coupling facility planning considerations .... 59 Hardware.............
    [Show full text]
  • LPAR Weight Concepts
    Planning for any System z processor, especially image upgrades, consideration must be given to handling the impacts Determine Per CP Share - Vertical CP Management of PR/SM where the following factors should be considered: * Logical processors are classified as vertical high , medium or low - The number of partitions * PR/SM quasi-dedicates vertical high logicals to physical processors - The CP usage; either general purpose, traditional CPs or the use of IFL/ICF CPs and z/OS specialty processors. vertical medium - The remainder of the share is distributed to the LPAR A: 7.2 CPs – 6 VH,2 VM (60%), 1 VL - The partition mode, either dedicated or shared processors - The ratio of logical CPs to physical CPs defined * Vertical low processors are only given service when other partitions do - The number of logical CPs defined to the partitions not use their entire share and there is demand in the partition LPAR B: 1.8 CPs – 1 VH, 1 VM (80%), 7 VL - The type of system control program (z/OS, z/VM, Linux, etc.), and the workload characteristics in each partition. - The effect of the partitions shared weight and any impact of capping on the partition. * Vertical low processors are parked by z/OS when no extra service is available. Book 0 Important Concepts System z Partitioning Controls * LPAR weights become important only when the processor is extremely busy ( approaching 100%) or are capped * Example CEC 2827-704: Access to resources is relative to other partitions. * There are two dispatchers involved in making resource allocations: - PR/SM Every partition must have a relative weight, the relative weight is also known as the initial - Operating System processing weight (hard cap).
    [Show full text]
  • United States Patent (19) 11 Patent Number: 5,802,354 Kubala Et Al
    IIIUSOO5802354A United States Patent (19) 11 Patent Number: 5,802,354 Kubala et al. 45 Date of Patent: Sep. 1, 1998 54 SESSESSEEogical :::::: y: a G. et al. ................... 395/551 PARTITIONS OF A PARTITIONED OTHER PUBLICATIONS NFORMATION HANDLING SYSTEM TO A TEST DATESOURCE "Enterprise Systems Architecture/390 Principles of Opera tion' IBM Publication, SA22-7201-02, Dec. 1994. (75) Inventors: JeffreyB. Mathias, P. Kubala, Vestal; Poughguag;Ira G. Siegel, Thomas New ocessor RResource/Systems C is S t sManager Planninging Uu1Guide” Paltz; David E. Whitney, IBM Publication, GA22-7236-01, Sep. 1996. Poughkeepsie, all of N.Y. Primary Examiner Thomas M. Heckler 73) Assignee: International Business Machines Attorney; Agent, or Firm-W. A. Kinnaman, Jr. Corporation. Armonk, N.Y. 57) ABSTRACT (21) Appl. No.: 871,429 A method and apparatus for synchronizing selected logical o partitions of a partitioned information handling system to a 22 Filed: Jun. 9, 1997 test datesource. A system operator is presented with a 6 display panel in which the operator may specify a set of test 2. 4 to spees ope-woo was seeds Pawa as aposuo Xu Pow Ge.K. partitions and a test clock value. Each partition designated as (58 Field of search an a wo be 44 440 x and see395551 555 a test partition is synchronized to the test clock value upon being newly activated, while production partitions are syn 395/200.78 chronized to a production clock value. The first test partition to be newly activated is synchronized to the test clock value 56) References Cited by calculating the difference between the test clock value U.S.
    [Show full text]