Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Loganaden Velvindron <loganaden@gmail.com>
Cc: moeller0 <moeller0@gmx.de>, cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Wed, 3 Aug 2016 12:48:47 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1608031247280.16896@nftneq.ynat.uz> (raw)
In-Reply-To: <CAOp4FwSKThsgeGFRLsgLbnhSP30fZ2mCgJkM-7MB=SU2kmYk0A@mail.gmail.com>

On Wed, 3 Aug 2016, Loganaden Velvindron wrote:

> My conclusion from playing with fq_codel, cake, and txqueuelen 0 hacks
> is that as a pre-requisite, we need to have ISPs that are able to give
> latency with little variations to various places around the earth.
>
> Proving that any QoS on high bandwidth with volatile RTTs is difficult
> due to the "jitter".
>
>
> Please correct me if I'm wrong.

I think you have the order wrong. In order for the ISPs to provide consistant 
latencies, we need fq_codel, cake, or similar to be deployed widely, including 
in the ISP equipment so that the latencies are managed sanely when overloads 
hit.

David Lang

  reply	other threads:[~2016-08-03 19:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  4:29 Loganaden Velvindron
2016-07-19  8:09 ` Jonathan Morton
2016-07-19 10:16   ` moeller0
     [not found]     ` <CAOp4FwQs9-PF=V5zDDMVj_38qmziKkeZECTyX1e8EfChtGm8bA@mail.gmail.com>
     [not found]       ` <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de>
2016-07-23 18:36         ` Loganaden Velvindron
2016-07-23 18:59           ` Loganaden Velvindron
2016-07-24  5:53             ` Loganaden Velvindron
2016-07-24  6:12               ` Loganaden Velvindron
2016-07-24  7:03                 ` Loganaden Velvindron
2016-07-24  8:27                   ` moeller0
2016-07-24  8:43                     ` Loganaden Velvindron
2016-07-24 10:53               ` moeller0
2016-07-24 11:28                 ` Jonathan Morton
2016-07-24 14:40                   ` moeller0
2016-07-24 16:18                     ` Jonathan Morton
2016-07-24 17:13                     ` Loganaden Velvindron
2016-07-24 17:21                       ` moeller0
2016-07-24 19:43                         ` Loganaden Velvindron
2016-07-25  4:13                           ` Loganaden Velvindron
2016-07-26 21:10                             ` Loganaden Velvindron
2016-07-30  3:45                               ` Loganaden Velvindron
2016-07-30 13:04                                 ` Mario Ferreira
2016-07-30 13:48                                   ` Loganaden Velvindron
2016-07-30 14:07                                     ` Mario Ferreira
2016-08-03 18:52                               ` Loganaden Velvindron
2016-08-03 19:48                                 ` David Lang [this message]
2016-07-19 17:13   ` Loganaden Velvindron

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1608031247280.16896@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cake@lists.bufferbloat.net \
    --cc=loganaden@gmail.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