HP-UX 11i June 2002 Release Notes

HP-UX 11i Operating Environment Applications
HP-UX 11i Enterprise Operating Environment (EOE)
Chapter 6
106
NOTE Process Resource Manager and HP-UX Workload Manager both make use of the PRM
API. Consequently, only one of the products should be used at a time. (See also “HP-UX
Workload Manager” on page 109.)
updated for
June 2002
HP PRM version C.02.00.02 provides the following:
• The xprm command has a logging option, -l, that creates the file xprm.log for
information on xprm execution, which may be useful in diagnosing a problem.
• The prm2d memory manager has been improved.
updated for
September 2001
HP PRM version C.02.00 provides the following:
• new memory features
— in-kernel memory management
— dedicated memory for PRM groups
— proportional overachievement for PRM groups
— memory isolation - PRM uses the prm2d memory manager to optionally specify
that a group’s memory cannot be used by other groups and processes on the
system.
• support for processor sets
— HP PRM introduces a new type of PRM group, called a PSET PRM group, that is
based on processor sets. The PSET PRM’s CPU entitlement is specified by
assigning it to a subset of the system’s processors.
• prmanalyze updated to perform new functionality
• new PRM toolset for SCM
NOTE Processor Sets can be installed from the December 2001 Software Pack (Optional HP-UX
11i Core Enhancements) CD included in your HP-UX 11i December 2001 media kit. You
can also download Processor Sets from the HP Software Depot at
http://software.hp.com.
new at 11i
original release
With version C.01.08.02, PRM provides the following features:
• Distribution of resources through hierarchical PRM groups
• Provides a shares model of distributing resources instead of static percentages. This
model facilitates configuration changes. PRM groups can be nested, allowing for
more convenient partitioning.
• Memory controlled in the kernel, through the prm2d daemon, rather than in user
space, through the prm0d daemon.
• Syntax for memory records is essentially the same, with the only difference being
that the optional SUPPRESS field is no longer needed and is ignored if present:
#!PRM_MEM:{PRMID|GROUP}:SHARES:[CAP]:::