General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mario Hock <mario.hock@kit.edu>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking
Date: Tue, 5 Jun 2018 09:44:25 +0200	[thread overview]
Message-ID: <fca810ac-fafa-648a-6301-c2f6a020c14e@kit.edu> (raw)
In-Reply-To: <alpine.DEB.2.02.1806041557060.2048@nftneq.ynat.uz>

Am 05.06.2018 um 01:00 schrieb David Lang:
> On Mon, 4 Jun 2018, Bless, Roland (TM) wrote:
> 
>> Hi,
>>
>> Am 24.05.2018 um 17:38 schrieb Jan Ceuleers:
>>> Took 3 years after Dave approached them, but Ubuntu is finally adopting
>>> fq_codel as the default qdisc.
>>
>> Yes, if the Linux kernel is forwarding packets it makes a lot of sense,
>> but I don't understand why it make sense for ordinary end-systems.
>> Didn't Byte Queue Limits (BQL) suffice? Just curious...
> 
> no, BQL makes things much better (and make it possible for more advanced 
> quueing to take place), but you can still run into problems where a bulk 
> stream can flood the output queue so that other traffic suffers badly.
> 
> with fq_codel, the available bandwidth is distributed in a way that ends 
> up being much more functional.
> 
> It turns out that the behavior to prioritize new and sparse connections 
> significantly improves perceived performance (no more long delays in DNS 
> lookups before you start doing any real work for example)
> 
> without BQL, you can't even see the rest of the problems, but BQL 
> doesn't solve everything.

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?

Mario Hock

  reply	other threads:[~2018-06-05  7:44 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 [this message]
2018-06-05  7:49         ` Jonathan Morton
2018-06-05 11:01           ` Mario Hock
2018-08-16 21:08           ` Dave Taht
     [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=fca810ac-fafa-648a-6301-c2f6a020c14e@kit.edu \
    --to=mario.hock@kit.edu \
    --cc=bloat@lists.bufferbloat.net \
    /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