Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michel Blais <michel@targointernet.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Bandwidith rate by host instead of global while using [dual-]srchost and [dual-]dsthost
Date: Mon, 11 Jun 2018 10:44:37 -0700	[thread overview]
Message-ID: <CAA93jw4sXh+OW12skttnCrmbj1-qpBJARsVGrthw2dyqtRzc6w@mail.gmail.com> (raw)
In-Reply-To: <CAAWM72U2tZwFRSpLDpVNn1t0OZB=VDqAs89dUNCCNTDzD5vkFQ@mail.gmail.com>

On Mon, Jun 11, 2018 at 8:43 AM, Michel Blais <michel@targointernet.com> wrote:
> Hi all,
>
> Is it possible while using srchost, or dual-srchost, and dsthost, or
> dual-dsthost, to do a bandwidth limitation by host instead of global ? From
> what I read, seem like not.

No. It's been one of those things where custom non-linux hardware is
used on the head end (CMTSes, DSLAMs),
where even trying seems futile. If there was a head-end maker that
wanted to try (and sponsor the effort), that would be cool.

One way to maybe get there without custom hw would be to insert a fat
x86 or arm64 cake box in front of a CMTS or dslam as a transparent
bridge (much like we see with certain dpi products) to do one veth per
subscriber. We'd coalesce all the IPs a subscriber has into a cake
instance

# eth0 takes all traffic, eth1 outputs the reshaped traffic
# bridge veth0,veth1 to eth1
# Route customer 1
ip route add 1.1.1.1 dev veth0
ip route add 2001::1:x:y:z/64 dev veth0
# Route customer 2
ip route add 1.1.1.2 dev veth1
ip route add 2001::2:x:y:z/64 dev veth1

tc qdisc add dev veth0 cake bandwidth 100mbit
tc qdisc add dev veth1 cake bandwidth 20mbit

Some comms from the head-end would be helpful to be monitoring the
achieved rate (line noise issues) and global bandwidth available
and tweaking each cake instance to suit every few seconds (tc qdisc
change dev veth0 cake bandwidth 80mbit).

Given that the latest cake is cracking 40gbit on a single interface,
it might be interesting to see how hard we could push, say, 10,000
instances like the above through a big box to see what happens. But I
tend to think the work should be layered onto a line card rather than
a separate box.

This is why we try so hard to make the code dual licensed and publish
papers documenting the algoriths. 7 years after this effort started
cable head-ends still use 2sec of FIFO buffering. I'd had high hopes
we'd see *something* from arris by now that did more of the right
thing.

they tried sfq way back when

https://pdfs.semanticscholar.org/c577/0612bfaa1dff4daf2b0cfe56b79627dddc9c.pdf

and sfq is in one of their fiber products.

I keep hoping we'll make some onts and gpon hardware soon, with bql +
fq_codel at least.

> I saw several times on messages on mailling list that some option could be
> usefull for ISP and dual-srchost and dual-dsthost would seem something
> usefull for small ISP, an alternative to Mikrotik PCQ with all the advantage
> of cake like flow fairness and latency.

Keep hoping that mikrotik will get on the ball. Many fq_codel requests
on their forums. ubnt is all over this stuff.

> Thanks
> ---
> Cordialement,  /  With regards,
>
> Michel Blais
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-06-11 17:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 15:43 Michel Blais
2018-06-11 17:44 ` Dave Taht [this message]
2018-06-11 19:44 ` Toke Høiland-Jørgensen
2018-06-11 19:54   ` Stephen Hemminger
2018-06-11 20:17     ` Dave Taht
2018-06-12  6:55       ` Pete Heist
2018-06-12 18:55         ` Dave Taht
2018-06-16 15:33           ` Michel Blais
2018-06-16 19:20             ` Pete Heist
2018-06-16 19:26               ` Pete Heist
2018-06-17 13:35             ` Toke Høiland-Jørgensen

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=CAA93jw4sXh+OW12skttnCrmbj1-qpBJARsVGrthw2dyqtRzc6w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=michel@targointernet.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