General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel]   DOCSIS 3+ recommendation?
Date: Sat, 21 Mar 2015 02:34:23 +0200	[thread overview]
Message-ID: <D89D7FB2-B0BD-48B0-B000-00507D1E44CB@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503201716420.22474@nftneq.ynat.uz>


> On 21 Mar, 2015, at 02:25, David Lang <david@lang.hm> wrote:
> 
> As I said, there are two possibilities
> 
> 1. if you mark packets sooner than you would drop them, advantage non-ECN
> 
> 2. if you mark packets and don't drop them until higher levels, advantage ECN, and big advantage to fake ECN

3: if you have flow isolation with drop-from-longest-queue-on-overflow, faking ECN doesn’t matter to other traffic - it just turns the faker’s allocation of queue into a dumb, non-AQM one.  No problem.

 - Jonathan Morton


  reply	other threads:[~2015-03-21  0:34 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150316203532.05BD21E2@taggart.lackof.org>
     [not found] ` <123130.1426635142@turing-police.cc.vt.edu>
     [not found]   ` <b8526a9c-5305-4467-8fd2-a6d1e0016903@reed.com>
     [not found]     ` <CAJq5cE2nLRKuq64vQgpPSQ01e2Mc5Vtguo6smQg+ySC8mLH=aQ@mail.gmail.com>
     [not found]       ` <15A0911A-E3B7-440A-A26B-C5E1489EA98B@viagenie.ca>
     [not found]         ` <CAJq5cE1UFgt6fpLxRH7m3VFUpziGZm9OLCCNFQ93QemH00CHaQ@mail.gmail.com>
     [not found]           ` <1426773234.362612992@apps.rackspace.com>
2015-03-19 17:11             ` Dave Taht
2015-03-19 19:58               ` Livingood, Jason
2015-03-19 20:29                 ` dpreed
2015-03-19 23:18                   ` Greg White
2015-03-20  8:18                     ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31                       ` David P. Reed
2015-03-20 13:46                         ` Sebastian Moeller
2015-03-20 14:05                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07                     ` Sebastian Moeller
2015-03-20 13:50                     ` [Bloat] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36                       ` Pedro Tumusok
2015-03-30  7:06                         ` Jonathan Morton
2015-03-30 13:56                           ` Pedro Tumusok
2015-03-30 14:18                             ` Jonathan Morton
2015-03-30 14:20                               ` Pedro Tumusok
2015-03-30 14:55                                 ` Dave Taht
2015-03-30 16:05                                   ` Pedro Tumusok
2015-03-31  5:07                                     ` Jesper Dangaard Brouer
2015-04-01 17:21                                       ` Pedro Tumusok
     [not found]                                         ` <CAH3Ss96599p_22c+9Dm5s2LUGwkvnc_ivunpz6aTzDAteS1ZPg@mail.gmail.com>
     [not found]                                           ` <CACQiMXYxbbLh=rVWK2MnTfo7xePoy794k_V36XDrJxybKiiC9g@mail.gmail.com>
2015-04-07 17:16                                             ` [Bloat] Fwd: " Pedro Tumusok
2015-03-30 16:20                                   ` [Bloat] " Livingood, Jason
2015-03-31  1:30                                 ` Pedro Tumusok
2015-03-31  4:14                                   ` Jonathan Morton
2015-03-30 14:42                               ` [Bloat] Latency Measurements in Speed Test suites Toke Høiland-Jørgensen
2015-03-20 13:57                     ` [Bloat] [Cerowrt-devel] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08                       ` David P. Reed
2015-03-20 14:14                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48                           ` Matt Mathis
2015-03-20 13:48                 ` Jim Gettys
2015-03-20 14:11                   ` Livingood, Jason
2015-03-20 14:54                     ` Michael Welzl
2015-03-20 15:31                       ` Jim Gettys
2015-03-20 15:39                         ` Michael Welzl
2015-03-20 16:31                       ` Jonathan Morton
2015-03-20 20:59                         ` Michael Welzl
2015-03-20 23:47                           ` David P. Reed
2015-03-21  0:08                             ` Michael Welzl
2015-03-21  0:03                           ` David Lang
2015-03-21  0:13                             ` Steinar H. Gunderson
2015-03-21  0:25                               ` David Lang
2015-03-21  0:34                                 ` Jonathan Morton [this message]
2015-03-21  0:38                                   ` David Lang
2015-03-21  0:43                                     ` Jonathan Morton
2015-03-22  4:15                                 ` Michael Welzl
2015-03-21  0:15                             ` Michael Welzl
2015-03-21  0:29                               ` David Lang
2015-03-22  4:10                                 ` Michael Welzl
2015-03-20 18:14                     ` Jonathan Morton

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=D89D7FB2-B0BD-48B0-B000-00507D1E44CB@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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