HP Instant Capacity User's Guide for versions 8.x > Appendix A Special Considerations

Instant Capacity Compatibility with Processor Sets (HP-UX)

  Table of Contents

  Index

Overview

The Instant Capacity software successfully co-exists with processor sets (Psets).

To co-exist with Psets, the Instant Capacity software only activates and deactivates cores in the default processor set. Cores in non-default processor sets are not activated or deactivated.

NOTE: There must be at least one core in the default processor set. The last remaining core in the default processor set is unavailable for deactivation.

Scope of the Instant Capacity Software Interacting with Psets

The Instant Capacity software does not provide any additional functionality to specifically support adding or removing cores from a specific Pset.

Psets on nPars

In an nPar environment where Psets are present, the Instant Capacity software only activates and deactivates cores in the default Pset.

Cores can be manually migrated to the default Pset for purposes of deactivation, or from the default Pset to other Psets after activation.

Psets on vPars

In a vPar environment, the Instant Capacity software passes the request for a core activation or deactivation to the vparmodify command.

With vPars version A.04.01 or greater, vPars is Pset-aware to an extent. When adding cores to a running vPar, a core is always added to the default Pset; thereafter, it may be moved to another Pset. When removing cores, vparmodify will choose cores from the default Pset first, and if not enough exist in the default Pset to satisfy the request, vparmodify chooses the remaining cores arbitrarily, without regard to Pset membership.

With vPars versions less than A.04, no special consideration is given to Psets from the vparmodify command’s perspective. Therefore, when using vPars, cores in non-default Psets must be bound cores. Otherwise, a core designated for deactivation by vparmodify may be selected from an unexpected Pset.