From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Yuchung Cheng <ycheng@google.com>
Cc: Kristian Evensen <kristian.evensen@gmail.com>,
David Miller <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] tcp: Add TCP_FREEZE socket option
Date: Fri, 24 Oct 2014 18:26:07 +0200 [thread overview]
Message-ID: <CAPh34mdeYib4VSDT7Fj9i-oNc4c8HmUGT9KHpU2gS4scpODdpA@mail.gmail.com> (raw)
In-Reply-To: <CAK6E8=fiHrgicTXy2hBGh0GUcZRWWxpYxw_bNVmRD+ueN9mUdw@mail.gmail.com>
On 24 October 2014 16:58, Yuchung Cheng <ycheng@google.com> wrote:
> Do packets actually get dropped during the handover period? if not
> then the sender can detect spurious RTOs and undo the cwnd reductions
> with timestamps or DSACKs (Eifel). Eifel did not exist when the
> freeze-TCP was published at 2000. Even if the connection does not
> support these options as major TCP stacks do, slow-start on a path
> with new BDP isn't that bad of an idea.
Yes, starting with fresh values for a new links is a good thing to do.
But what I think what Kristian want to address is to reduce larger
idle period due to backoff'ing timeouts followed by larger idle
periods? E.g. like a temporary cork for an exact period of time.
I thought that freeze-TCP was *also* designed to bridge a larger
disconnection? The downside with this approach (compared to SplitTCP)
is that you only send one instance into sleep. The other peer (sender)
may run into timeouts too.
Hagen
next prev parent reply other threads:[~2014-10-24 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 15:36 [PATCH net-next] tcp: Add TCP_FREEZE socket option Kristian Evensen
2014-10-22 15:54 ` Eric Dumazet
2014-10-22 16:10 ` Kristian Evensen
2014-10-22 16:14 ` David Miller
2014-10-22 17:08 ` Kristian Evensen
2014-10-22 19:50 ` Hagen Paul Pfeifer
2014-10-22 20:33 ` Kristian Evensen
2014-10-24 14:58 ` Yuchung Cheng
2014-10-24 16:26 ` Hagen Paul Pfeifer [this message]
2014-10-25 21:29 ` Kristian Evensen
2014-10-25 21:21 ` Kristian Evensen
2014-10-22 16:56 ` Cong Wang
2014-10-22 17:11 ` Kristian Evensen
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=CAPh34mdeYib4VSDT7Fj9i-oNc4c8HmUGT9KHpU2gS4scpODdpA@mail.gmail.com \
--to=hagen@jauu.net \
--cc=davem@davemloft.net \
--cc=kristian.evensen@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/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).