Re: [aqm] [Bloat] TCP BBR paper is now generally available

Jonathan Morton <> Fri, 02 December 2016 20:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EE618120725 for <>; Fri, 2 Dec 2016 12:32:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id g4QpgCnaZlEb for <>; Fri, 2 Dec 2016 12:32:23 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4010:c07::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CBB731293D9 for <>; Fri, 2 Dec 2016 12:32:19 -0800 (PST)
Received: by with SMTP id o141so23186411lff.1 for <>; Fri, 02 Dec 2016 12:32:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ecjTSoS30C0S3E9bUP0JDhhCbogg+OoAb72MuONZzkQ=; b=Qr0ttsE8aOuh7ZPbJo3Byn3K1yG7MHaJ918pDd2JZHPhbL7WLaNdmVAqqoN6FTnMec 7h5xYpzgrNt91MD8SZQqA0ykUGZ5ipb6AET4OkYmFJV5neXo2Ujs95faqS6lhog9WZDp CZDqRbg7FJcg5f8LBNOipXdW0vrHObKiEsRye+Ils4KdrzjOETrK8SZc8WWaHPP/n18D yfiHYIpLSjncmRV5DbAXfQYv3SD5+jiuArHSNsJwZEX9RiSvIv+dCHTL0pykPL+0/4Id RG3/48HUYGF2FzoEZsTFxReCCLRwrMdssoJZyXTrYBSQj5sPrSqKi+IISa3AZt8OklFm K5zA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ecjTSoS30C0S3E9bUP0JDhhCbogg+OoAb72MuONZzkQ=; b=B6VG9fk7YfUhi1x8o427hPTA6usmk2pJFzDzVlRwnyyUYM9F69PtqP/DdhC3cCDzxk HVI72z1bNxjiQWdMOiFegCqTQ1ErD9VQAH4IOkHnjVBVD2HvEOETOlgpeY3QXnVpUNWV 1fhPTdx78N73PfHwA6mnVcDsU14V63YEAhEfEJvTRcMlClZDm+GvwRuVxWyUQxew17rM DtvGiWnHWnnxg7swKLf3s+mSuYxxaMzyCR5P+KozvqD2S1yyznlRM2xo8uehJZBqxWTZ nL6KPNM0R5O7wAMDXLYvrSXb1LVJxMcIfqGL+90YodLXthV96Vlt/N6NtD5grYLQjD60 gkqg==
X-Gm-Message-State: AKaTC03zSrikLrmFyihiEgTeubLHu6OzhcMosbP/rPYv2eocvwsohycgQWbGce3EtJ2lWA==
X-Received: by with SMTP id 206mr23396876ljf.17.1480710737944; Fri, 02 Dec 2016 12:32:17 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id h3sm1041775lfj.27.2016. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Dec 2016 12:32:17 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jonathan Morton <>
In-Reply-To: <>
Date: Fri, 2 Dec 2016 22:32:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Aaron Wood <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Cc: bloat <>, Dave Taht <>, "" <>
Subject: Re: [aqm] [Bloat] TCP BBR paper is now generally available
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Dec 2016 20:32:25 -0000

> On 2 Dec, 2016, at 21:15, Aaron Wood <> wrote:
> So, how is this likely to be playing with our qos_scripts and with cake?

Cake’s deficit-mode shaper behaves fairly closely like an ideal constant-throughput link, which is what BBR is supposedly designed for.  I haven’t read that far in the paper yet, but it shouldn’t trigger any “bucket detection” algorithms, because it doesn’t have a “bucket”.  It is capable of bursting, but only to the minimum extent required to reconcile required throughput with timer resolution and scheduling latency; I’ve tested it with millisecond timers.

The older schemes involving HTB and HFSC *do* have token-bucket behaviour, with an explicitly configured burst size (this excess traffic will collect in downstream buffers).  However, these are shapers, not policers, so they will start delaying packets (leaving them in child qdiscs) when the bucket is empty, not simply dropping them.

The interaction with AQM-related marking and dropping will be interesting to read, though.  It’s not a-priori obvious how much a shaper-AQM combination looks like a policer.

 - Jonathan Morton