mirror of
https://github.com/checkpoint-restore/criu
synced 2025-09-05 16:55:43 +00:00
If a TCP socket will get live-migrated from one box to another the timestamps (which are typically ON) will get screwed up -- the new kernel will generate TS values that has nothing to do with what they were on dump. The solution is to yet again fix the kernel and put a "timestamp offset" on a socket. v2: don't fail if TCP_TIMESTAMP is unsupported Signed-off-by: Andrey Vagin <avagin@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
13 lines
345 B
Protocol Buffer
13 lines
345 B
Protocol Buffer
message tcp_stream_entry {
|
|
required uint32 inq_len = 1;
|
|
required uint32 inq_seq = 2;
|
|
required uint32 outq_len = 3;
|
|
required uint32 outq_seq = 4;
|
|
|
|
required uint32 opt_mask = 5; /* TCPI_OPT_ bits */
|
|
required uint32 snd_wscale = 6;
|
|
required uint32 mss_clamp = 7;
|
|
optional uint32 rcv_wscale = 8;
|
|
optional uint32 timestamp = 9;
|
|
}
|