From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neal Cardwell Subject: Re: [PATCH net-next 2/2] tcp: do not aggressively quick ack after ECN events Date: Tue, 22 May 2018 13:36:17 -0400 Message-ID: References: <20180521220857.229273-1-edumazet@google.com> <20180521220857.229273-3-edumazet@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: David Miller , Netdev , Van Jacobson , Yuchung Cheng , Soheil Hassas Yeganeh , Eric Dumazet To: Eric Dumazet Return-path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:40652 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751268AbeEVRgf (ORCPT ); Tue, 22 May 2018 13:36:35 -0400 Received: by mail-wm0-f65.google.com with SMTP id j5-v6so1959339wme.5 for ; Tue, 22 May 2018 10:36:35 -0700 (PDT) In-Reply-To: <20180521220857.229273-3-edumazet@google.com> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, May 21, 2018 at 6:09 PM Eric Dumazet wrote: > ECN signals currently forces TCP to enter quickack mode for > up to 16 (TCP_MAX_QUICKACKS) following incoming packets. > We believe this is not needed, and only sending one immediate ack > for the current packet should be enough. > This should reduce the extra load noticed in DCTCP environments, > after congestion events. > This is part 2 of our effort to reduce pure ACK packets. > Signed-off-by: Eric Dumazet > --- Acked-by: Neal Cardwell Thanks! neal