| /linux-4.4.14/Documentation/vm/ |
| D | numa_memory_policy.txt | 11 Memory policies should not be confused with cpusets
14 memory may be allocated by a set of processes. Memory policies are a
16 both cpusets and policies are applied to a task, the restrictions of the cpuset
50 In a multi-threaded task, task policies apply only to the thread
72 VMA policies have a few complicating details:
83 VMA policies are shared between all tasks that share a virtual address
85 they are inherited across fork(). However, because VMA policies refer
87 space is discarded and recreated on exec*(), VMA policies are NOT
89 use VMA policies.
102 Shared Policy: Conceptually, shared policies apply to "memory objects"
[all …]
|
| D | zswap.txt | 84 Zswap seeks to be simple in its policies. Sysfs attributes allow for one user
|
| D | frontswap.txt | 21 conform to certain policies as follows:
148 backend, such as zcache, must implement policies to carefully (but
|
| /linux-4.4.14/Documentation/serial/ |
| D | 00-INDEX | 16 - guide to the locking policies of the tty layer.
|
| D | tty.txt | 4 Your guide to the ancient and twisted locking policies of the tty layer and
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-fs-f2fs | 45 policies.
52 policies.
|
| D | configfs-stp-policy | 5 This group contains policies mandating Master/Channel allocation
|
| /linux-4.4.14/Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /linux-4.4.14/Documentation/security/ |
| D | SELinux.txt | 2 to use the distro-provided policies, or install the
|
| D | credentials.txt | 228 rules (policies) that say what operations a task with one label may do to
|
| /linux-4.4.14/block/ |
| D | Kconfig | 97 the IO rate to a device. IO rate policies are per cgroup and
99 cgroups and specifying per device IO rate policies.
|
| /linux-4.4.14/fs/nfsd/ |
| D | Kconfig | 103 SELinux and Smack to label files to facilitate enforcement of their policies.
107 Smack policies on NFSv4 files, say N.
|
| /linux-4.4.14/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 | 158 messages are used. Refer to cache-policies.txt.
194 See cache-policies.txt for details.
|
| /linux-4.4.14/net/xfrm/ |
| D | Kconfig | 28 one, two policies can be applied to the same packet at once.
|
| /linux-4.4.14/drivers/staging/lustre/lustre/ptlrpc/ |
| D | sec.c | 62 static struct ptlrpc_sec_policy *policies[SPTLRPC_POLICY_MAX] = { variable
78 if (unlikely(policies[number])) { in sptlrpc_register_policy()
82 policies[number] = policy; in sptlrpc_register_policy()
97 if (unlikely(policies[number] == NULL)) { in sptlrpc_unregister_policy()
103 LASSERT(policies[number] == policy); in sptlrpc_unregister_policy()
104 policies[number] = NULL; in sptlrpc_unregister_policy()
126 policy = policies[number]; in sptlrpc_wireflavor2policy()
|
| /linux-4.4.14/arch/metag/mm/ |
| D | Kconfig | 48 memory policies to be used for prioritizing and controlling
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | pids.txt | 22 Organisational operations are not blocked by cgroup policies, so it is possible
|
| 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
343 Common files among various policies
|
| D | unified-hierarchy.txt | 460 independent of which policies are enabled. Each line in the
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 115 5. Scheduling policies
117 CFS implements three scheduling policies:
|
| D | sched-stats.txt | 152 under the scheduler's policies. A simple version of such a program is
|
| D | sched-deadline.txt | 484 SCHED_{OTHER,FIFO,RR,DEADLINE} scheduling policies and their related
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | f2fs.txt | 93 - Support greedy and cost-benefit algorithms for victim selection policies
216 updates in f2fs. There are five policies:
224 F2FS_IPU_UTIL and F2FS_IPU_SSR_UTIL policies.
569 F2FS supports two victim selection policies: greedy and cost-benefit algorithms.
|
| D | tmpfs.txt | 105 NUMA memory allocation policies have optional flags that can be used in
|
| /linux-4.4.14/security/selinux/ |
| D | Kconfig | 62 policies. If unsure, say Y. With this option enabled, the
|
| /linux-4.4.14/Documentation/usb/ |
| D | hotplug.txt | 25 Those triggered actions must support a system's administrative policies;
|
| /linux-4.4.14/arch/sh/mm/ |
| D | Kconfig | 120 memory policies to be used for prioritizing and controlling
|
| /linux-4.4.14/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
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Overview.txt | 139 Read the kernel patch submission policies as well as the
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 37 on policies set by a remote management console
|
| /linux-4.4.14/Documentation/networking/ |
| D | dccp.txt | 52 during an established connection are not supported). Currently, two policies are
|
| D | bonding.txt | 238 The bandwidth and count selection policies permit failover of
547 Specifies one of the bonding policies. The default is
584 policies may be selected via the xmit_hash_policy option,
605 policies may be 802.3ad compliant, particularly in
1586 system administrator. The output port is simply selected using the policies of
1589 slightly more complex policies. For example, to reach a web server over a
|
| D | packet_mmap.txt | 586 Currently implemented fanout policies are:
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 122 extension. This allows you to attach timeout policies to flow
348 policies to flows, instead of using the global timeout policy.
1142 It enables you to express policies like `10kpps for any given
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 11 wfi to power gating) according to OS PM policies. The CPU states representing
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 20 Documentation/CodingStyle. For much of that time, the policies described
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 134 that userspace can exploit to implement policies like "only interface
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 812 node unless explicitly overridden by memory policies or cpuset
|
| /linux-4.4.14/init/ |
| D | Kconfig | 967 system to halt without being limited by other cgroup policies. The
1126 policies.
|