From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neal Cardwell Subject: Re: [PATCH v2 net-next 1/4] tcp: hint compiler about sack flows Date: Tue, 27 Nov 2018 16:03:31 -0500 Message-ID: References: <20181127155738.73068-1-edumazet@google.com> <20181127155738.73068-2-edumazet@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: David Miller , Netdev , jean-louis@dupond.be, Yuchung Cheng , Eric Dumazet To: Eric Dumazet Return-path: Received: from mail-ot1-f68.google.com ([209.85.210.68]:46774 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726321AbeK1IC6 (ORCPT ); Wed, 28 Nov 2018 03:02:58 -0500 Received: by mail-ot1-f68.google.com with SMTP id w25so21463865otm.13 for ; Tue, 27 Nov 2018 13:03:49 -0800 (PST) In-Reply-To: <20181127155738.73068-2-edumazet@google.com> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Nov 27, 2018 at 10:57 AM Eric Dumazet wrote: > > Tell the compiler that most TCP flows are using SACK these days. > > There is no need to add the unlikely() clause in tcp_is_reno(), > the compiler is able to infer it. > > Signed-off-by: Eric Dumazet > --- Acked-by: Neal Cardwell Nice. Thanks! neal