Searched full:policies (Results 1 – 25 of 50) sorted by relevance
12
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 17 Memory policies should not be confused with cpusets
20 memory may be allocated by a set of processes. Memory policies are a
22 both cpusets and policies are applied to a task, the restrictions of the cpuset
23 takes priority. See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
29 Scope of Memory Policies
63 In a multi-threaded task, task policies apply only to the thread
90 VMA policies have a few complicating details:
102 * VMA policies are shared between all tasks that share a
105 fork(). However, because VMA policies refer to a specific
107 space is discarded and recreated on exec*(), VMA policies
[all …]
|
| /Documentation/filesystems/ |
| D | fscrypt.rst | 148 Limitations of v1 policies
151 v1 encryption policies have some weaknesses with respect to online
167 All the above problems are fixed with v2 encryption policies. For
169 policies on all new encrypted directories.
212 the key is used for v1 encryption policies or for v2 encryption
213 policies. Users **must not** use the same key for both v1 and v2
214 encryption policies. (No real-world attack is currently known on this
218 For v1 encryption policies, the KDF only supports deriving per-file
224 For v2 encryption policies, the KDF is HKDF-SHA512. The master key is
259 DIRECT_KEY policies
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 2 Guidance for writing policies
7 makes it easier to write the policies.
26 Overview of supplied cache replacement policies
|
| D | index.rst | 8 cache-policies
|
| D | cache.rst | 158 Policies will have different tunables, specific to each one, so we
160 messages are used. Refer to cache-policies.txt.
199 See cache-policies.txt for details.
295 Policies will have different tunables, specific to each one, so we
|
| /Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
|
| D | SafeSetID.rst | 100 applicable restriction policy is in place. Policies are configured through
109 Note on GID policies and setgroups()
116 policies add no meaningful security. setgroups() restrictions will be enforced
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-intro.rst | 31 implementing policies that belong to userspace.
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy | 5 This group contains policies mandating Master/Channel allocation
|
| D | ima_policy | 10 Policies are loaded into the securityfs file ima/policy
|
| D | sysfs-fs-f2fs | 70 policies. It is used by F2FS_IPU_UTIL and F2FS_IPU_SSR_UTIL policies.
76 policies.
|
| /Documentation/driver-api/ |
| D | spi.rst | 44 policies for how they use the bits transferred with SPI.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 8 a need of various kinds of IO control policies (like proportional BW, max BW)
11 and based on user options switch IO policies in the background.
292 Common files among various policies
|
| D | pids.rst | 23 Organisational operations are not blocked by cgroup policies, so it is possible
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 73 Further details of specific enforcement policies may be posted
|
| /Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 41 object corresponds to one logical CPU and ``CPUFreq`` policies are effectively
70 ``scaling_driver`` policy attribute in ``sysfs`` for all ``CPUFreq`` policies
75 can be applied to ``CPUFreq`` policies in the same way as generic scaling
78 different policies, but that is not recommended.]
209 ``sysfs`` for all ``CPUFreq`` policies contains the string "intel_cpufreq".
717 scaling governor (for the policies it is attached to), or by the ``CPUFreq``
718 core (for the policies with other scaling governors).
|
| /Documentation/scheduler/ |
| D | sched-design-CFS.rst | 119 5. Scheduling policies
122 CFS implements three scheduling policies:
|
| /Documentation/cpu-freq/ |
| D | core.rst | 33 Reference counting of the cpufreq policies is done by cpufreq_cpu_get
|
| /Documentation/driver-api/mei/ |
| D | iamt.rst | 22 on policies set by a remote management console
|
| /Documentation/bpf/ |
| D | bpf_lsm.rst | 10 policies using eBPF.
|
| /Documentation/vm/ |
| D | frontswap.rst | 28 conform to certain policies as follows:
163 backend, such as zcache, must implement policies to carefully (but
|
| D | zswap.rst | 97 Zswap seeks to be simple in its policies. Sysfs attributes allow for one user
|
| /Documentation/driver-api/usb/ |
| D | hotplug.rst | 30 Those triggered actions must support a system's administrative policies;
|
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 54 to support multiple security policies. This Internet Draft provides the
56 security policy. Support for additional security policies shall be
510 policies may require both incoming and outgoing datagrams be checked against
|
12