Lines Matching refs:to

1 The cgroup freezer is useful to batch job management system which start
2 and stop sets of tasks in order to schedule the resources of a machine
3 according to the desires of a system administrator. This sort of program
4 is often used on HPC clusters to schedule access to the cluster as a
5 whole. The cgroup freezer uses cgroups to describe the set of tasks to
7 a means to start and stop the tasks composing the job.
10 of tasks. The freezer allows the checkpoint code to obtain a consistent
11 image of the tasks by attempting to force the tasks in a cgroup into a
13 walk /proc or invoke a kernel interface to gather information about the
15 recoverable error occur. This also allows the checkpointed tasks to be
17 to another node and restarting the tasks there.
21 from within the tasks we wish to freeze. While SIGSTOP cannot be caught,
24 programs designed to watch for SIGSTOP and SIGCONT could be broken by
25 attempting to use SIGSTOP and SIGCONT to stop and resume tasks. We can
38 	<at this point 16690 exits and causes 16644 to exit too>
41 responds to them.
43 Another example of a program which catches and responds to these
44 signals is gdb. In fact any program designed to use ptrace is likely to
47 In contrast, the cgroup freezer uses the kernel freezer code to
48 prevent the freeze/unfreeze cycle from becoming visible to the tasks
49 being frozen. This allows the bash example above and gdb to run as
53 tasks belonging to the cgroup and all its descendant cgroups. Each
67   belonging to the cgroup and its descendants become frozen. Note that
68   a cgroup reverts to FREEZING from FROZEN after a new task is added
69   to the cgroup or one of its descendant cgroups until the new task is
77   If THAWED is written, the self-state of the cgroup is changed to
78   THAWED.  Note that the effective state may not change to THAWED if
86   This value is 1 iff the last write to freezer.state was "FROZEN".
103 to get status of the freezer subsystem :
108 to freeze all tasks in the container :
116 to unfreeze all tasks in the container :