Page server - Revision history

Radostin: /* Limitations */ Support for DNS name resolution was added with commit a7c384f6eebcebc8b49655601956c18c51735672

2019-01-13T12:54:37Z

Limitations: Support for DNS name resolution was added with commit a7c384f6eebcebc8b49655601956c18c51735672

2018-10-24T09:49:12Z

Running page server: Document --ps-socket

2016-08-31T04:32:18Z

2016-08-31T04:31:43Z

Pages deduplication: link to Memory images deduplication

2016-08-30T20:52:36Z

add note about pagemap/pages .img

2016-08-30T20:04:40Z

Running page server: moved one-shot/exit-code piece up

2016-08-30T19:01:29Z

Running page server: add one-shot + exit code

2016-08-30T18:47:18Z

Usage: rewording

2016-08-30T18:13:20Z

added "Limitations", mention -o and -v options for 'criu page-server'

2016-08-30T12:38:33Z

← Older revision		Revision as of 12:54, 13 January 2019
Line 86:		Line 86:

	* Currently it only works via TCP		* Currently it only works via TCP
−	* DNS names are not resolved for <code>--address</code> argument, only IP addresses are allowed
	* No encryption, no compression, data is passed over network as is		* No encryption, no compression, data is passed over network as is

← Older revision		Revision as of 09:49, 24 October 2018
Line 55:		Line 55:

	Some other options might also be useful, such as:		Some other options might also be useful, such as:
		+
		+	; --ps-socket $FD
		+	: Use provided file descriptor as socket for incoming connection. In this case <code>--address</code> and <code>--port</code> are ignored. Useful for intercepting page-server traffic e.g. to add encryption or authentication.

	; -o\|--logfile $FILE		; -o\|--logfile $FILE

@@ Line 93: / Line 93: @@
 * [[Iterative migration]]
 * [[Incremental dumps]]
 * [[Lazy migration]]

← Older revision		Revision as of 04:31, 31 August 2016
Line 25:		Line 25:

	=== Pages deduplication ===		=== Pages deduplication ===
		+
		+	''Main article: [[Memory images deduplication]].''

	When iterative memory dumping feature (<code>criu pre-dump</code>) is used, memory is sent to page server a few times. The page server can automatically deduplicate pages, by punching holes in parent images where the child image is replacing an existing page. This functionality is turned on by <code>--auto-dedup</code> option of <code>criu page-server</code> command.		When iterative memory dumping feature (<code>criu pre-dump</code>) is used, memory is sent to page server a few times. The page server can automatically deduplicate pages, by punching holes in parent images where the child image is replacing an existing page. This functionality is turned on by <code>--auto-dedup</code> option of <code>criu page-server</code> command.

@@ Line 21: / Line 21: @@
 [[Image:Memory_migration_with_page_server.png|thumb|500px|right|Memory migration with page server]]
 When using page server, the memory is dumped not to disk, but directly to network, thus eliminating any disk reads/writes on the source. On the destination system, a page server runs, receiving the data from network and writing it to files on disk or tmpfs.
 === Pages deduplication ===

@@ Line 36: / Line 36: @@
   [dst]# criu page-server --images-dir $DIR --port $PORT [--auto-dedup] [...]
 The options are:
@@ Line 55: / Line 57: @@
 ; -v$N|-vvv[..]
 : Set logging level (verbosity). For example, <code>-v4</code> (or <code>-vvvv</code>, which means the same) enables tons of debug info.
 === criu pre-dump/dump ===

@@ Line 48: / Line 48: @@
 : Perform auto deduplication of images. Useful with iterative memory dumps.
-Some other general options might also be useful, such as:
+Some other options might also be useful, such as:
 ; -o|--logfile $FILE
@@ Line 55: / Line 55: @@
 ; -v$N|-vvv[..]
 : Set logging level (verbosity). For example, <code>-v4</code> (or <code>-vvvv</code>, which means the same) enables tons of debug info.
 === criu pre-dump/dump ===

@@ Line 29: / Line 29: @@
 == Usage ==
-You would want to use page server feature when performing a [[live migration]]. In most cases, just use [[P.Haul]] which handles the details for you. Otherwise, read on.
+The obvious use case for page server is [[live migration]]. In most cases, use [[P.Haul]] to hide the details from you. Otherwise, read on.
 === Running page server ===
@@ Line 58: / Line 58: @@
 === criu pre-dump/dump ===
-In addition to usual set of options (see [[live migration]], [[iterative migration]] etc.), when a page-server is used, you need to specify a few additional arguments to <code>criu pre-dump</code> or <code>criu dump</code> commands:
+On the source system, run <code>criu pre-dump</code> or <code>criu dump</code> as usual (see [[live migration]], [[iterative migration]] etc.).
 ; --page-server

@@ Line 35: / Line 35: @@
 First, run a page server on a destination node:
-  [dst]# criu page-server --images-dir $DIR --port $PORT [--auto-dedup]
+  [dst]# criu page-server --images-dir $DIR --port $PORT [--auto-dedup] [...]
 The options are:
@@ Line 47: / Line 47: @@
 ; --auto-dedup
 : Perform auto deduplication of images. Useful with iterative memory dumps.
 === criu pre-dump/dump ===
@@ Line 64: / Line 72: @@
 To view an example video of using a page server, please go to https://asciinema.org/a/15847.
 == See also ==

@@ Line 69: / Line 69: @@
 * [[P.Haul]]
 * [[Live migration]]
 * [[Iterative migration]]
 * [[Incremental dumps]]