HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

181

182

183

184

185

186

187

188

189

190

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man2/!!!intro.2

________________________________________________________________

___ ___

mpctl(2) mpctl(2)

all domains in the system have been used by LWPs in this process. At that point,

the selection of locality domains begins again from the system wide pool of

domains. As with all launch policies, the LWP is bound to the locality domain on

which it was launched. The ldom argument is ignored.

MPC_SETLWP_FILL

This call establishes a ﬁll ﬁrst policy for the speciﬁed LWP. Fill ﬁrst indicates that

successive child LWPs are launched on the same locality domain as their parent

LWP until one LWP has been created for each processor in the domain. At that

point, a new locality domain is selected and successive LWPs launched there until

there is one LWP per processor. All domains in the system will be used before the

original domain is selected again. As with all launch policies, the LWP is bound to

the locality domain on which it was launched. The ldom argument is ignored.

MPC_SETLWP_PACKED

This call establishes a packed policy for the speciﬁed LWP. Packed indicates that

successive child LWPs are launched on the same locality domain as their parent

LWP. As with all launch policies, the LWP is bound to the locality domain on

which it was launched. The ldom argument is ignored.

MPC_SETLWP_LEASTLOAD

This call establishes a least loaded policy for the speciﬁed LWP. Least loaded indi-

cates that successive child LWPs are launched on the least loaded locality domain

in the system regardless of the location of their parent LWP. As with all launch

policies, the LWP is bound to the locality domain on which it was launched. The

ldom argument is ignored.

MPC_SETLWP_NONE

This call unsets any launch policy in the LWP. In removing a launch policy, the

LWP is no longer bound to the locality domain on which it was launched. The

ldom argument is ignored.

To change the processor assignment, locality domain assignment, or launch policy of another process, the

caller must be either a member of a group having PRIV_MPCTL access, have the same effective user id of

the target process, or be the super-user.

ERRORS

If mpctl fails, -1 will be returned. If mpctl is successful, the value returned will be as speciﬁed for that

command/option. Note: in some cases a negative number other than -1 may be returned that indicates a

successful return. In general, mpctl fails if one or more of the following is true:

[EINVAL] request is an illegal number.

[EINVAL] request is MPC_GETNEXTSPU

or MPC_GETNEXTSPU_SYS and spu identiﬁes the last

processor. Or request is

MPC_GETNEXTLDOM or MPC_GETNEXTLDOM_SYS and ldom

identiﬁes the last locality domain.

[ESRCH] pid or lwpid identiﬁes a process or LWP that does not exist.

[EINVAL] request is to bind a process or an LWP to a processor or locality domain that is not in the

processor set of the speciﬁed process or LWP.

[EPERM] request is MPC_SETPROCESS

, MPC_SETPROCESS_FORCE,orMPC_SETLDOM, spu is

not

MPC_SPUNOCHANGE or

MPC_LDOMNOCHANGE, pid identiﬁes another process, and

the caller is not the super-user, does not have the same effective user id of the target pro-

cess, or is not a member of a group having

PRIV_MPCTL access.

[EPERM] request is MPC_SETPROCESS_RR, MPC_SETPROCESS_FILL

MPC_SETPROCESS_PACKED, MPC_SETPROCESS_LEASTLOAD

,or

MPC_SETPROCESS_NONE, pid identiﬁes another process, and the caller is not the

super-user, does not have the same effective user id of the target process, or is not a

member of a group having PRIV_MPCTL access.