The tasks in this section explain how to create a new domain with CPU whole cores, how to configure an existing domain with CPU whole cores, and how to configure the primary domain with CPU whole cores.
Use the following command to configure a domain to use CPU whole cores:
ldm set-core number-of-CPU-cores domain
This command also specifies the maximum number of CPU cores for the domain, which is max-cores. See the ldm(1M) man page.
Max-cores and the allocation of CPU cores is handled by separate commands. By using these commands, you can independently allocate CPU cores, set a cap, or both. The allocation unit can be set to cores even when no max-cores is in place. However, running the system in this mode is not acceptable for configuring hard partitioning on your Oracle VM Server for SPARC system.
Allocate the specified number of CPU cores to a domain by using the add-core, set-core, or remove-core subcommand.
Set the max-cores by using the create-domain or set-domain subcommand to specify the max-cores property value.
You must set the cap if you want to configure hard partitioning on your Oracle VM Server for SPARC system.
primary# ldm add-domain domain-name
primary# ldm set-core number-of-CPU-cores domain
primary# ldm set-domain max-cores=max-number-of-CPU-cores domain
During this configuration, ensure that you use the ldm add-core, ldm set-core, or ldm remove-core command.
primary# ldm bind domain-name primary# ldm start-domain domain-name
This example creates a domain, ldg1, with two CPU whole cores. The first command creates the ldg1 domain. The second command configures the ldg1 domain with two CPU whole cores.
At this point, you can perform further configuration on the domain, subject to the restrictions described in Step 3 in How to Create a New Domain With CPU Whole Cores.
The third and fourth commands show how to bind and start the ldg1 domain, at which time you can use the ldg1 domain.
primary# ldm add-domain ldg1 primary# ldm set-core 2 ldg1 ... primary# ldm bind ldg1 primary# ldm start-domain ldg1
If a domain already exists and is configured to use CPU threads, you can change its configuration to use CPU whole cores.
This step is required only if you also set the max-cores constraint.
primary# ldm stop domain-name primary# ldm unbind domain-name
primary# ldm set-core number-of-CPU-cores domain
primary# ldm set-domain max-cores=max-number-of-CPU-cores domain
This step is required only if you also set the max-cores constraint.
primary# ldm bind domain-name primary# ldm start-domain domain-name
This example updates the configuration of an existing domain, ldg1 by configuring it with four CPU whole cores.
primary# ldm set-core 4 ldg1
If the primary domain is configured to use CPU threads, you can change its configuration to use CPU whole cores.
You need to initiate a delayed reconfiguration only if you want to modify the max-cores property.
primary# ldm start-reconf primary
primary# ldm set-core number-of-CPU-cores primary
primary# ldm set-domain max-cores=max-number-of-CPU-cores primary
Use the appropriate procedure to reboot the primary domain depending on the system configuration. See Rebooting the Root Domain With PCIe Endpoints Configured.
You need to reboot the domain only if you want to modify the max-cores property.
This example configures CPU whole cores on the primary domain. The first command initiates delayed reconfiguration mode on the primary domain. The second command configures the primary domain with two CPU whole cores. The third command sets the max-cores property to 2, and the fourth command reboots the primary domain.
primary# ldm start-reconf primary primary# ldm set-core 2 primary primary# ldm set-domain max-cores=2 primary primary# shutdown -i 5
The optional Steps 1 and 4 are required only if you want to modify the max-cores property.