Physical Memory Control and the capped-memory Resource - Introduction to Oracle® Solaris Zones

Language:

Physical Memory Control and the `capped-memory` Resource

The capped-memory resource sets limits for physical, swap, and locked memory. Each limit is optional, but at least one must be set. To use the capped-memory resource, the resource-cap package must be installed in the global zone. Also see capped-cpu Resource.

Determine values for this resource if you plan to cap memory for the zone by using rcapd from the global zone. The physical property of the capped-memory resource is used by rcapd as the max-rss value for the zone.
The swap property of the capped-memory resource is the preferred way to set the zone.max-swap resource control.
The locked property of the capped-memory resource is the preferred way to set the zone.max-locked-memory resource control.

Note - Applications generally do not lock significant amounts of memory, but you might decide to set locked memory if the zone's applications are known to lock memory. If zone trust is a concern, you can also consider setting the locked memory cap to 10 percent of the system's physical memory, or 10 percent of the zone's physical memory cap.

For more information, see Chapter 10, About Physical Memory Control Using the Resource Capping Daemon, in Administering Resource Management in Oracle Solaris 11.2 , Chapter 11, Administering the Resource Capping Daemon Tasks, in Administering Resource Management in Oracle Solaris 11.2 , and How to Configure the Zone in Creating and Using Oracle Solaris Zones . To temporarily set a resource cap for a zone, see How to Specify a Temporary Resource Cap for a Zone in Administering Resource Management in Oracle Solaris 11.2 .