From: David Miller <davem@davemloft.net>
To: avagin@openvz.org
Cc: netdev@vger.kernel.org, criu@openvz.org,
linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
edumazet@google.com, xemul@parallels.com
Subject: Re: [PATCH net-next] tcp: add ability to set a timestamp offset
Date: Wed, 13 Feb 2013 13:22:54 -0500 (EST) [thread overview]
Message-ID: <20130213.132254.1534641136664469265.davem@davemloft.net> (raw)
In-Reply-To: <1360597819-23783-1-git-send-email-avagin@openvz.org>
From: Andrey Vagin <avagin@openvz.org>
Date: Mon, 11 Feb 2013 19:50:16 +0400
> 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.
>
> A socket offset is added in places where externally visible tcp
> timestamp option is parsed/initialized.
>
> Connections in the SYN_RECV state are not supported, global
> tcp_time_stamp is used for them, because repair mode doesn't support
> this state. In a future it can be implemented by the similar way as for
> TIME_WAIT sockets.
>
> For time-wait sockets offset is inhereted by a proper tcp_sock.
>
> A per-socket offset can be set only for sockets in repair mode.
Series applied, thanks.
next prev parent reply other threads:[~2013-02-13 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 15:50 [PATCH net-next] tcp: add ability to set a timestamp offset Andrey Vagin
2013-02-11 15:50 ` [PATCH 1/3] tcp: adding a per-socket " Andrey Vagin
2013-02-11 15:50 ` [PATCH 2/3] tcp: set and get per-socket timestamp Andrey Vagin
2013-02-11 15:50 ` [PATCH 3/3] tcp: send packets with a socket timestamp Andrey Vagin
2013-02-13 18:22 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 20:52 [PATCH net-next] tcp: add ability to set a timestamp offset Andrey Vagin
2013-01-22 21:16 ` Rick Jones
2013-01-22 21:18 ` Neal Cardwell
2013-01-22 21:24 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130213.132254.1534641136664469265.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=avagin@openvz.org \
--cc=criu@openvz.org \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@parallels.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).