Difference between revisions of "CR tools"
m (downgrade headers level) |
|||
| Line 4: | Line 4: | ||
it tries to achieve the same target mostly in user space. | it tries to achieve the same target mostly in user space. | ||
| − | === | + | === Agenda === |
| + | |||
| + | 1. Basic design (checkpoint == proc + SEIZE, restore == syscalls + execve) | ||
| + | 2. What's required from kernel | ||
| + | |||
| + | == Basic design == | ||
| + | |||
| + | |||
| + | === Checkpoint === | ||
| + | |||
| + | The checkpoint procedure relies heavily on '''/proc''' file system, since it's a general place where crtools takes all info it needs. | ||
Revision as of 16:20, 14 October 2011
What CRtools is
CRtools is an utility to checkpoint/restore process tree. Unlike checkpoint/restore implemented completely in kernel space, it tries to achieve the same target mostly in user space.
Agenda
1. Basic design (checkpoint == proc + SEIZE, restore == syscalls + execve) 2. What's required from kernel
Basic design
Checkpoint
The checkpoint procedure relies heavily on /proc file system, since it's a general place where crtools takes all info it needs.
