HP UX 11.23 vpar memory modification

Some abbrevations and definitions :
Base memory – used by kernel for content that cannot be evacuated, or (if there is a surplus) that it can evacuate. Can not be whipped whlile vpar is up. vpar Monitor A04 does not recognise base and float memory.
Boot processor – processor from which vpar kernel starts up
CLI – command line interface
CLM – cell local memory. Is dividied into base and floating memory. Refers the memory that is physically in the cell.
CLP – cell local processor, core/CPU, NOT the physical processor
Floating memory – used by kernel ONLY for content that it can evacuate. Can be whipped out while vpar is up.
memory granule – unit of memory that can be added or subtracted (vparmodify), can be seen using command vparstatus. In HP UX 11.23 that is a X*64MB, default is 128MB.
Interleaved memory – memory addresses that are on all memory banks, for faster work
ILM – interleaved local memory, this type of memory is ESENTIAL for HP UX PA RISC systems, for starting up, and MUST be the first 2GB. Generally all the memory may be defined as ILM. Is divided into base and floating memory. May be memory from one or more cells.
ISL – initial system loader, from where vpar Monitor starts
NUMA – memory locality based optimization on non-uniform memory access systems
LIF area – Logical Interchange Format, the part of the OS that gets us from the FW to the OS on the disk
PCI – peripheral component interconnect
vpar – virtual partition
vPars Partition Database – may be changed ONLY from OS level, but is inside of vpar monitor

Note for memory, and its allotment, for PA RISC systems : When ranges are specified for the entire memory owned by a partition, you should ensure that at least one of the ranges is below 2 GB and is large enough to accommodate the kernel for that partition. However, other partitions also require memory below 2 GB for their kernels. Hence, you also should ensure that the specified range below 2 GB is not so large such as to preclude memory below 2 GB for the other partitions.

Order of vpar system startup :
HW—>FW—>LIF—>ILS—>vpar MON—>vpar—>HP UX

Gathering data about vpar :
From the ISL/hpux vpmon level, OS is not as yet up :
MON> vparinfo vpar3
..Resources assigned to partition 2 (vpar3)…
…..
Total CPUs: 2
User specified cpu count: 0
CLP count(cell 1): 0
The following CPUs belong to partition:

ILM Effective Size: 6103040 kb
CLM Effective Size(cell 1): 0 kb
…..
Boot Options:
AUTOBOOT:on
DYNAMIC

Here a vpar Monitor version may be seen, which is very important, because of the commands and their effect :
MON> release
@(#) $Revision: vmunix:…..bhaski_A.04.02.10…..; FLAVOR=perf

Or from the OS level, from the administrative virtuel partition (vpar1 in my case) :
These are the data for the whole partition (number 0), on which we have several other vpars (vpar1, vpar2, vpar3…..) :
OS1:/>parstatus -p 0 -V
[Partition]
Partition Number : 0
Partition Name : Partition 0
Status : Active
…..
Core Cell : cab0,cell1
Total Good Memory Size : 6.0 GB
Total Interleave Memory: 6.0 GB
Total Requested CLM : 0.0 GB
Total Allocated CLM : 0.0 GB
…..
OS1:/>vparstatus -p vpar1
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============= ===== ============ ======================= =====
vpar1 Up Dyn,Auto,Asr /stand/tuned_system/vmuni
[Virtual Partition Resource Summary]
CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
======================= ======= ==== ==== ========== ==========
vpar1 1/ 6 2 7 128 128
Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
=============== ====================== ======================
vpar1 0/ 0 5960 0/ 0 0
The relevant data is data concerning the amount of allocated memory, and its granularity (128) since memory is added in granule units.

See which vpar is the administrative one :
OS1:/>vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============= ===== ============ ======================= =====
vpar1 Up Dyn,Auto,Asr /stand/tuned_system/vmuni
vpar2 Down Dyn,Auto,Asr /stand/vmunix
vpar3 Down Dyn,Auto,Asr /stand/vmunix
…..

Change the memory for vpar
This can be done ONLY when that vpar is down (in my case vpar3) or when it is up in a “single user mod”-u (here how that is done : MON> vparload -p vpar1 -o "-is").
This can be done ONLY from the administrative vpar (vpar1 in my case) :
# vparmodify -p vpar3 -m mem::XYZ
Where XYZ is the number of granules (here 128M) in Mb.

Note 1 : super document about HPUX vpar-s.
Note 2 : how does HP UX PA RISC enter into single user mode – document.

This entry was posted in Unix and tagged , . Bookmark the permalink.

Comments are closed.