xref: /titanic_50/usr/src/man/man1m/pbind.1m (revision 174bc6499d233e329ecd3d98a880a7b07df16bfa)
te
Copyright 2015 Ryan Zezeski
Copyright (c) 2008, Sun Microsystems, Inc.
All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
PBIND 1M "Feb 25, 2008"
NAME
pbind - control and query bindings of processes or LWPs
SYNOPSIS

pbind -b processor_id pid [/lwpid]...

pbind -e processor_id cmd [args...]

pbind [-q] [pid [/lwpid]]...

pbind -Q [processor_id]...

pbind -u pid [/lwpid]...

pbind -U [processor_id]...
DESCRIPTION

pbind controls and queries bindings of processes and LWPs (lightweight processes) to processors. pbind can also remove processor bindings that were previously established.

When an LWP is bound to a processor, it will be executed only by that processor except when the LWP requires a resource that is provided only by another processor. The binding is not exclusive, that is, the processor is free to execute other LWPs as well.

Bindings are inherited, so new LWPs and processes created by a bound LWP will have the same binding. Binding an interactive shell to a processor, for example, binds all commands executed by the shell.

The processor_id must be present and on-line. Use the psrinfo(1M) command to determine which processors are available.

Superusers may bind or unbind any process or LWP, while other users can bind or unbind any process or LWP for which they have permission to signal, that is, any process that has the same effective user ID as the user.

OPTIONS

The following options are supported: -b processor_id

Binds all or a subset of the LWPs of the specified processes to processor_id.

-e processor_id

Execute a command while bound to processor_id.

-q

Displays the bindings of the specified processes or of all processes. If a process is composed of multiple LWPs which have different bindings and the LWPs are not explicitly specified, the bindings of only one of the bound LWPs will be displayed. The bindings of a subset of LWPs can be displayed by appending "/lwpids" to the process IDs. Multiple LWPs may be selected using "-" and "," delimiters. See EXAMPLES.

-Q

Displays the LWPs bound to the specified list of processors, or all LWPs with processor bindings. For processes composed of multiple LWPs, the bindings of individual LWPs will be displayed.

-u

Removes the bindings of all or a subset of the LWPs of the specified processes, allowing them to be executed on any on-line processor.

-U

Removes the bindings of all LWPs bound to the specified list of processors, or to any processor if no argument is specified.

OPERANDS

The following operands are supported: pid

The process ID of the process to be controlled or queried.

lwpid

The set of LWP IDs of the specified process to be controlled or queried. The syntax for selecting LWP IDs is as follows:

2,3,4-8 LWP IDs 2, 3, and 4 through 8
-4 LWPs whose IDs are 4 or below
4- LWPs whose IDs are 4 or above
processor_id

The processor ID of the processor to be controlled or queried.

cmd [args...]

The command to execute along with optional arguments.

EXAMPLES

Example 1 Binding Processes

The following example binds processes 204 and 223 to processor 2:

example% pbind -b 2 204 223
process id 204: was 2, now 2
process id 223: was 3, now 2

Example 2 Unbinding a Process

The following example unbinds process 204:

example% pbind -u 204

Example 3 Querying Bindings

The following example queries bindings. It demonstrates that process 1 is bound to processor 0, process 149 has at least one LWP bound to CPU3, and process 101 has no bound LWPs.

example% pbind -q 1 149 101
process id 1: 0
process id 149: 3
process id 101: not bound

Example 4 Querying LWP Bindings

The following example queries bindings of LWPs. It demonstrates that LWP 1 of process 149 is bound to CPU3, and LWP 2 of process 149 is not bound.

example% pbind -q 149/1-2
lwp id 149/1: 3
lwp id 149/2: not bound

Example 5 Querying LWP Bindings for Processor 2:

The following example queries all LWPs bound to processor 2:

example% pbind -Q 2
lwp id 149/4: 2
lwp id 149/5: 2

Example 6 Executing a bound command:

The following example executes ls while bound to processor 6:

example% pbind -e 6 ls -la
EXIT STATUS

The following exit values are returned: 0

Successful completion.

>0

An error occurred.

SEE ALSO

psradm(1M), psrinfo(1M), psrset(1M), processor_bind(2), processor_info(2), sysconf(3C), attributes(5)

DIAGNOSTICS
pbind: cannot query pid 31: No such process

The process specified did not exist or has exited.

pbind: cannot bind pid 31: Not owner

The user does not have permission to bind the process.

pbind: cannot bind pid 31: Invalid argument

The specified processor is not on-line.

pbind: failed to exec cmd

Could not resolve the cmd from PATH.