From: Stephen Hemminger <stephen@networkplumber.org>
To: "De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia-bell-labs.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
TCP Prague List <tcpPrague@ietf.org>
Subject: Re: [Bloat] DualPI2 qdisc implementation available for Linux
Date: Mon, 24 Oct 2016 22:12:00 -0700 [thread overview]
Message-ID: <CAOaVG14Jx_f_BKjruRBLcSCu_U0F40K2k7JykfSMaJrC4KyHwQ@mail.gmail.com> (raw)
In-Reply-To: <BF6B00CC65FD2D45A326E74492B2C19FB76CC84C@FR711WXCHMBA05.zeu.alcatel-lucent.com>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2453 bytes --]
next prev parent reply other threads:[~2016-10-25 5:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 15:47 [Bloat] some experiments with downstream queue delay Kathleen Nichols
2016-07-29 9:08 ` [Bloat] DualPI2 qdisc implementation available for Linux De Schepper, Koen (Nokia - BE)
2016-10-25 5:12 ` Stephen Hemminger [this message]
2016-08-03 9:36 De Schepper, Koen (Nokia - BE)
2016-08-10 9:36 ` Dave Täht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOaVG14Jx_f_BKjruRBLcSCu_U0F40K2k7JykfSMaJrC4KyHwQ@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=tcpPrague@ietf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox