Print this page
9842 man page typos and spelling
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man2/pset_bind.2.man.txt
+++ new/usr/src/man/man2/pset_bind.2.man.txt
1 1 PSET_BIND(2) System Calls PSET_BIND(2)
2 2
3 3
4 4
5 5 NAME
6 6 pset_bind - bind LWPs to a set of processors
7 7
8 8 SYNOPSIS
9 9 #include <sys/pset.h>
10 10
11 11 int pset_bind(psetid_t pset, idtype_t idtype, id_t id, psetid_t *opset);
12 12
13 13
14 14 DESCRIPTION
15 15 The pset_bind() function binds the LWP or set of LWPs specified by
16 16 idtype and id to the processor set specified by pset. If opset is not
17 17 NULL, pset_bind() sets the psetid_t variable pointed to by opset to the
18 18 previous processor set binding of one of the specified LWP, or to
19 19 PS_NONE if the selected LWP was not bound.
20 20
21 21
22 22 If idtype is P_PID, the binding affects all LWPs of the process with
23 23 process ID (PID) id.
24 24
25 25
26 26 If idtype is P_LWPID, the binding affects the LWP of the current
27 27 process with LWP ID id.
28 28
29 29
30 30 If idtype is P_TASKID, the binding affects all LWPs of all processes
31 31 with task ID id.
32 32
33 33
34 34 If idtype is P_PROJID, the binding affects all LWPs of all processes
35 35 with project ID id.
36 36
37 37
38 38 If idtype is P_ZONEID, the binding affects all LWPs of all processes
39 39 with zone ID id.
40 40
41 41
42 42 If idtype is P_CTID, the binding affects all LWPs of all processes with
43 43 process contract ID id.
44 44
45 45
46 46 If id is P_MYID, the specified LWP, process, task, process, zone, or
47 47 process contract is the current one.
48 48
49 49
50 50 If pset is PS_NONE, the processor set bindings of the specified LWPs
51 51 are cleared.
52 52
53 53
54 54 If pset is PS_QUERY, the processor set bindings are not changed.
55 55
56 56
57 57 If pset is PS_MYID, the specified LWPs are bound to the same processor
58 58 set as the caller. If the caller is not bound to a processor set, the
59 59 processor set bindings are cleared.
60 60
61 61
62 62 The {PRIV_SYS_RES_CONFIG} privilege must be asserted in the effective
63 63 set of the calling process or pset must be PS_QUERY.
64 64
65 65
66 66 LWPs that have been bound to a processor with processor_bind(2) may
67 67 also be bound to a processor set if the processor is part of the
68 68 processor set. If this occurs, the binding to the processor remains in
69 69 effect. If the processor binding is later removed, the processor set
70 70 binding becomes effective.
71 71
72 72
73 73 Processor set bindings are inherited across fork(2) and exec(2).
74 74
75 75 RETURN VALUES
76 76 Upon successful completion, 0 is returned. Otherwise, -1 is returned
77 77 and errno is set to indicate the error.
78 78
79 79 ERRORS
80 80 The pset_bind() function will fail if:
81 81
82 82 EBUSY
83 83 One of the LWPs is bound to a processor, and the specified
84 84 processor set does not include that processor.
85 85
86 86
87 87 EFAULT
88 88 The location pointed to by opset was not NULL and not
89 89 writable by the user.
90 90
91 91
92 92 EINVAL
93 93 An invalid processor set ID was specified; or idtype was
94 94 not P_PID, P_LWPID, P_PROJID, P_TASKID, P_ZONEID, or P_CTID.
95 95
96 96
97 97 ENOTSUP
98 98 The pools facility is active. See pooladm(1M) and
|
↓ open down ↓ |
98 lines elided |
↑ open up ↑ |
99 99 pool_set_status(3POOL) for information about enabling and
100 100 disabling the pools facility. Processes can be bound to
101 101 pools using the poolbind(1M) utility or the
102 102 pool_set_binding(3POOL) function.
103 103
104 104 Binding a system process to a processor set is not
105 105 supported.
106 106
107 107
108 108 EPERM
109 - The {PRIV_PROC_OWNER} is not asserted in the effecive set of
110 - the calling process and either the real or effective user ID
111 - of the calling process does not match the real or effective
112 - user ID of one of the LWPs being bound, or the processor set
113 - from which one or more of the LWPs are being unbound has the
114 - PSET_NOESCAPE attribute set and {PRIV_SYS_RES_CONFIG) is not
115 - asserted in the effective set of the calling process. See
116 - pset_setattr(2) for more information about processor set
117 - attributes.
109 + The {PRIV_PROC_OWNER} is not asserted in the effective set
110 + of the calling process and either the real or effective user
111 + ID of the calling process does not match the real or
112 + effective user ID of one of the LWPs being bound, or the
113 + processor set from which one or more of the LWPs are being
114 + unbound has the PSET_NOESCAPE attribute set and
115 + {PRIV_SYS_RES_CONFIG) is not asserted in the effective set
116 + of the calling process. See pset_setattr(2) for more
117 + information about processor set attributes.
118 118
119 119
120 120 ESRCH
121 121 No processes, LWPs, or tasks were found to match the
122 122 criteria specified by idtype and id.
123 123
124 124
125 125 ATTRIBUTES
126 126 See attributes(5) for descriptions of the following attributes:
127 127
128 128
129 129
130 130
131 131 +--------------------+-------------------+
132 132 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
133 133 +--------------------+-------------------+
134 134 |Interface Stability | Committed |
135 135 +--------------------+-------------------+
136 136 |MT-Level | Async-Signal-Safe |
137 137 +--------------------+-------------------+
138 138
139 139 SEE ALSO
140 140 pbind(1M), pooladm(1M), poolbind(1M), psrset(1M), exec(2), fork(2),
141 141 processor_bind(2), pset_create(2), pset_info(2), pset_setattr(2),
142 142 pool_set_binding(3POOL), pool_set_status(3POOL), pset_getloadavg(3C),
143 143 process(4), project(4), attributes(5), privileges(5)
144 144
145 145
146 146
147 147 March 13, 2009 PSET_BIND(2)
|
↓ open down ↓ |
20 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX