criu/protobuf/fdinfo.proto

enum fd_types {
	UND		= 0;
	REG		= 1;
	PIPE		= 2;
	FIFO		= 3;
	INETSK		= 4;
	UNIXSK		= 5;
	EVENTFD		= 6;
	EVENTPOLL	= 7;
	INOTIFY		= 8;
}

message fdinfo_entry {
	required uint32	id	= 1;
	required uint32	flags	= 2;
	required fd_types type	= 3;
	required uint32	fd	= 4;
}
fdinfo: Make fdinfo.type be an enum This types specifies a strict set of what is hidden behind the fd. Thus these numbers should be in the description of the fdinfo message. Plus protobuf makes shure nothing else will be there. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-19 10:18:37 +04:00			`enum fd_types {`
			`UND = 0;`
			`REG = 1;`
			`PIPE = 2;`
			`FIFO = 3;`
			`INETSK = 4;`
			`UNIXSK = 5;`
			`EVENTFD = 6;`
			`EVENTPOLL = 7;`
			`INOTIFY = 8;`
			`}`

protobuf: Start switching our image entries to Google's protobuf A short story -- there were a long conversation on which format should be used to keep checkpointed data on disk image. We ended up in using Google's Protocol Buffers (see https://developers.google.com/protocol-buffers/ for detailed description). Thus image entries should be convered to PB. This patch converts fdinfo_entry to PB "message fdinfo_entry". Build note: one should have protobuf and protobuf-c installed to be able to build crtools. - http://code.google.com/p/protobuf/ - http://code.google.com/p/protobuf-c/ Inspired-by: Pavel Emelianov <xemul@parallels.com> Inspired-by: Kinsbursky Stanislav <skinsbursky@openvz.org> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-12 13:06:00 +04:00			`message fdinfo_entry {`
			`required uint32 id = 1;`
			`required uint32 flags = 2;`
fdinfo: Make fdinfo.type be an enum This types specifies a strict set of what is hidden behind the fd. Thus these numbers should be in the description of the fdinfo message. Plus protobuf makes shure nothing else will be there. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-19 10:18:37 +04:00			`required fd_types type = 3;`
protobuf: Start switching our image entries to Google's protobuf A short story -- there were a long conversation on which format should be used to keep checkpointed data on disk image. We ended up in using Google's Protocol Buffers (see https://developers.google.com/protocol-buffers/ for detailed description). Thus image entries should be convered to PB. This patch converts fdinfo_entry to PB "message fdinfo_entry". Build note: one should have protobuf and protobuf-c installed to be able to build crtools. - http://code.google.com/p/protobuf/ - http://code.google.com/p/protobuf-c/ Inspired-by: Pavel Emelianov <xemul@parallels.com> Inspired-by: Kinsbursky Stanislav <skinsbursky@openvz.org> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2012-07-12 13:06:00 +04:00			`required uint32 fd = 4;`
			`}`