Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] #17
Date: Sun, 12 Apr 2015 14:59:20 -0700	[thread overview]
Message-ID: <CAA93jw5eRMNAwba7UphtWrpH1hT_aKM9eDhATNAL3AV9-9iE4g@mail.gmail.com> (raw)
In-Reply-To: <EFD9024A-2241-4271-A767-270A41703A5D@gmx.de>

It is not clear if atm framing and things like pppoe are used at
higher rates on newer technologies like GPON and fiber. They are not
used in cablemodems, for example. Given the headache it has been to
get that straightened out on DSL AND detect AND configure properly, I
would not mind if we abandoned the idea of supporting alternate
framings in cake, and stuck with what already works in the sqm-scripts
with htb + fq_codel.



On Sun, Apr 12, 2015 at 12:18 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi list, hi Dave
>
> On Sat Apr 11 19:33:59 PDT 2015, Dave That <dave.taht at gmail.com> wrote:
> 17)  the atm compensation in cake is entirely untested. And it is
> unclear as to how best handle pppoe.
>
> Regarding ATM, it seems from http://www.bufferbloat.net/projects/codel/wiki/Cake that there is only one command line argument “atm” to activate accounting for atm encapsulation. I venture a guess that this will not be sufficient as it seems  necessary to add the per packet overhead before “expanding” the packet size to the 43 in 53 atm cells. This might be really just a documentation issue (I have not looked agh cake’s code, not that I a) read C well and b) know where to find the cake code repository). In my experience the relevant per packet overhead on the ATM link needs to be measured on each link individually (and repeatedly to catch the ISPs doing funny things like adding an otherwise invisible vlan tag on the atm link).
>
> PPPoE, is easy, either drill into the packets to get the values used for hashing, or ask people to activate cake on the pppoe interfaces in the router (these typically do not show the pppoe headers so that classifier will find the right values). Or you could argue that a PPPoE link really is just one flow, and hence does not deserve special treatment ;) (which other “multiplexors” would deserve the same special treatment SPDY/HTTP2?).
>
> Best Regards
>         Sebastian
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

  reply	other threads:[~2015-04-12 21:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 19:18 Sebastian Moeller
2015-04-12 21:59 ` Dave Taht [this message]
2015-04-12 23:50   ` Sebastian Moeller
2015-04-12 23:55     ` Jonathan Morton
2015-04-13  0:15       ` Sebastian Moeller
2015-04-13  0:23         ` Sebastian Moeller
2015-04-13  0:45           ` Jonathan Morton
2015-04-13  6:51             ` Sebastian Moeller
2015-04-13 14:45             ` Sebastian Moeller
2015-04-14 10:13               ` Jonathan Morton
2015-04-14 10:34                 ` Sebastian Moeller
2015-04-13 14:59   ` Sebastian Moeller
2015-04-13 17:06     ` Jonathan Morton
2015-04-13 19:45       ` Sebastian Moeller
2015-04-13 20:08         ` Jonathan Morton
2015-04-13 20:10           ` Sebastian Moeller
2015-04-14  0:58             ` Jonathan Morton
2015-04-14  1:24               ` Dave Taht
2015-04-14  7:03               ` Sebastian Moeller

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=CAA93jw5eRMNAwba7UphtWrpH1hT_aKM9eDhATNAL3AV9-9iE4g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --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