Solaris Containers: Resource Management and Solaris Zones Developer's Guide

Resource Controls Associated With a Project

Resource controls associated with a project include the following:

project.cpu-cap

In Solaris 10 8/07, the absolute limit on the amount of CPU resources that can be consumed by a project. A value of 100 means 100% of one CPU as the project.cpu-cap setting. A value of 125 is 125%, because 100% corresponds to one full CPU on the system when using CPU caps.

project.cpu-shares

The number of CPU shares that are granted to this project for use with the fair share scheduler, FSS(7).

project.max-crypto-memory

Total amount of kernel memory that can be used by libpkcs11 for hardware crypto acceleration. Allocations for kernel buffers and session-related structures are charged against this resource control.

project.max-locked-memory

Total amount of physical locked memory allowed.

Note that this resource control replaced project.max-device-locked-memory, which has been removed.

project.max-msg-ids

Maximum number of System V message queues allowed for a project.

project.max-port-ids

Maximum allowable number of event ports.

project.max-sem-ids

Maximum number of System V semaphores allowed for a project.

project.max-shm-ids

Maximum number of shared memory IDs allowed for this project.

project.max-msg-ids

Maximum number of message queue IDs allowed for this project.

project.max-shm-memory

Total amount of System V shared memory allowed for this project.

project.max-lwps

Maximum number of LWPs simultaneously available to this project.

project.max-tasks

Maximum number of tasks allowable in this project.

project.max-contracts

Maximum number of contracts allowed in this project.