Technologies - Revision history

Xemul: /* Managing protocol buffers objects */

2016-09-21T10:26:42Z

Managing protocol buffers objects

2016-09-21T10:26:06Z

2016-09-21T10:25:39Z

Parasite code injection

2015-02-10T13:39:19Z

2015-02-10T13:38:47Z

2015-02-10T13:38:29Z

2015-02-10T13:09:36Z

Sharing of kernel objects

2015-02-10T12:49:30Z

Added KCMP

2015-02-10T09:34:04Z

pb2dict.py

2015-02-10T09:32:58Z

Fixed text

@@ Line 19: / Line 19: @@
 See more examples in our protobuf/*.proto files.
-It is also worth noting, that we have a unique number for all kinds of custom protobuf options(see [[Images#Notes_about_protobuf]]), so you don't have to worry that it might collide with others.
+It is also worth noting, that we have a unique number for all kinds of custom protobuf options, so you don't have to worry that it might collide with others.
 == Sharing of kernel objects ==

@@ Line 26: / Line 26: @@
 In kernel there's no API that can just reveal the tasks-to-objects map. Instead, there's an API called <code>kcmp()</code> that compares two e.g. file descriptors and reports back whether the file referenced by them is the same or not. In CRIU we have a [https://github.com/xemul/criu/blob/master/kcmp-ids.c KCMPIDS] engine that uses this API, build [[kcmp trees]] and turns the equals-notequals answers into a list of IDs of objects.
 [[Category:Development]]
 [[Category:Under the hood]]

@@ Line 2: / Line 2: @@
 == Parasite code injection ==
-This thing was split into a separate project called [https://github.com/xemul/compel compel].
+This thing was split into a sub-project called [[compel]].
 Compel is an utility to execute code in foreign process address space. It is based on the same technology we use in CRIU to obtain some process-private data on dump.
 We don't currently maintain compel and it's quite out-dated, but still functional.
 == Managing protocol buffers objects ==

← Older revision		Revision as of 13:39, 10 February 2015
Line 1:		Line 1:
−	This page contains a list of technologies and tools ~~has~~ been developed while we were implementing CRIU, which might be useful on their own. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.	+	This page contains a list of technologies and tools have been developed while we were implementing CRIU, which might be useful on their own. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.

	== Parasite code injection ==		== Parasite code injection ==

← Older revision		Revision as of 13:38, 10 February 2015
Line 1:		Line 1:
−	This page contains a list of technologies and tools has been developed while we were implementing CRIU, which might be useful on ~~its~~ own. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.	+	This page contains a list of technologies and tools has been developed while we were implementing CRIU, which might be useful on their own. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.

	== Parasite code injection ==		== Parasite code injection ==

@@ Line 6: / Line 6: @@
 We don't currently maintain compel and it's quite out-dated, but still functional.
-== [https://github.com/xemul/criu/blob/master/pycriu/images/pb2dict.py pb2dict.py] ==
+== Managing protocol buffers objects ==
-A Python module to convert google protocol buffers to json and back.
+We have [https://github.com/xemul/criu/blob/master/pycriu/images/pb2dict.py a Python module] to convert google protocol buffers to python objects and back.
 Unlike other projects to convert pb to python dict or json, our pb2dict does treat optional fields with empty repeated inside properly. It includes special support for custom field options to mark those needed to be treated in a special way.

@@ Line 1: / Line 1: @@
-This page contains a list of tools that were developed for criu and which others might want to use in their projects.
+This page contains a list of technologies and tools that were developed while we did CRIU and that make sense outside of it. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.
-== [https://github.com/xemul/compel Compel] ==
+== Parasite code injection ==
-An utility to execute code in foreign process address space. It is based on the same technology we use in CRIU to obtain some process-private data on dump.
+This thing was split into a separate project called [https://github.com/xemul/compel compel].
 == [https://github.com/xemul/criu/blob/master/pycriu/images/pb2dict.py pb2dict.py] ==