Technical data

Processor Sets (Psets) on nPartitions
Introduction to Psets
HP System Partitions Guide: Administration for nPartitions—rp7410
EMSP—[e-mail]
332
Locality Domain Count: 1
Processor Count : 5
Domain Processors
------ ----------
0 0 3 4 7 8
#
The System
Default Pset
When Pset software is installed, a system default Pset always exists that
gives all users access to the processors assigned to it. The default Pset is
Pset 0, which always has at least processor ID 0 assigned to it.
All processors are initially assigned to the default Pset until you
configure processors to belong to other Psets.
When a Pset is destroyed or when a processor is removed from a Pset,
the processors involved are assigned back to the default Pset.
Pset Attributes
and Access
Permissions
Each Pset has attributes that configure the Pset’s behavior in various
situations. These attributes also include “owner, group, and others”
access permissions similar to traditional HP-UX file permissions. The
default Pset’s attributes cannot be changed, but all other Psets can have
their attributes adjusted as needed.
Users who have write access for a Pset can modify some of the Pset’s
attributes, including attributes other than the access permissions. Each
Pset’s owner can modify the Pset’s access permissions.
The following users can modify all aspects of all non-default Psets in a
system: root, superuser, and users who belong to a group that has the
PSET privileged capability. These users can modify all Pset attributes,
modify all Pset processor assignments, and can create and destroy Psets.
The PSET privileged capability is established for a group by issuing the
setprivgrp command. For example, setprivgrp mygrp PSET applies
this privilege (and no other privileges) to the “mygrp” group. See the
setprivgrp (1M) manpage for details.
Pset Boot-Time
Configuration
When HP-UX boots on an nPartition that has Pset software installed, by
default all processors are assigned to the default Pset: Pset 0.
You can have multiple Psets established at boot time either by creating
HP-UX startup scripts that configure Psets, or by configuring Psets
through PRM and having PRM establish configurations at boot time.
HP Restricted / DRAFT
DRAFT NOV 2001