Lines Matching full:limit
6 * after a certain limit is reached.
8 * Since it is trivial to hit the task limit without hitting any kmemcg limits
21 * To set a cgroup to have no limit, set pids.max to "max". This is the default
23 * stringent limit in the hierarchy is followed).
42 /* Fork failed in subtree because this pids_cgroup limit was hit. */
44 /* Fork failed in this pids_cgroup because ancestor limit was hit. */
57 atomic64_t limit; member
87 atomic64_set(&pids->limit, PIDS_MAX); in pids_css_alloc()
141 * This function does *not* follow the pid limit set. It cannot fail and the new
142 * pid count may exceed the limit. This is only used for reverting failed
143 * attaches, where there is no other way out than violating the limit.
162 * This function follows the set limit. It will fail if the charge would cause
163 * the new value to exceed the hierarchical limit. Returns 0 if the charge
172 int64_t limit = atomic64_read(&p->limit); in pids_try_charge() local
176 * p->limit is %PIDS_MAX then we know that this test will never in pids_try_charge()
179 if (new > limit) { in pids_try_charge()
184 * Not technically accurate if we go over limit somewhere up in pids_try_charge()
248 /* Only log the first time limit is hit. */ in pids_event()
306 int64_t limit; in pids_max_write() local
311 limit = PIDS_MAX; in pids_max_write()
315 err = kstrtoll(buf, 0, &limit); in pids_max_write()
319 if (limit < 0 || limit >= PIDS_MAX) in pids_max_write()
324 * Limit updates don't need to be mutex'd, since it isn't in pids_max_write()
325 * critical that any racing fork()s follow the new limit. in pids_max_write()
327 atomic64_set(&pids->limit, limit); in pids_max_write()
335 int64_t limit = atomic64_read(&pids->limit); in pids_max_show() local
337 if (limit >= PIDS_MAX) in pids_max_show()
340 seq_printf(sf, "%lld\n", limit); in pids_max_show()