[lkml]   [2019]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH net-next v2] tcp: Ensure DCTCP reacts to losses

On 4/4/19, 10:53 AM, "David Miller" <> wrote:

From: "Tilmans, Olivier (Nokia - BE/Antwerp)" <>
Date: Thu, 4 Apr 2019 12:24:02 +0000

> RFC8257 §3.5 explicitly states that "A DCTCP sender MUST react to
> loss episodes in the same way as conventional TCP".
> This patch replace the clamping of alpha by setting ssthresh to
> half of cwnd for both fast retransmissions and RTOs, at most once
> per RTT. Consequently, the dctcp_clamp_alpha_on_loss module parameter
> has been removed.

Applied to 'net' and queued up for -stable, thanks.

DCTCP is meant to be used in environments where the switches/routers do ECN marking, so it is not surprising that it performs badly when used in environments where it was not meant to be used. Has anyone measured the effect of this changed when DCTCP is used in environments where all the switches/routers do ECN marking? My concern is that we could end up hurting performance when DCTCP is used how it was meant to be used in order to protect incorrect uses of DCTCP.

 \ /
  Last update: 2019-04-04 20:12    [W:0.104 / U:3.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site