| /Linux-v6.1/net/netlink/ |
| D | policy.c | 24 } policies[]; member
38 if (state->policies[i].policy == policy && in add_policy()
39 state->policies[i].maxtype == maxtype) in add_policy()
42 if (!state->policies[i].policy) { in add_policy()
43 state->policies[i].policy = policy; in add_policy()
44 state->policies[i].maxtype = maxtype; in add_policy()
50 state = krealloc(state, struct_size(state, policies, n_alloc), in add_policy()
55 memset(&state->policies[state->n_alloc], 0, in add_policy()
56 flex_array_size(state, policies, n_alloc - state->n_alloc)); in add_policy()
58 state->policies[state->n_alloc].policy = policy; in add_policy()
[all …]
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_guc_ads.c | 58 struct guc_policies policies; member
146 ads_blob_write(guc, policies.dpc_promote_time, in guc_policies_init()
148 ads_blob_write(guc, policies.max_num_work_items, in guc_policies_init()
154 ads_blob_write(guc, policies.global_flags, global_flags); in guc_policies_init()
155 ads_blob_write(guc, policies.is_valid, 1); in guc_policies_init()
166 ads_blob_read(guc, policies.dpc_promote_time)); in intel_guc_ads_print_policy_info()
168 ads_blob_read(guc, policies.max_num_work_items)); in intel_guc_ads_print_policy_info()
170 ads_blob_read(guc, policies.global_flags)); in intel_guc_ads_print_policy_info()
774 offsetof(struct __guc_ads_blob, policies)); in __guc_ads_init()
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/drivers/net/wireless/silabs/wfx/ |
| D | data_tx.c | 152 struct wfx_tx_policy *policies = wvif->tx_policy_cache.cache; in wfx_tx_policy_upload() local
159 is_used = memzcmp(policies[i].rates, sizeof(policies[i].rates)); in wfx_tx_policy_upload()
160 if (!policies[i].uploaded && is_used) in wfx_tx_policy_upload()
164 policies[i].uploaded = true; in wfx_tx_policy_upload()
165 memcpy(tmp_rates, policies[i].rates, sizeof(tmp_rates)); in wfx_tx_policy_upload()
|
| /Linux-v6.1/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-v6.1/Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Linux-v6.1/security/landlock/ |
| D | Kconfig | 10 tailored access control policies. A Landlock security policy is a
|
| /Linux-v6.1/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
|
| D | SafeSetID.rst | 109 Note on GID policies and setgroups()
116 policies add no meaningful security. setgroups() restrictions will be enforced
|
| /Linux-v6.1/drivers/acpi/dptf/ |
| D | Kconfig | 11 a coordinated approach for different policies to effect the hardware
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | intel_dptf.rst | 18 a coordinated approach for different policies to effect the hardware
37 A set of UUIDs strings presenting available policies
39 user space can support those policies.
|
| /Linux-v6.1/Documentation/userspace-api/media/mediactl/ |
| D | media-controller-intro.rst | 31 implementing policies that belong to userspace.
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | configfs-stp-policy | 5 This group contains policies mandating Master/Channel allocation
|
| /Linux-v6.1/fs/nfsd/ |
| D | Kconfig | 145 SELinux and Smack to label files to facilitate enforcement of their policies.
149 Smack policies on NFSv4 files, say N.
|
| /Linux-v6.1/block/ |
| D | Kconfig | 94 the IO rate to a device. IO rate policies are per cgroup and
96 cgroups and specifying per device IO rate policies.
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | spi.rst | 44 policies for how they use the bits transferred with SPI.
|
| /Linux-v6.1/Documentation/process/ |
| D | code-of-conduct.rst | 73 Further details of specific enforcement policies may be posted
|
| /Linux-v6.1/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.
297 Common files among various policies
|
| /Linux-v6.1/net/xfrm/ |
| D | Kconfig | 55 one, two policies can be applied to the same packet at once.
|
| /Linux-v6.1/Documentation/cpu-freq/ |
| D | core.rst | 33 Reference counting of the cpufreq policies is done by cpufreq_cpu_get
|
| /Linux-v6.1/Documentation/security/ |
| D | landlock.rst | 38 policies, CPU-based attacks), Landlock rules shall not be able to
|
