| /Linux-v5.4/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_guc_ads.c | 27 static void guc_policies_init(struct guc_policies *policies) in guc_policies_init() argument
32 policies->dpc_promote_time = POLICY_DEFAULT_DPC_PROMOTE_TIME_US; in guc_policies_init()
33 policies->max_num_work_items = POLICY_MAX_NUM_WI; in guc_policies_init()
37 policy = &policies->policy[p][i]; in guc_policies_init()
43 policies->is_valid = 1; in guc_policies_init()
60 struct guc_policies policies; member
77 guc_policies_init(&blob->policies); in __guc_ads_init()
119 blob->ads.scheduler_policies = base + ptr_offset(blob, policies); in __guc_ads_init()
|
| /Linux-v5.4/tools/testing/selftests/cpufreq/ |
| D | cpufreq.sh | 31 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
32 for policy in $policies; do
39 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
40 for policy in $policies; do
|
| /Linux-v5.4/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
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
109 applications may use VMA policies.
125 Conceptually, shared policies apply to "memory objects" mapped
[all …]
|
| /Linux-v5.4/tools/perf/trace/beauty/ |
| D | sched_policy.c | 22 const char *policies[] = { in syscall_arg__scnprintf_sched_policy() local
31 printed = scnprintf(bf, size, "%s%s", show_prefix ? prefix : "", policies[policy]); in syscall_arg__scnprintf_sched_policy()
|
| /Linux-v5.4/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
280 - For v1 encryption policies, the encryption is done directly with the
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | index.rst | 8 cache-policies
|
| D | cache-policies.rst | 2 Guidance for writing policies
7 makes it easier to write the policies.
26 Overview of supplied cache replacement policies
|
| /Linux-v5.4/Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | configfs-stp-policy | 5 This group contains policies mandating Master/Channel allocation
|
| D | sysfs-fs-f2fs | 45 policies.
52 policies.
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | media-controller-intro.rst | 38 implementing policies that belong to userspace.
|
| /Linux-v5.4/fs/nfsd/ |
| D | Kconfig | 143 SELinux and Smack to label files to facilitate enforcement of their policies.
147 Smack policies on NFSv4 files, say N.
|
| /Linux-v5.4/block/ |
| D | Kconfig | 91 the IO rate to a device. IO rate policies are per cgroup and
93 cgroups and specifying per device IO rate policies.
|
| /Linux-v5.4/net/xfrm/ |
| D | Kconfig | 44 one, two policies can be applied to the same packet at once.
|
| /Linux-v5.4/Documentation/process/ |
| D | code-of-conduct.rst | 73 Further details of specific enforcement policies may be posted
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | spi.rst | 44 policies for how they use the bits transferred with SPI.
|
| /Linux-v5.4/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
|
| /Linux-v5.4/security/selinux/ |
| D | Kconfig | 54 policies. If unsure, say Y. With this option enabled, the
|
| /Linux-v5.4/Documentation/cpu-freq/ |
| D | core.txt | 41 Reference counting of the cpufreq policies is done by cpufreq_cpu_get
|
| /Linux-v5.4/Documentation/power/ |
| D | energy-model.rst | 53 policies. All CPUs in a performance domain are required to have the same
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 41 object corresponds to one logical CPU and ``CPUFreq`` policies are effectively
67 policies contains the string "intel_pstate".
71 can be applied to ``CPUFreq`` policies in the same way as generic scaling
74 different policies, but that is not recommended.]
197 ``sysfs`` for all ``CPUFreq`` policies contains the string "intel_cpufreq".
697 scaling governor (for the policies it is attached to), or by the ``CPUFreq``
698 core (for the policies with other scaling governors).
|
| /Linux-v5.4/Documentation/driver-api/mei/ |
| D | iamt.rst | 22 on policies set by a remote management console
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-design-CFS.rst | 119 5. Scheduling policies
122 CFS implements three scheduling policies:
|
