General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
To: Sebastian Moeller <moeller0@gmx.de>,
	Jonathan Foulkes <jf@jonathanfoulkes.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking
Date: Wed, 6 Jun 2018 09:44:35 +0200	[thread overview]
Message-ID: <8360fcc1-002b-11f9-ba7c-7b054840acff@kit.edu> (raw)
In-Reply-To: <9675C88A-FCC0-43EB-9C71-CBEFD67408CB@gmx.de>

Hi,

Am 05.06.2018 um 20:34 schrieb Sebastian Moeller:
> 	The rationale for that decision still is valid, at low bandwidth every opportunity to send a packet matters and every packet being transferred will increase the queued packets delay by its serialization delay. The question IMHO is more is 4 Mbps a reasonable threshold to disable ECN or not.

ECN should be enabled irrespective of the current bottleneck bandwidth.
I don't see any relationship between serialization delay with ECN.
Congestion control is about determining the right amount of inflight
data. ECN just provides an explicit congestion signal as feedback
and helps anyway. The main problem is IMHO that most routers have
no AQM in place in order to set the CE codepoint appropriately...

Regards,
 Roland


  parent reply	other threads:[~2018-06-06  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 ` [Bloat] Fwd: " 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                 ` Bless, Roland (TM) [this message]
2018-06-06  8:15                   ` [Bloat] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking 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
     [not found] <mailman.3.1527177601.17575.bloat@lists.bufferbloat.net>
2018-05-24 16:31 ` [Bloat] " Rich Brown

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=8360fcc1-002b-11f9-ba7c-7b054840acff@kit.edu \
    --to=roland.bless@kit.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=jf@jonathanfoulkes.com \
    --cc=moeller0@gmx.de \
    /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