Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Loganaden Velvindron <loganaden@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Sun, 24 Jul 2016 16:40:30 +0200	[thread overview]
Message-ID: <0B5FF17F-817F-4993-826D-DE55387D8D91@gmx.de> (raw)
In-Reply-To: <43469614-F02B-4D9B-8D0E-14D0F4211CF1@gmail.com>

Hi Jonathan,

> On Jul 24, 2016, at 13:28 , Jonathan Morton <chromatix99@gmail.com> wrote:
> 
> 
>> On 24 Jul, 2016, at 13:53, moeller0 <moeller0@gmx.de> wrote:
>> 
>> In theory interval can be different for ingress and egress (think old-school SAT-internet with modem upload) it probably is easiest to only configure one interval setting for the time being.
> 
> Since the interval parameter depends on the RTT, not the one-way delay, it should always be the same both ways (except for inter-packet-time effects).

	Thanks for setting this straight. I was confused; the thing that lingered at the back of my mind was that if we do the target extension for one direction and correct the interval in that direction, we should also correct the interval in the other direction, especially since as Jonathan points out the interval describes the full back-and-forth path…

Best Regards
	Sebastian


> 
> - Jonathan Morton
> 


  reply	other threads:[~2016-07-24 14:40 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 [this message]
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
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=0B5FF17F-817F-4993-826D-DE55387D8D91@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=loganaden@gmail.com \
    /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