priocntl(1MSRM)

NAME | ADDENDUM | ATTRIBUTES | SEE ALSO | NOTES

NAME

priocntl- Solaris Resource Manager addendum to priocntl

ADDENDUM

The Solaris Resource Manager CPU scheduler (SHR) implements a per-process user priority and user priority limit. The external behavior and range of these parameters is compatible with the TS class. An approximately linear correspondence is maintained between the user priority and nice value (see nice(1) of processes in the SHR class. If the user priority range is -x to +x, then -x corresponds to maximum nice (19), a default user priority of 0 corresponds to default nice (0), and +x corresponds to nice -20. A change to either user priority or nice value causes the corresponding change to the other parameter.

The valid SHR class-specific options for setting time-sharing parameters are:

-m shruprilim

Set the user priority limit of the specified processes to shruprilim.

-p shrupri

Set the user priority of the specified processes to shrupri, and set their nice values correspondingly.

The valid range for the parameters can be displayed by using the command:

---

priocntl -l

---

The command:

---

priocntl -d

---

displays the user priority and user priority limit of selected processes.

A process in the SHR class that has a higher nice value gets a lower rate of CPU service than SHR class processes with lower nice values on the same lnode. Moreover, SHR class processes with higher nice values are charged at a lesser rate than SHR class processes with lower nice values.

The maximum nice value is treated specially. Processes in the SHR class with this value of nice are given CPU service only when no other processes are runnable.

Any SHR class process may set its own shrupri, or that of any other SHR class process with the same UID to any value less than or equal to the shruprilim of the target process. Only a process with superuser privileges may raise the shruprilim of a SHR class process.

Once a process belongs to the SHR scheduling class, only the superuser can move the process to another class.

Only the superuser can move processes into the SHR class. Normally the init process is started in the SHR scheduling class at system boot, and subsequent processes inherit membership of the SHR class.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Architecture	SPARC
Availability	SUNWsrmb

SEE ALSO

nice(1), priocntl(1), srm(5SRM)

Solaris Resource Manager 1.3 System Administration Guide

NOTES

This man page is applicable to SunOS 5.6, SunOS 5.7, and SunOS 5.8.

SunOS 5.8  Last Revised 7 Dec 1998

NAME | ADDENDUM | ATTRIBUTES | SEE ALSO | NOTES