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

CPU-core: Adding or Deleting by SLP (Socket Local Processor)

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 76 highlights

CPU-core: Adding or Deleting by SLP (Socket Local Processor) Similar to SLM (socket local memory), SLP (Socket local processor) refers to CPUs in a specific socket on a specific blade. This is generally used in conjunction with SLM to ensure that the cores and the memory are close to each other. The syntax to specify SLP is: -a, -d socket:socket_ID:cpu::num where: -a is adding -d is deleting socket_ID is the path (enclosure#/blade#/socket#) num is the number of CPU-cores from the socket to be added to or deleted from the virtual partition. Note that the num CPU-cores need to be available in the socket as well as in the nPartition before they can be added. To see whether they are available or already allocated, use the vparstatus -A command when the nPartition is booted in vPar mode. Examples • To create a virtual partition using 2 CPU-cores from socket 0 on blade 1: vparcreate -N -p -a socket:1/1/0:cpu::2 • To increase the number of CPU-cores by 2 using the CPU-cores from socket 0 on blade 1: vparmodify -N -p -a socket:1/1/0:cpu::2 To decrease the number of CPU-cores by 2 removing CPUs from socket 0 on blade 1: vparmodify -N -p -d socket:1/1/0:cpu::2 CPU-core: Adding or Deleting by Resource path The syntax for specifying by resource path is: -a, -d cpu:cpu_path where: -a is adding -d is deleting cpu_path is the resource path of the cpu (you can find the resource path of an already existing and defined vPar using the vparstatus -v -p ) command. NOTE: CPUs that are added using the resource path syntax can be deleted only by using the resource path syntax. Adding or deleting CPUs by path changes the total count of CPUs. Example • To add the CPU at 1/1/0/0 (enclosure 1, blade1, socket 0, core 0) and 1/1/0/1 to vPar0001: vparmodify -N -p -a cpu:1/1/0/0 -a cpu:1/1/0/1 CPU: Summary Information Impact on vPars Commands: Specifying CPU The CPU resource paths can be defined in the following four ways: 76 Planning Your System for Virtual Partitions

  • 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
CPU-core: Adding or Deleting by SLP (Socket Local Processor)
Similar to SLM (socket local memory), SLP (Socket local processor) refers to CPUs in a specific
socket on a specific blade. This is generally used in conjunction with SLM to ensure that the cores
and the memory are close to each other. The syntax to specify SLP is:
-a, -d socket:
socket_ID
:cpu::
num
where:
-a
is adding
-d
is deleting
socket_ID
is the path
(enclosure#/blade#/socket#)
num
is the number of CPU-cores from the socket to be added to or deleted from the
virtual partition. Note that the
num
CPU-cores need to be available in the socket
as well as in the nPartition before they can be added. To see whether they are
available or already allocated, use the
vparstatus -A
command when the
nPartition is booted in vPar mode.
Examples
•
To create a virtual partition using 2 CPU-cores from socket 0 on blade 1:
vparcreate -N <nPar name> -p <vPar name> -a socket:1/1/0:cpu::2
•
To increase the number of CPU-cores by 2 using the CPU-cores from socket 0 on blade 1:
vparmodify -N <nPar name> -p <vPar name> -a socket:1/1/0:cpu::2
To decrease the number of CPU-cores by 2 removing CPUs from socket 0 on blade 1:
vparmodify -N <nPar name> -p <vPar name> -d socket:1/1/0:cpu::2
CPU-core: Adding or Deleting by Resource path
The syntax for specifying by resource path is:
-a, -d cpu:
cpu_path
where:
-a
is adding
-d
is deleting
cpu_path
is the resource path of the cpu (you can find the resource path of an already existing
and defined vPar using the
vparstatus -v -p <nPar_id:vPar_id>
)
command.
NOTE:
CPUs that are added using the resource path syntax can be deleted only by using the
resource path syntax.
Adding or deleting CPUs by path changes the total count of CPUs.
Example
•
To add the CPU at
1/1/0/0
(enclosure 1, blade1, socket 0, core 0) and
1/1/0/1
to vPar0001:
vparmodify -N <nPar name> -p <vPar name> -a cpu:1/1/0/0 -a
cpu:1/1/0/1
CPU: Summary Information
Impact on vPars Commands: Specifying CPU
The CPU resource paths can be defined in the following four ways:
76
Planning Your System for Virtual Partitions