lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 25 Oct 2014 23:29:42 +0200 From: Kristian Evensen <kristian.evensen@...il.com> To: Hagen Paul Pfeifer <hagen@...u.net> Cc: Yuchung Cheng <ycheng@...gle.com>, David Miller <davem@...emloft.net>, Network Development <netdev@...r.kernel.org> Subject: Re: [PATCH net-next] tcp: Add TCP_FREEZE socket option Hi, On Fri, Oct 24, 2014 at 6:26 PM, Hagen Paul Pfeifer <hagen@...u.net> wrote: > 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. Yes, that is exactly what I want to achieve. To temporarily stop traffic while the handover occurs, to prevent the penalty of the potentially large idle period caused by the sender backing off. With regards to which values to use when the handover is done, I agree that it would make sense to start with for example a lower cwnd. The network characteristics (for example throughput and latency) will most likely have changed. However, at least the way I have thought about this, such a change would also need changes on the remote machine. > 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. Yes, that is true. But I guess with the alternate design (netlink module), the probability of this will be reduced. As long as the application sets the frozen socket option and assuming zero window will arrive, sender should stop as well. -Kristian -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists