HP Integrity Superdome 2 16-socket HP Superdome 2 Partitioning Administrator G - Page 83

CPU-core: Adding or Deleting by Resource Path, CPU: Summary Information, Table 7 CPU-core Allocation

Page 83 highlights

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 NOTE: When CPUs are added using the socket local syntax, they can be deleted only by using the socket local syntax. Adding or deleting CPUs by socket changes the total count of CPUs. CPU-core: Adding or Deleting by Resource Path To specify by resource path, use the following syntax: -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 existing and defined vPar using the vparstatus -v -p ) command. NOTE: When CPUs are added using the resource path syntax, they 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 Table 7 (page 83) lists the CPU resource paths in the following four ways: Table 7 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 Planning Your Virtual Partitions 83

  • 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
  • 107
  • 108
  • 109
  • 110

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
NOTE:
When CPUs are added using the socket local syntax, they can be deleted only by using
the socket local syntax. Adding or deleting CPUs by socket changes the total count of CPUs.
CPU-core: Adding or Deleting by Resource Path
To specify by resource path, use the following syntax:
-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 existing and
defined vPar using the
vparstatus -v -p <nPar_id:vPar_id>
) command.
NOTE:
When CPUs are added using the resource path syntax, they 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
Table 7 (page 83)
lists the CPU resource paths in the following four ways:
Table 7 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
Planning Your Virtual Partitions
83