Re: [tcpPrague] [Bloat] DualPI2 qdisc implementation available for Linux
Stephen Hemminger <stephen@networkplumber.org> Tue, 25 October 2016 05:12 UTC
Return-Path: <stephen@networkplumber.org>
X-Original-To: tcpprague@ietfa.amsl.com
Delivered-To: tcpprague@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 5DB1A129610
for <tcpprague@ietfa.amsl.com>; Mon, 24 Oct 2016 22:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=networkplumber-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 4o5M6LMlDy5z for <tcpprague@ietfa.amsl.com>;
Mon, 24 Oct 2016 22:12:02 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com
[IPv6:2607:f8b0:4003:c06::22d])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 179E3129454
for <tcpPrague@ietf.org>; Mon, 24 Oct 2016 22:12:02 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id y2so77747166oie.0
for <tcpPrague@ietf.org>; Mon, 24 Oct 2016 22:12:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=networkplumber-org.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=xAdzo+JSa9NcR+eHfsPkaP4OTQksp5dqUmzm7R+jag8=;
b=iP0jNcjCk6UeGpZc8IDooctIgvkmeNrik0orluUHPMMgpztXqcqt4nyLEMazzv1die
WLXeEqHwgfqAQOwpY4MH0JeH4vca+aNAe8YtOO6weHpA7jfzjSYlD5Vyk6MA6GXdpZ8q
1oMCPUxU33XbC07PxWN2RVGWZ3FGCnX0R6ajD5GqobExcZMlzrFMyZkDfgt1wV8IAIb4
IdxZ+TtVFfzp3G865yUmojl1RJZjNbHZtKBJyZyS/zQKr2e196YX2mmyyoEpKLOdONz8
t59kY9r7xjWoaFmLN5Rd9WTXin/uB2vVxGg8mxJwr98HFsga1EQ6x5jPekMU3nNM0WYT
YU4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=xAdzo+JSa9NcR+eHfsPkaP4OTQksp5dqUmzm7R+jag8=;
b=P7ag7GOH1Pc5bwdPpbCNLhlJeJcmcDX7Ty30sV3A+MVrxljKwHgd/nWlUXcoMmFNuB
DNmIomueKUuyHSnFsxHE3oTEE2teBxDt2qJm0OOj0JPWUmY/SPU7K9iODfoneWBtpTqV
ud46gMS2jVJH7ZBI0cgYoay7dbv3IEx+X2hvXpSVgY2F8vAe5Wlri6hFkU5g1H5FpIH5
OSbsdE7z0N7Z8KSXSI+dHzh0pv9JEcwNOam4mZrptG5lZyeg4wFaZcspBdHqwNrlfPc2
W4z5hpFNtj6azWNH/p2Ywgj+cUxRO3lCl7coBo7Uas1ZAOTk04bozUiNHRTU4+47gYDg
SrvA==
X-Gm-Message-State: ABUngvfL3phC8qbEo9QTDrwm8I76OMOyh45sY4cLCQqG/7anx/eRVSJQkNjmfg8CW+UXCvdlcLcENsH7/cQ1DA==
X-Received: by 10.36.83.213 with SMTP id n204mr581455itb.100.1477372321252;
Mon, 24 Oct 2016 22:12:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.12.20 with HTTP; Mon, 24 Oct 2016 22:12:00 -0700 (PDT)
In-Reply-To: <BF6B00CC65FD2D45A326E74492B2C19FB76CC84C@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <68b1c3f2-dfc3-ffc3-da8b-24c535d77df0@pollere.com>
<BF6B00CC65FD2D45A326E74492B2C19FB76CC84C@FR711WXCHMBA05.zeu.alcatel-lucent.com>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 24 Oct 2016 22:12:00 -0700
Message-ID: <CAOaVG14Jx_f_BKjruRBLcSCu_U0F40K2k7JykfSMaJrC4KyHwQ@mail.gmail.com>
To: "De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia-bell-labs.com>
Content-Type: multipart/alternative; boundary=001a113f55c268dc09053fa98c30
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpprague/IBtqjIVMG4QT14eu0tDLsmaFKvI>
Cc: TCP Prague List <tcpPrague@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tcpPrague] [Bloat] DualPI2 qdisc implementation available for
Linux
X-BeenThere: tcpprague@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "To coordinate implementation and standardisation of TCP Prague
across platforms. TCP Prague will be an evolution of DCTCP designed to live
alongside other TCP variants and derivatives." <tcpprague.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpprague>,
<mailto:tcpprague-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpprague/>
List-Post: <mailto:tcpprague@ietf.org>
List-Help: <mailto:tcpprague-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpprague>,
<mailto:tcpprague-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2016 05:12:04 -0000
Why not submit it upstream where it can get more review and will get picked up by more users? On Fri, Jul 29, 2016 at 2:08 AM, De Schepper, Koen (Nokia - BE) < koen.de_schepper@nokia-bell-labs.com> wrote: > Hi all, > > For those who missed the L4S BoF, the PI2 AQM with DualQ option is > available on the following git: https://github.com/olgabo/dualpi2 > > PI2 (PI Improved with a Square) is a simplification of PIE (PI Enhanced) > with the advantage of also supporting L4S congestion controls (like DCTCP). > PI2 controls by default a single queue, with a common target (default > 20ms). To get the most out of the L4S traffic you need a second L4S queue > and a coupled AQM. PI2 supports this by specifying the "dualq" option. The > L4S queue is having an immediate step ECN marker at 1ms, while the classic > queue still has the 20ms target (with mark/drop coupled back to both L4S > and Classic). > > Note that PI2 supports DCTCP, but DCTCP is not the target to be used on > the internet. The TCP-Prague requirements (https://tools.ietf.org/html/ > draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-02#appendix-A) defines > what is needed to have an end-system CC implementation which behaves > similar to what FQ-X achieves in the network. FQ-X is a way the network can > correct the behavior of classic TCP CCs, TCP-Prague is the end-system > alternative that keeps the network simple and transport layer independent. > > Feel free to try it out, and join in developing a TCP CC that meets the > TCP-Prague requirements. > > Regards, > Koen. > > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >
- [tcpPrague] DualPI2 qdisc implementation availabl… De Schepper, Koen (Nokia - BE)
- Re: [tcpPrague] [Bloat] DualPI2 qdisc implementat… Stephen Hemminger