| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 2 NUMA Memory Policy
5 What is NUMA Memory Policy?
8 In the Linux kernel, "memory policy" determines from which node the kernel will
11 The current memory policy support was added to Linux 2.6 around May 2004. This
12 document attempts to describe the concepts and APIs of the 2.6 memory policy
24 Memory Policy Concepts
30 The Linux kernel supports _scopes_ of memory policy, described here from
33 System Default Policy
34 this policy is "hard coded" into the kernel. It is the policy
36 one of the more specific policy scopes discussed below. When
[all …]
|
| D | hugetlbpage.rst | 179 over all the set of allowed nodes specified by the NUMA memory policy of the
181 task has default memory policy--is all on-line nodes with memory. Allowed
185 of the interaction of task memory policy, cpusets and per node attributes
220 across all nodes in the memory policy of the task modifying ``nr_hugepages``.
284 Interaction of Task Memory Policy with Huge Page Allocation/Freeing
290 NUMA memory policy of the task that modifies the ``nr_hugepages_mempolicy``
310 memory policy mode--bind, preferred, local or interleave--may be used. The
317 However, if a node in the policy does not contain sufficient contiguous
322 the task's memory policy.
324 #. One or more nodes may be specified with the bind or interleave policy.
[all …]
|
| /Documentation/security/ |
| D | ipe.rst | 3 Integrity Policy Enforcement (IPE) - Kernel Documentation
20 policy. A mandatory access control system would be present, and
41 enforce the integrity policy, or it should not.
44 policy would indicate what labels required integrity verification, which
48 file should be subject to integrity policy.
75 The next step was to choose a *policy* to enforce the integrity mechanism.
76 The minimum requirements for the policy were:
78 1. The policy itself must be integrity verified (preventing trivial
80 2. The policy itself must be resistant to rollback attacks.
81 3. The policy enforcement must have a permissive-like mode.
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy | 1 What: /config/stp-policy
9 What: /config/stp-policy/<device>.<policy>
13 This group is the root of a policy; its name is a concatenation
14 of an stm device name to which this policy applies and an
17 has a policy assigned to it, mkdir will fail with EBUSY.
19 What: /config/stp-policy/<device>.<policy>/device
23 STM device to which this policy applies, read only. Same as the
26 What: /config/stp-policy/<device>.<policy>/<node>
30 Policy node is a string identifier that software clients will
34 What: /config/stp-policy/<device>.<policy>/<node>/masters
[all …]
|
| D | configfs-stp-policy-p_sys-t | 1 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/uuid
13 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/do_len
23 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/ts_interval
32 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/clocksync_interval
|
| D | ima_policy | 1 What: /sys/kernel/security/*/ima/policy
9 the policy can be constrained based on LSM specific data.
10 Policies are loaded into the securityfs file ima/policy
12 then closing the file. The new policy takes effect after
13 the file ima/policy is closed.
80 default policy:
121 The default policy measures all executables in bprm_check,
124 policy appraises all files owned by root.
188 All of these policy rules could, for example, be constrained
|
| D | sysfs-platform-wilco-ec | 5 Boot on AC is a policy which makes the device boot from S5
38 Control the USB PowerShare Policy. USB PowerShare is a policy
|
| /Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 48 .init - A pointer to the per-policy initialization function.
68 .exit - A pointer to a per-policy cleanup function called during
71 .suspend - A pointer to a per-policy suspend function which is called
73 policy.
75 .resume - A pointer to a per-policy resume function which is called
78 .ready - A pointer to a per-policy ready function which is called after
79 the policy is fully initialized.
86 .set_boost - A pointer to a per-policy function to enable/disable boost
94 cpufreq driver registers itself, the per-policy initialization function
95 cpufreq_driver.init is called if no cpufreq policy existed for the CPU.
[all …]
|
| D | core.rst | 27 policy changes (ex. thermal modules like ACPI) or of all
37 policy doesn't get freed while being used.
45 There are two different CPUFreq notifiers - policy notifiers and
49 2.1 CPUFreq policy notifiers
52 These are notified when a new policy is created or removed.
55 CPUFREQ_CREATE_POLICY when the policy is first created and it is
56 CPUFREQ_REMOVE_POLICY when the policy is removed.
60 frequencies (in kHz) of the new policy).
66 These are notified twice for each online CPU in the policy, when the
77 policy a pointer to the struct cpufreq_policy
[all …]
|
| /Documentation/trace/ |
| D | sys-t.rst | 15 a policy for your STM device, by specifying it in the policy name:
17 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/
19 In other words, the policy name format is extended like this:
23 With Intel TH, therefore it can look like "0-sth:p_sys-t.my-policy".
30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
33 Now, with the MIPI SyS-T protocol driver, each policy node in the
37 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
38 # ls /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
59 See Documentation/ABI/testing/configfs-stp-policy-p_sys-t for more
|
| D | stm.rst | 26 To solve this mapping problem, stm class provides a policy management
28 identifiers to ranges of masters and channels. If these rules (policy)
32 This policy is a tree structure containing rules (policy_node) that
34 associated with it, located in "stp-policy" subsystem directory in
35 configfs. The topmost directory's name (the policy) is formatted as
36 the STM device name to which this policy applies and an arbitrary
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
44 $ cat /config/stp-policy/dummy_stm.my-policy/user/channels
60 In order to find an appropriate policy node for a given trace source,
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 85 ``CPUFreq`` Policy Objects
104 of its user space interface is based on the policy concept.
129 Once invoked, the ``CPUFreq`` core checks if the policy pointer is already set
130 for the given CPU and if so, it skips the policy object creation. Otherwise,
131 a new policy object is created and initialized, which involves the creation of
132 a new policy directory in ``sysfs``, and the policy pointer corresponding to
133 the given CPU is set to the new policy object's address in memory.
135 Next, the scaling driver's ``->init()`` callback is invoked with the policy
139 to, represented by its policy object) and, if the policy object it has been
140 called for is new, to set parameters of the policy, like the minimum and maximum
[all …]
|
| D | intel_pstate.rst | 40 CPUs. Consequently, if ``intel_pstate`` is in use, every ``CPUFreq`` policy
70 ``scaling_driver`` policy attribute in ``sysfs`` for all ``CPUFreq`` policies
76 governors (that is, through the ``scaling_governor`` policy attribute in
108 selection algorithm has been applied to the given policy (or to the CPU it
115 be made available from the ``scaling_cur_freq`` policy attribute in ``sysfs``.
157 ``powersave`` or ``performance``, depending on the ``scaling_governor`` policy
159 available from the ``scaling_cur_freq`` policy attribute in ``sysfs`` is
208 If the driver works in this mode, the ``scaling_driver`` policy attribute in
216 scaling governors listed by the ``scaling_available_governors`` policy attribute
218 used). Then, it is responsible for the configuration of policy objects
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 9 Mappings are loaded into the policy at construction time.
11 Every bio that is mapped by the target is referred to the policy.
12 The policy can return a simple HIT or MISS or issue a migration.
14 Currently there's no way for the policy to issue background work,
18 Because we map bios, rather than requests it's easy for the policy
20 issues periodic ticks to the policy. It's suggested that the policy
32 This policy is now an alias for smq (see below).
45 This policy is the default.
47 The stochastic multi-queue (smq) policy addresses some of the problems
48 with the multiqueue (mq) policy.
[all …]
|
| D | cache.rst | 24 policy module. Several of these have been written as we experiment,
41 (depending on policy).
57 which are dirty, and extra hints for use by the policy object.
106 A simple cleaner policy is provided, which will clean (write back) all
145 Per-block policy hints
148 Policy plug-ins can store a chunk of data per cache block. It's up to
149 the policy how big this chunk is, but it should be kept small. Like the
153 Policy hints affect performance, not correctness.
155 Policy messaging
183 <policy> <#policy args> [policy args]*
[all …]
|
| /Documentation/netlink/specs/ |
| D | nlctrl.yaml | 77 name: policy
79 type-value: [ policy-id, attr-id ]
80 nested-attributes: policy-attrs
82 name: op-policy
85 nested-attributes: op-policy-attrs
114 name: policy-attrs
115 name-prefix: nl-policy-type-attr-
141 name: policy-idx
144 name: policy-maxtype
156 name: op-policy-attrs
[all …]
|
| /Documentation/translations/zh_CN/cpu-freq/ |
| D | cpu-drivers.rst | 103 *policy`` 作为参数。现在该怎么做呢？
110 |policy->cpuinfo.min_freq和 | 该CPU支持的最低和最高频率（kHz） |
111 |policy->cpuinfo.max_freq | |
114 |policy->cpuinfo.transition_latency | CPU在两个频率之间切换所需的时间，以 |
119 |policy->cur | 该CPU当前的工作频率(如适用) |
122 |policy->min, | 必须包含该CPU的"默认策略"。稍后 |
123 |policy->max, | 会用这些值调用 |
124 |policy->policy and, if necessary, | cpufreq_driver.verify和下面函数 |
125 |policy->governor | 之一：cpufreq_driver.setpolicy或 |
129 |policy->cpus | 该policy通过DVFS框架影响的全部CPU |
[all …]
|
| /Documentation/translations/zh_TW/cpu-freq/ |
| D | cpu-drivers.rst | 103 *policy`` 作爲參數。現在該怎麼做呢？
110 |policy->cpuinfo.min_freq和 | 該CPU支持的最低和最高頻率（kHz） |
111 |policy->cpuinfo.max_freq | |
114 |policy->cpuinfo.transition_latency | CPU在兩個頻率之間切換所需的時間，以 |
119 |policy->cur | 該CPU當前的工作頻率(如適用) |
122 |policy->min, | 必須包含該CPU的"默認策略"。稍後 |
123 |policy->max, | 會用這些值調用 |
124 |policy->policy and, if necessary, | cpufreq_driver.verify和下面函數 |
125 |policy->governor | 之一：cpufreq_driver.setpolicy或 |
129 |policy->cpus | 該policy通過DVFS框架影響的全部CPU |
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 7 latest reference policy release from
11 However, if you want to install a dummy policy for
21 SELinux enabled and a real policy. If
29 Step 4 will create a new dummy policy valid for your
31 It will compile the policy, will set your ``SELINUXTYPE`` to
32 ``dummy`` in ``/etc/selinux/config``, install the compiled policy
|
| D | ipe.rst | 3 Integrity Policy Enforcement (IPE)
15 Integrity Policy Enforcement (IPE) is a Linux Security Module that takes a
45 For the IPE policy, specifically, it grants the ability to enforce
47 reference values defined within the policy. This assessment can be based on
54 nuanced approach to policy enforcement enables a highly secure and
59 :menuselection:`Security -> Integrity Policy Enforcement (IPE)`) config
116 policy. If a binary does not pass this verification process, either
120 resulting from policy violation.
140 Policy chapter
143 IPE policy is a plain-text [#devdoc]_ policy composed of multiple statements
[all …]
|
| D | SafeSetID.rst | 100 applicable restriction policy is in place. Policies are configured through
103 mounted. The format for adding a policy is '<UID>:<UID>' or '<GID>:<GID>',
105 Writing an empty string "" will flush the policy. Again, configuring a policy
117 once we have the policy checking code in place, which will rely on GID policy
|
| /Documentation/networking/ |
| D | ipsec.rst | 13 policy check on receiver.
17 2.2. Non-Expansion Policy
24 IPComp header is added to the datagram. This policy ensures saving
38 packet len), the packet is dropped when checking the policy as this packet
44 One workaround is try to set "level use" for each policy if user observed
46 will skip policy checking on receiver side.
|
| D | xfrm_proc.rst | 61 No policy is found for states
65 Policy discards
68 Policy error
107 Policy discards
110 Policy is dead
113 Policy error
|
| /Documentation/filesystems/ |
| D | fscrypt.rst | 182 policy and AES-256-XTS is used; such keys must be 64 bytes.
269 this by setting FSCRYPT_POLICY_FLAG_DIRECT_KEY in the fscrypt policy,
285 When FSCRYPT_POLICY_FLAG_IV_INO_LBLK_64 is set in the fscrypt policy,
476 the encryption policy; see `FS_IOC_SET_ENCRYPTION_POLICY`_.
553 Setting an encryption policy
559 The FS_IOC_SET_ENCRYPTION_POLICY ioctl sets an encryption policy on an
561 has the specified encryption policy. It takes in a pointer to
593 policy version as "v1", though its version code is really 0.)
670 encryption policy is assigned to the directory, turning it into an
674 directory will be encrypted, inheriting the same encryption policy.
[all …]
|
| D | tmpfs.rst | 160 tmpfs has a mount option to set the NUMA memory allocation policy for
165 mpol=default use the process allocation policy
178 A memory policy with a valid NodeList will be saved, as specified, for
180 system, the mount option memory policy will be applied with a NodeList,
184 memory policy for the file will revert to "default" policy.
190 all available memory allocation policy mode flags and their effect on
191 memory policy.
199 allocation policy of MPOL_BIND | MPOL_F_STATIC_NODES.
208 on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
|