Administering Resource Management in Oracle^® Solaris 11.4

Example: How to Change the Multi-CPU Binding Type

This example changes the binding type to strong bind.

Alternatively, you could instead delete the project.mcb.flag key, because the value is set to strong by default.

1. Assume the root role.

   For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.4.

2. Change the value of project.mcb.flags to strong.

   $ projmod -s -K project.mcb.flags=strong new-project

3. View the project.

   $ projects -l new-project
   new-project
           projid : 100
           comment: ""
           users  : (none)
           groups : (none)
           attribs: project.mcb.cpus=0,3-5,9-11
                    project.mcb.flags=strong

   ---

   Note -  By default, the projmod command only modifies the project configuration file. To apply the changes to the processes in the project, use the –A option.

   $ projmod -A new-project
   projmod: Updating project new-project succeeded with following warning message.
   WARNING: We bind the target project to the default pool of the zone because an MCB entry exists.

   The update was successful. However, at least one of the CPUs described in the project.mcb.cpus entry must exist in the system and be online. If a subset of the CPUs do not exist or are not online, these are not bound to, and warnings are printed.

   If you try to apply the attributes of the project to processes, an error message is displayed. For example, the following message displays if none of the specified CPUs 17-20 exist:

   ERROR: All of given multi-CPU binding (MCB) ids are not found in the system: project.mcb.cpus=17-20

   ---