Line 8: |
Line 8: |
| === Daemon === | | === Daemon === |
| | | |
− | Tasks after restore should have lazy VMAs being backed by userfaultfd, the fd itself should be sent before resume to CRIU daemon and closed. This is that daemon who will monitor the UFFD events and repopulate the tasks address space. The daemon should be able to get pages from both -- remote and local images. | + | Tasks after restore should have lazy VMAs being backed by userfaultfd, the fd itself should be sent before resume to CRIU (daemon?) and closed. This is CRIU who will monitor the UFFD events and repopulate the tasks address space. It should be able to get pages from both -- remote and local images. |
| | | |
| === Local images === | | === Local images === |
| | | |
− | The daemon should just use local page-read engine and read pages from images | + | The daemon should just use local page-read engine and read pages from images. |
| | | |
| === Remote images === | | === Remote images === |
| | | |
− | * The page-read engine should be patched to learn how to talk to the [[page server]] on the other end | + | * The page-read engine should be patched to learn how to talk to the remote host ([[page server]] with --page-server option?) on the other end. |
− | * The page server should get pages from tasks dumped and send them out on the destination node. | + | * The source node should get pages from tasks dumped and send them out on the destination node. |
− | * Protocol should include out-of-order pages and background pages pushing (sending them before demand from the process) | + | * Protocol should include out-of-order pages and background pages pushing (sending them before demand from the process). |
− | * The now dump-only <code>--page-server</code> option should be used for restore
| |
| | | |
| [[Category:Memory]] | | [[Category:Memory]] |
| [[Category:Plans]] | | [[Category:Plans]] |
| [[Category:Development]] | | [[Category:Development]] |