From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: mario.hock@kit.edu, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking
Date: Thu, 16 Aug 2018 14:08:31 -0700 [thread overview]
Message-ID: <CAA93jw4DH=jLA3oBGUYKx9d5Ua4i3K05oDydWNyTFmG7R5pECA@mail.gmail.com> (raw)
In-Reply-To: <5CCC459D-A142-42F9-BD10-97E69ED7E8F3@gmail.com>
On Tue, Jun 5, 2018 at 12:49 AM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 5 Jun, 2018, at 10:44 am, Mario Hock <mario.hock@kit.edu> wrote:
> >
> > Just to make sure that I got your answer correctly. The benefit for endsystems comes from the "fq" (flow queuing) part, not from the "codel" part of fq_codel?
>
> That's a fair characterisation, yes.
>
> In fact, even for middleboxes, the "flow isolation" semantics of FQ have the most impact on reducing inter-flow induced latency. The "codel" part (AQM) helps with intra-flow latency, which is usually much less important once flow isolation is in place, but is still worth having.
So, jonathan, this portion of the debate leaked over into
https://github.com/systemd/systemd/issues/9725
And I lost a great deal of hair over it. the codel portion is way
worth it on "end-systems".
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-08-16 21:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <152717340941.28154.812883711295847116.malone@soybean.canonical.com>
2018-05-24 15:38 ` Jan Ceuleers
2018-06-04 11:28 ` Bless, Roland (TM)
2018-06-04 13:16 ` Jonas Mårtensson
2018-06-04 17:08 ` Dave Taht
2018-06-04 18:22 ` Jonas Mårtensson
2018-06-04 21:36 ` Jonathan Morton
2018-06-05 15:10 ` [Bloat] " Jonathan Foulkes
2018-06-05 17:24 ` Jonathan Morton
2018-06-05 18:34 ` Sebastian Moeller
2018-06-05 19:31 ` Jonathan Morton
2018-06-06 6:53 ` Sebastian Moeller
2018-06-06 13:04 ` Jonathan Morton
2018-06-12 6:39 ` Dave Taht
2018-06-12 6:47 ` Dave Taht
2018-08-11 19:17 ` Dave Taht
2018-08-13 22:29 ` [Bloat] ecn redux Dave Taht
2018-06-06 7:44 ` [Bloat] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking Bless, Roland (TM)
2018-06-06 8:15 ` Sebastian Moeller
2018-06-06 8:55 ` Mario Hock
2018-06-05 0:22 ` [Bloat] Fwd: " Michael Richardson
2018-06-05 6:21 ` Jonas Mårtensson
2018-06-06 4:14 ` Mikael Abrahamsson
2018-06-07 12:56 ` [Bloat] Fwd: [Bug 1436945] -> What other options/bufferbloat-advice ... ? Simon Iremonger (bufferbloat)
2018-06-04 23:00 ` [Bloat] Fwd: [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking David Lang
2018-06-05 7:44 ` Mario Hock
2018-06-05 7:49 ` Jonathan Morton
2018-06-05 11:01 ` Mario Hock
2018-08-16 21:08 ` Dave Taht [this message]
[not found] <20150708105006.4232.80615.launchpad@gac.canonical.com>
2015-07-08 13:00 ` Jan Ceuleers
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='CAA93jw4DH=jLA3oBGUYKx9d5Ua4i3K05oDydWNyTFmG7R5pECA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=mario.hock@kit.edu \
/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