What can change after C/R - Revision history

Dsafonov: what can change: add a link to vdso page

2019-07-31T19:14:24Z

what can change: add a link to vdso page

Xemul at 18:49, 15 September 2016

2016-09-15T18:49:19Z

Kir: fix parentheses

2015-04-08T21:33:31Z

fix parentheses

Xemul at 19:03, 26 November 2013

2013-11-26T19:03:29Z

Xemul at 19:01, 26 November 2013

2013-11-26T19:01:47Z

Xemul: + mount ids

2013-08-30T12:33:28Z

+ mount ids

Xemul: Created page with "This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the lis..."

2013-03-08T08:08:06Z

Created page with "This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the lis..."

New page

This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R

; Per-task statistics
: Various counters, that can be obtained via <code>/proc/$pid/status</code> or <code>getrusage()</code>

; Namespaces' IDs
: Numbers you see in the <code>/proc/$pid/ns/*</code> links' targets

; Process start time
: It's in the 22nd field of the <code>/proc/$pid/stat</code> file

@@ Line 17: / Line 17: @@
 ; VDSO
-: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade), the VDSO contents ''may'' change. However, its linkage with the application is preserved.
+: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade), the [[Vdso|VDSO contents ''may'' change]]. However, its linkage with the application is preserved.
 [[Category:Using]]

← Older revision		Revision as of 18:49, 15 September 2016
Line 18:		Line 18:
	; VDSO		; VDSO
	: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade), the VDSO contents ''may'' change. However, its linkage with the application is preserved.		: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade), the VDSO contents ''may'' change. However, its linkage with the application is preserved.
		+
		+	[[Category:Using]]

← Older revision		Revision as of 21:33, 8 April 2015
Line 17:		Line 17:

	; VDSO		; VDSO
−	: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade, the VDSO contents ''may'' change. However, its linkage with the application is preserved.	+	: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade), the VDSO contents ''may'' change. However, its linkage with the application is preserved.

← Older revision		Revision as of 19:03, 26 November 2013
Line 15:		Line 15:
	; Sockets IDs		; Sockets IDs
	: If you stat() a file descriptor with a socket the st_ino value can be used as unique socket ID. This value does changes after C/R as these IDs are global and we have no API to restore one.		: If you stat() a file descriptor with a socket the st_ino value can be used as unique socket ID. This value does changes after C/R as these IDs are global and we have no API to restore one.
		+
		+	; VDSO
		+	: The VDSO is a shared library linked into app by kernel. If the C/R cycle implies changing the kernel in between (e.g. [[live migration]] or seamless kernel upgrade, the VDSO contents ''may'' change. However, its linkage with the application is preserved.

@@ Line 1: / Line 1: @@
-This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R
+This page is very important (I believe). It describes what can change in a tasks' environment after a C/R cycle. If a software you're using depends on either item from the list below, it may break after C/R. The list is incomplete, but we do our best to make it contain relevant data.
 ; Per-task statistics
@@ Line 12: / Line 12: @@
 ; Mount points IDs
 : The numbers from first 2 columns of <code>/proc/$pid/mountinfo</code>

← Older revision		Revision as of 12:33, 30 August 2013
Line 9:		Line 9:
	; Process start time		; Process start time
	: It's in the 22nd field of the <code>/proc/$pid/stat</code> file		: It's in the 22nd field of the <code>/proc/$pid/stat</code> file
		+
		+	; Mount points IDs
		+	: The numbers from first 2 columns of <code>/proc/$pid/mountinfo</code>