| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | intel_guc_ads.c | 45 static void guc_policies_init(struct guc_policies *policies) in guc_policies_init() argument
50 policies->dpc_promote_time = POLICY_DEFAULT_DPC_PROMOTE_TIME_US; in guc_policies_init()
51 policies->max_num_work_items = POLICY_MAX_NUM_WI; in guc_policies_init()
55 policy = &policies->policy[p][i]; in guc_policies_init()
61 policies->is_valid = 1; in guc_policies_init()
83 struct guc_policies policies; in intel_guc_ads_create() member
105 guc_policies_init(&blob->policies); in intel_guc_ads_create()
140 blob->ads.scheduler_policies = base + ptr_offset(blob, policies); in intel_guc_ads_create()
|
| /Linux-v4.19/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-v4.19/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-v4.19/tools/perf/trace/beauty/ |
| D | sched_policy.c | 20 const char *policies[] = { in syscall_arg__scnprintf_sched_policy() local
29 printed = scnprintf(bf, size, "%s", policies[policy]); in syscall_arg__scnprintf_sched_policy()
|
| /Linux-v4.19/Documentation/serial/ |
| D | 00-INDEX | 16 - guide to the locking policies of the tty layer.
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | cache-policies.txt | 1 Guidance for writing policies
6 makes it easier to write the policies.
25 Overview of supplied cache replacement policies
|
| D | cache.txt | 153 messages are used. Refer to cache-policies.txt.
189 See cache-policies.txt for details.
|
| /Linux-v4.19/Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Linux-v4.19/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
|
| /Linux-v4.19/Documentation/media/uapi/mediactl/ |
| D | media-controller-intro.rst | 31 implementing policies that belong to userspace.
|
| /Linux-v4.19/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-v4.19/fs/nfsd/ |
| D | Kconfig | 141 SELinux and Smack to label files to facilitate enforcement of their policies.
145 Smack policies on NFSv4 files, say N.
|
| /Linux-v4.19/net/xfrm/ |
| D | Kconfig | 41 one, two policies can be applied to the same packet at once.
|
| /Linux-v4.19/block/ |
| D | Kconfig | 113 the IO rate to a device. IO rate policies are per cgroup and
115 cgroups and specifying per device IO rate policies.
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | spi.rst | 44 policies for how they use the bits transferred with SPI.
|
| /Linux-v4.19/Documentation/process/ |
| D | code-of-conduct.rst | 73 Further details of specific enforcement policies may be posted
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | blkio-controller.txt | 6 a need of various kinds of IO control policies (like proportional BW, max BW)
9 and based on user options switch IO policies in the background.
11 Currently two IO control policies are implemented. First one is proportional
342 Common files among various policies
|
| D | pids.txt | 22 Organisational operations are not blocked by cgroup policies, so it is possible
|
| /Linux-v4.19/security/selinux/ |
| D | Kconfig | 68 policies. If unsure, say Y. With this option enabled, the
|
| /Linux-v4.19/Documentation/cpu-freq/ |
| D | core.txt | 41 Reference counting of the cpufreq policies is done by cpufreq_cpu_get
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 39 object corresponds to one logical CPU and ``CPUFreq`` policies are effectively
65 policies contains the string "intel_pstate".
69 can be applied to ``CPUFreq`` policies in the same way as generic scaling
72 different policies, but that is not recommended.]
195 ``sysfs`` for all ``CPUFreq`` policies contains the string "intel_cpufreq".
680 scaling governor (for the policies it is attached to), or by the ``CPUFreq``
681 core (for the policies with other scaling governors).
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 115 5. Scheduling policies
117 CFS implements three scheduling policies:
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | f2fs.txt | 93 - Support greedy and cost-benefit algorithms for victim selection policies
287 updates in f2fs. There are five policies:
295 F2FS_IPU_UTIL and F2FS_IPU_SSR_UTIL policies.
640 F2FS supports two victim selection policies: greedy and cost-benefit algorithms.
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | hotplug.rst | 30 Those triggered actions must support a system's administrative policies;
|
