| /linux-6.14.4/tools/testing/selftests/net/ |
| D | xfrm_policy_add_speed.sh | 23 local policies
26 policies=0
38 policies=$((policies+1))
39 [ "$policies" -gt "$max" ] && return
43 policies=$((policies+1))
44 [ "$policies" -gt "$max" ] && return
67 policies=$(wc -l < "$tmp")
68 printf "Inserted %-06s policies in $result ms\n" $policies
71 if [ "$have" -ne "$policies" ]; then
72 echo "WARNING: mismatch, have $have policies, expected $policies"
|
| D | xfrm_policy.sh | 58 # add policies with different netmasks, to make sure kernel carries
59 # the policies contained within new netmask over when search tree is
67 # policies it carries need to be merged with the existing one(s).
97 # the sub-tree. As no duplicates are allowed, policies in
109 # similar to above: add policies (with partially random address), with shrinking prefixes.
151 # policies that are not supposed to match any packets generated in this test.
289 # insert non-overlapping policies in a random order and check that
446 # insert block policies with adjacent/overlapping netmasks
449 check_exceptions "exceptions and block policies"
459 check_exceptions "exceptions and block policies after hresh changes"
[all …]
|
| /linux-6.14.4/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 15 Memory policies should not be confused with cpusets
18 memory may be allocated by a set of processes. Memory policies are a
20 both cpusets and policies are applied to a task, the restrictions of the cpuset
21 takes priority. See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
27 Scope of Memory Policies
61 In a multi-threaded task, task policies apply only to the thread
88 VMA policies have a few complicating details:
100 * VMA policies are shared between all tasks that share a
103 fork(). However, because VMA policies refer to a specific
105 space is discarded and recreated on exec*(), VMA policies
[all …]
|
| /linux-6.14.4/net/netlink/ |
| D | policy.c | 24 } policies[] __counted_by(n_alloc); 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()
57 memset(&state->policies[old_n_alloc], 0, in add_policy()
58 flex_array_size(state, policies, n_alloc - old_n_alloc)); in add_policy()
60 state->policies[old_n_alloc].policy = policy; in add_policy()
[all …]
|
| /linux-6.14.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
259 DIRECT_KEY policies
[all …]
|
| /linux-6.14.4/Documentation/admin-guide/ |
| D | nvme-multipath.rst | 7 This document describes NVMe multipath and its path selection policies supported
19 Different policies result in different path selections.
22 Policies chapter
25 All policies follow the ANA (Asymmetric Namespace Access) mechanism, meaning
27 one. Current the NVMe multipath policies include numa(default), round-robin and
|
| /linux-6.14.4/security/ipe/ |
| D | Kconfig | 29 is deployed via the $securityfs/ipe/policies/$policy_name/active
60 policies. The property evaluates to TRUE when a file from a dm-verity
69 policies. The property evaluates to TRUE when a file from a dm-verity
80 policies. The property evaluates to TRUE when a file is fsverity
91 policies. The property evaluates to TRUE when a file is fsverity
|
| D | policy_fs.c | 28 * read_pkcs7() - Read handler for "ipe/policies/$name/pkcs7".
72 * read_policy() - Read handler for "ipe/policies/$name/policy".
110 * read_name() - Read handler for "ipe/policies/$name/name".
148 * read_version() - Read handler for "ipe/policies/$name/version".
191 * setactive() - Write handler for "ipe/policies/$name/active".
238 * getactive() - Read handler for "ipe/policies/$name/active".
276 * update_policy() - Write handler for "ipe/policies/$name/update".
315 * delete_policy() - write handler for "ipe/policies/$name/delete".
|
| /linux-6.14.4/drivers/gpu/drm/xe/ |
| D | xe_guc_ads.c | 113 struct guc_policies policies; member
461 ads_blob_write(ads, policies.dpc_promote_time, in guc_policies_init()
463 ads_blob_write(ads, policies.max_num_work_items, in guc_policies_init()
469 ads_blob_write(ads, policies.global_flags, global_flags); in guc_policies_init()
470 ads_blob_write(ads, policies.is_valid, 1); in guc_policies_init()
893 offsetof(struct __guc_ads_blob, policies)); in xe_guc_ads_populate_minimal()
927 offsetof(struct __guc_ads_blob, policies)); in xe_guc_ads_populate()
1004 struct guc_policies *policies; in xe_guc_ads_scheduler_policy_toggle_reset() local
1008 policies = kmalloc(sizeof(*policies), GFP_KERNEL); in xe_guc_ads_scheduler_policy_toggle_reset()
1009 if (!policies) in xe_guc_ads_scheduler_policy_toggle_reset()
[all …]
|
| D | xe_gt_sriov_pf_policy_types.h | 12 * struct xe_gt_sriov_guc_policies - GuC SR-IOV policies.
25 * @guc: GuC scheduling policies.
|
| /linux-6.14.4/kernel/ |
| D | Kconfig.preempt | 159 allows scheduling policies to be implemented as BPF programs to
163 iteration of new scheduling policies.
165 implement policies that are not applicable to general-purpose
168 scheduling policies in production environments.
172 wish to implement scheduling policies. The struct_ops structure
|
| /linux-6.14.4/Documentation/admin-guide/LSM/ |
| D | ipe.rst | 28 unchangeable over time. For example, IPE policies can be crafted to trust
35 integrity and trust. For example, IPE allows the definition of policies
39 checks, allowing IPE to enforce policies that trust files protected by
152 uniquely identify policies to deploy new policies vs update existing
153 policies.
192 preserve older policies being compatible with newer kernels that can introduce
197 enforcing the configurable policies at startup, around reading and
218 Deploying Policies
221 Policies can be deployed from userspace through securityfs. These policies
223 authorization of the policies (prohibiting an attacker from gaining
[all …]
|
| 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
|
| /linux-6.14.4/Documentation/security/ |
| D | ipe.rst | 134 1. Policies were not readable by humans, usually requiring a binary
153 The first issue is one of code maintenance and duplication. To author policies,
164 and the original file itself to try to understand what policies have been deployed
165 on this system and what policies have not. For a single user, this may be alright,
166 as old policies can be discarded almost immediately after the update takes hold.
169 this quickly becomes an issue, as stale policies from years ago may be present,
243 policies to be updated without updating the kernel).
270 minimum required version across all policies that can be active on
277 need to be aware of this, and ensure the new secure policies are
288 that were critical to its function. In this system, three types of policies
[all …]
|
| /linux-6.14.4/tools/testing/selftests/amd-pstate/ |
| D | run.sh | 77 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
78 for policy in $policies; do
90 policies=$(awk '{print $1}' $OUTFILE.backup_governor.log)
91 for policy in $policies; do
105 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
106 for policy in $policies; do
|
| /linux-6.14.4/include/uapi/linux/ |
| D | mempolicy.h | 3 * NUMA memory policies for Linux.
18 /* Policies */
64 #define MPOL_F_SHARED (1 << 0) /* identify shared policies */
|
| /linux-6.14.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-6.14.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-6.14.4/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
|
| /linux-6.14.4/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_guc_ads.c | 64 struct guc_policies policies; member
167 ads_blob_write(guc, policies.dpc_promote_time, in guc_policies_init()
169 ads_blob_write(guc, policies.max_num_work_items, in guc_policies_init()
175 ads_blob_write(guc, policies.global_flags, global_flags); in guc_policies_init()
176 ads_blob_write(guc, policies.is_valid, 1); in guc_policies_init()
185 drm_printf(dp, "Global scheduling policies:\n"); in intel_guc_ads_print_policy_info()
187 ads_blob_read(guc, policies.dpc_promote_time)); in intel_guc_ads_print_policy_info()
189 ads_blob_read(guc, policies.max_num_work_items)); in intel_guc_ads_print_policy_info()
191 ads_blob_read(guc, policies.global_flags)); in intel_guc_ads_print_policy_info()
893 /* GuC scheduling policies */ in __guc_ads_init()
[all …]
|
| /linux-6.14.4/fs/crypto/ |
| D | policy.c | 21 * fscrypt_policies_equal() - check whether two encryption policies are the same
65 * (and later) encryption policies.
67 * Do *not* add anything new here, since v1 encryption policies are deprecated.
208 "v1 policies can't be used on casefolded directories"); in fscrypt_supported_v1_policy()
587 /* Extended ioctl version; can get policies of any version */
677 * encryption policy. Compare the cached policies if the keys are in fscrypt_has_permitted_context()
798 * times), then this function will verify that the policies are the same.
853 * fscrypt_dummy_policies_equal() - check whether two dummy policies are equal
857 * Return: %true if the dummy policies are both set and equal, or both unset.
|
| /linux-6.14.4/tools/power/cpupower/man/ |
| D | cpupower-set.1 | 11 registers affecting processor power saving policies.
65 Available policies can be found with
|
| /linux-6.14.4/include/linux/ |
| D | mempolicy.h | 3 * NUMA memory policies for Linux.
73 * Currently only needed for shared policies.
109 * Tree of shared policies for a shared memory region.
|
| /linux-6.14.4/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-6.14.4/Documentation/bpf/ |
| D | map_sockmap.rst | 89 This helper is used in programs implementing policies at the socket level. If
169 This helper is used in programs implementing policies at the socket level. If
185 This helper is used in programs implementing policies at the skb socket level.
201 For socket policies, apply the verdict of the BPF program to the next (number
221 For socket policies, prevent the execution of the verdict BPF program for
236 For socket policies, pull in non-linear data from user space for ``msg`` and set
|