HP Integrity Superdome 2 8/16 HP Superdome 2 Partitioning Administrator Guide - Page 77

Deleting CPU-cores Summary, CPU Allocation, Memory

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 77 highlights

Table 7-1 CPU-core Allocation Allocating By Forms Resource Path Example CPU resource path cpu:cpu_path enclosure#/blade#/ cpusocket#/cpucore# vparcreate -p Oslo -N Norway -a cpu:1/1/0/0 CPU count cpu::num All positive integers vparcreate -p Oslo -N Norway -a cpu::2 socket path socket:socket_id: enclosure#/blade#/cpusocket# vparcreate -p Oslo -N Norway -a cpu::num socket:3/6/0:cpu::2 Defining the minimum and maximum CPUs cpu:::[min][:[max]] All positive integers vparcreate -p Oslo -N Norway -a cpu::2:8 Deleting CPU-cores Summary • If you want to control which CPU-core is deleted, use the same method-by SLP, by resource path, or by count-on your deletion command line that you used on your addition command line. CPU Allocation On HP Integrity Superdome 2, parstatus command provides all the required CPU information from the OA without installing or booting to nPar mode. From HP-UX, ioscan is used to retrieve CPU information. However ensure that CPU resource paths are determined using the option -m that maps HP-UX hardware paths to resource paths. The first vPartition is configured with the AD221 Ethernet / Fibre channel combination card at hardware address 48/0/0/2/0/0/2/0. Run the following command to view the configuration: # ioscan -m resourcepath | grep cpucore 1/120 1/122 1/124 1/126 1/128 1/130 1/132 1/134 0x100ff02ff000017 0x100ff02ff000117 0x100ff02ff000217 0x100ff02ff000317 0x100ff02ff010017 0x100ff02ff010117 0x100ff02ff010217 0x100ff02ff010317 or, for this example, run the following command. # # ioscan -m resourcepath | grep 48/0/0/2/0 cpucore-1/2/0/0 cpucore-1/2/0/1 cpucore-1/2/0/2 cpucore-1/2/0/3 cpucore-1/2/1/0 cpucore-1/2/1/1 cpucore-1/2/1/2 cpucore-1/2/1/3 48/0/0/2/0 48/0/0/2/0/0 0x900010002ffff8e 0x90001000203ff85 iorp-9/1/0/0/2 ioslot-9/1/3 Memory There are two major types of memory addressing, Socket Local Memory, (SLM), and InterLeaved Memory, (ILM). With SLM, entire memory address ranges are from a single socket. For best performance, memory and CPU-cores from the same socket(s) should be assigned to a vPar. ILM is an address range of memory whose adjacent addresses reside on one or more sockets in the underlying nPartition. Planning Your Virtual Partitions 77

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
Table 7-1 CPU-core Allocation
Example
Resource Path
Forms
Allocating By
vparcreate -p Oslo -N Norway -a cpu:1/1/0/0
enclosure#/blade#/
cpusocket#/cpucore#
cpu:cpu_path
CPU resource
path
vparcreate -p Oslo -N Norway -a cpu::2
All positive integers
cpu::num
CPU count
vparcreate -p Oslo -N Norway -a
socket:3/6/0:cpu::2
enclosure#/blade#/cpusocket#
socket:socket_id:
cpu::num
socket path
vparcreate -p Oslo -N Norway -a cpu::2:8
All positive integers
cpu:::[min][:[max]]
Defining the
minimum and
maximum CPUs
Deleting CPU-cores Summary
•
If you want to control which CPU-core is deleted, use the same method—by SLP, by resource
path, or by count—on your deletion command line that you used on your addition command
line.
CPU Allocation
On HP Integrity Superdome 2,
parstatus
command provides all the required CPU information
from the OA without installing or booting to nPar mode.
From HP-UX,
ioscan
is used to retrieve CPU information. However ensure that CPU resource
paths are determined using the option
-m
that maps HP-UX hardware paths to resource paths.
The first vPartition is configured with the AD221 Ethernet / Fibre channel combination card at
hardware address 48/0/0/2/0/0/2/0. Run the following command to view the configuration:
#
ioscan
–
m resourcepath | grep cpucore
1/120
0x100ff02ff000017
cpucore-1/2/0/0
1/122
0x100ff02ff000117
cpucore-1/2/0/1
1/124
0x100ff02ff000217
cpucore-1/2/0/2
1/126
0x100ff02ff000317
cpucore-1/2/0/3
1/128
0x100ff02ff010017
cpucore-1/2/1/0
1/130
0x100ff02ff010117
cpucore-1/2/1/1
1/132
0x100ff02ff010217
cpucore-1/2/1/2
1/134
0x100ff02ff010317
cpucore-1/2/1/3
or, for this example, run the following command.
#
# ioscan -m resourcepath | grep 48/0/0/2/0
48/0/0/2/0
0x900010002ffff8e
iorp-9/1/0/0/2
48/0/0/2/0/0
0x90001000203ff85
ioslot-9/1/3
Memory
There are two major types of memory addressing, Socket Local Memory, (SLM), and InterLeaved
Memory, (ILM). With SLM, entire memory address ranges are from a single socket. For best
performance, memory and CPU-cores from the same socket(s) should be assigned to a vPar. ILM
is an address range of memory whose adjacent addresses reside on one or more sockets in the
underlying nPartition.
Planning Your Virtual Partitions
77