Searched refs:cpumasks (Results 1 – 10 of 10) sorted by relevance
| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | padata.rst | 50 修改cpumasks
63 一个实例的cpumasks可能有sysfs文件。例如，pcrypt的文件在
73 并行和一个串行cpumask组成)。用户提供的cpumasks在实例分配时默认为所有可能的CPU，
74 并且可以如上所述进行更改。可用的cpumasks总是用户提供的cpumasks的一个子集，只包
75 含用户提供的掩码中的在线CPU；这些是padata实际使用的cpumasks。因此，向padata提
104 在其他地方正在搞乱实例的CPU掩码，而当cb_cpu不在串行cpumask中、并行或串行cpumasks
|
| /linux/kernel/sched/ |
| H A D | isolation.c | 25 struct cpumask __rcu *cpumasks[HK_TYPE_MAX]; member
60 return rcu_dereference_all_check(housekeeping.cpumasks[type], in housekeeping_cpumask_dereference()
143 rcu_assign_pointer(housekeeping.cpumasks[HK_TYPE_DOMAIN], trial); in housekeeping_update()
186 omask = rcu_dereference(housekeeping.cpumasks[type]); in housekeeping_init()
191 RCU_INIT_POINTER(housekeeping.cpumasks[type], nmask); in housekeeping_init()
202 RCU_INIT_POINTER(housekeeping.cpumasks[type], mask); in housekeeping_setup_type()
|
| /linux/Documentation/core-api/ |
| H A D | padata.rst | 42 Modifying cpumasks
57 There may be sysfs files for an instance's cpumasks. For example, pcrypt's
67 Padata maintains two pairs of cpumasks internally, the user-supplied cpumasks
68 and the 'usable' cpumasks. (Each pair consists of a parallel and a serial
69 cpumask.) The user-supplied cpumasks default to all possible CPUs on instance
70 allocation and may be changed as above. The usable cpumasks are always a
71 subset of the user-supplied cpumasks and contain only the online CPUs in the
72 user-supplied masks; these are the cpumasks padata actually uses. So it is
111 serial cpumask, no online CPUs in the parallel or serial cpumasks, or a stopped
|
| H A D | housekeeping.rst | 48 Housekeeping cpumasks
51 Housekeeping cpumasks include the CPUs that can execute the work moved
52 away by the matching isolation feature. These cpumasks are returned by
|
| /linux/Documentation/bpf/ |
| H A D | cpumasks.rst | 13 reflect the CPUs on the system. Commonly, cpumasks are used to track which CPUs
19 used to allocate, mutate, query, and free cpumasks.
24 There are two different types of cpumasks that can be used by BPF programs.
30 BPF program, and whose lifecycle is entirely controlled by BPF. These cpumasks
195 kfuncs for mutating and querying cpumasks.
197 3.1 Mutating cpumasks
205 argument. :ref:`cpumasks-querying-label` below describes the read-only kfuncs.
269 3.1.2 Operations between cpumasks
273 callers can also perform bitwise operations between multiple cpumasks using
347 3.2 Querying cpumasks
[all …]
|
| H A D | index.rst | 23 cpumasks
|
| /linux/Documentation/scheduler/ |
| H A D | sched-domains.rst | 21 pointer. The union of cpumasks of these groups MUST be the same as the
24 read only data after they have been set up. The intersection of cpumasks from
|
| /linux/Documentation/admin-guide/ |
| H A D | cputopology.rst | 101 kernel start parameter as well as more information on the various cpumasks.
|
| /linux/Documentation/accounting/ |
| H A D | taskstats.rst | 38 registered listener. Using cpumasks allows the data received by one listener
48 for reporting delay accounting statistics. Users can register cpumasks,
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 1720 The argument value is the standard cpulist format for cpumasks,
|