From: Andrey Vagin <avagin@openvz.org>
To: netdev@vger.kernel.org
Cc: criu@openvz.org, linux-kernel@vger.kernel.org,
Andrey Vagin <avagin@openvz.org>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
Eric Dumazet <edumazet@google.com>,
Pavel Emelyanov <xemul@parallels.com>
Subject: [PATCH net-next] tcp: add ability to set a timestamp offset
Date: Mon, 11 Feb 2013 19:50:16 +0400 [thread overview]
Message-ID: <1360597819-23783-1-git-send-email-avagin@openvz.org> (raw)
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.
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: James Morris <jmorris@namei.org>
Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Cc: Patrick McHardy <kaber@trash.net>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Pavel Emelyanov <xemul@parallels.com>
Signed-off-by: Andrey Vagin <avagin@openvz.org>
Andrey Vagin (3):
tcp: adding a per-socket timestamp offset
tcp: set and get per-socket timestamp
tcp: send packets with a socket timestamp
include/linux/tcp.h | 3 +++
include/uapi/linux/tcp.h | 1 +
net/ipv4/tcp.c | 11 +++++++++++
net/ipv4/tcp_input.c | 8 +++++++-
net/ipv4/tcp_ipv4.c | 12 +++++++-----
net/ipv4/tcp_minisocks.c | 3 +++
net/ipv4/tcp_output.c | 4 ++--
net/ipv6/tcp_ipv6.c | 22 +++++++++++++---------
8 files changed, 47 insertions(+), 17 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-02-11 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 15:50 Andrey Vagin [this message]
2013-02-11 15:50 ` [PATCH 1/3] tcp: adding a per-socket timestamp offset 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 ` [PATCH net-next] tcp: add ability to set a timestamp offset David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 20:52 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=1360597819-23783-1-git-send-email-avagin@openvz.org \
--to=avagin@openvz.org \
--cc=criu@openvz.org \
--cc=davem@davemloft.net \
--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).