Lines Matching refs:may

64 There's no limit on how many hierarchies there may be, which means
66 The key may contain any varying number of entries and is unlimited in
80 depending on the specific controller.  In other words, hierarchy may
112 controller states are destroyed asynchronously and controllers may
113 have lingering references, a controller may not show up immediately on
116 moved out of the unified hierarchy and it may take some time for the
119 may need to be disabled too.
204 extra layer of nesting which may not be necessary, makes the interface
225  Except for the root, only cgroups which don't contain any task may
267 this may in the future be limited explicitly.
289 C0's ancestors and may be completely different from C1.  It's clear
400 reading; however, controllers may allow omitting later fields or
405 may be specified in any order and not all pairs have to be specified.
448   and memory, and better suited given that it may be used for cgroup
461 	file follows the following format.  More fields may later be
497 	settings may be omitted or specified in any order.
603 processes in sub-hierarchies may be delegated by changing the
622 useful features which may not be suitable for general consumption in a
626 general kernel APIs for good reasons.  It may end up leaking internal
639 may make sense for unprivileged access.  If deemed justified, those