Lines Matching full:protection

79 	bool protection = track_protection(counter);
85 		if (protection)
123 	bool protection = track_protection(counter);
153 		if (protection)
294  * protection which is derived from its own memory.min/low, its
298  * The following rules apply to the effective protection values:
300  * 1. At the first level of reclaim, effective protection is equal to
301  *    the declared protection in memory.min and memory.low.
303  * 2. To enable safe delegation of the protection configuration, at
304  *    subsequent levels the effective protection is capped to the
305  *    parent's effective protection.
308  *    user is allowed to overcommit the declared protection at a given
309  *    level. If that is the case, the parent's effective protection is
310  *    distributed to the children in proportion to how much protection
314  *    if one counter claims much more protection than it uses memory,
317  * 4. Conversely, when the declared protection is undercommitted at a
318  *    given level, the distribution of the larger parental protection
319  *    budget is NOT proportional. A counter's protection from a sibling
324  *    of the ancestor's claim to protection, any unutilized -
325  *    "floating" - protection from up the tree is distributed in
326  *    proportion to each counter's *usage*. This makes the protection
328  *    the shared parental protection budget, but it protects the
348 	 * protection than what the parent affords them, distribute
352 	 * claimed protection in order to be work-conserving: claimed
353 	 * but unused protection is available to siblings that would
360 	 * Ok, utilized protection of all children is within what the
367 	 * If there is unutilized protection, the cgroup will be fully
369 	 * protection than what the group could enjoy in theory. This
371 	 * protection is always dependent on how memory is actually
377 	 * If the children aren't claiming (all of) the protection
385 	 * some cgroups DO claim explicit protection, we don't protect