From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 5FE353B25D for ; Wed, 3 Aug 2016 05:36:55 -0400 (EDT) Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id E0104D6E0D8DE; Wed, 3 Aug 2016 09:36:51 +0000 (GMT) Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u739asFo008059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Aug 2016 09:36:54 GMT Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u739arZc027093 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Aug 2016 11:36:53 +0200 Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.89]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 3 Aug 2016 11:36:28 +0200 From: "De Schepper, Koen (Nokia - BE)" To: bloat , "aqm@ietf.org" Thread-Topic: DualPI2 qdisc implementation available for Linux Thread-Index: AQHR7WqCu82C996tHEmuyucWbM9lUg== Date: Wed, 3 Aug 2016 09:36:27 +0000 Message-ID: Accept-Language: nl-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.41] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Bloat] DualPI2 qdisc implementation available for Linux X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2016 09:36:55 -0000 (reposted as the previous did not get through due to changed email address) Hi all, For those who missed the L4S BoF, the PI2 AQM with DualQ option is availabl= e on the following git: https://github.com/olgabo/dualpi2 PI2 (PI Improved with a Square) is a simplification of PIE (PI Enhanced) wi= th the advantage of also supporting L4S congestion controls (like DCTCP). P= I2 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 c= oupled AQM. PI2 supports this by specifying the "dualq" option. The L4S que= ue is having an immediate step ECN marker at 1ms, while the classic queue s= till has the 20ms target (with mark/drop coupled back to both L4S and Class= ic). 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-b= riscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-02#appendix-A) defines what is need= ed 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 behav= ior 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.