Line 24:
Line 24:
==== Remote images ====
==== Remote images ====
−
* The [[page-server]] is run on the remote side with <code>--lazy-pages</code> option.
+
* The [[page server]] is run on the remote side with <code>--lazy-pages</code> option.
* The lazy-pages daemon connects to the remote [[page server]] with <code>--page-server</code> option. The <code>--address</code> and <code>--port</code> options allow setting of IP addrees and port of the listening [[page server]].
* The lazy-pages daemon connects to the remote [[page server]] with <code>--page-server</code> option. The <code>--address</code> and <code>--port</code> options allow setting of IP addrees and port of the listening [[page server]].
* Current protocol allows the lazy-pages daemon to request several continous pages.
* Current protocol allows the lazy-pages daemon to request several continous pages.
==== Migration ====
==== Migration ====
−
* The <code>dump</code> collects the pages into pipes and starts the [[page-server]] in a mode that allows <code>lazy-pages</code> daemon to connect to it and request the memory pages
+
* The <code>dump</code> collects the pages into pipes and starts the [[page server]] in a mode that allows <code>lazy-pages</code> daemon to connect to it and request the memory pages
−
* When the restored task accesses a missing memory page, the <code>lazy-pages</code> daemon request the page from the [[page-server]] running on the dump side
+
* When the restored task accesses a missing memory page, the <code>lazy-pages</code> daemon request the page from the [[page server]] running on the dump side
* After the page is received, the <code>lazy-pages</code> daemon injects it into the task's address space using userfautlfd
* After the page is received, the <code>lazy-pages</code> daemon injects it into the task's address space using userfautlfd