Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: dave seddon <dave.seddon.ca@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Ubiquity (Unifi ) Smart Queues
Date: Tue, 2 Jan 2024 23:57:29 +0200	[thread overview]
Message-ID: <18F24CCC-76E3-4FB0-AE62-BAAAFDEDB2EC@gmail.com> (raw)
In-Reply-To: <CANypexRYDqtsuj2vwX0qXWA=hXN3KZ5CJn5+vZRbm=Dikwh1Aw@mail.gmail.com>

> On 2 Jan, 2024, at 8:59 pm, dave seddon via Cake <cake@lists.bufferbloat.net> wrote:
> 
> 	• I'm not really sure what "overlimits" means or what that does, and tried looking this up, but I guess the kernel source is likely the "best" documentation for this.  Maybe this means it's dropping?  Or is it ECN?

Overlimit just means the shaper in HTB is restricting the flow, thus doing something useful.  Drop means the AQM is working to provide congestion information to a Not-ECT flow.  Those numbers look normal (about 0.2% drop rate, and most packets hitting "overlimit" when the link is saturated).

Using fq_codel's default parameters is not a bad thing at all.  I'd much rather they did that, thereby using numbers that are tuned for general Internet conditions, than try to change that tuning in ignorance of the end-user's actual network environment.  Most end-users have their WAN port facing "general Internet conditions" anyway.

> Apparently rather than applying the tc qdsic on the outbound path on the LAN side ( eth0 ), they are applying it inbound on the the eth2 via ifb_eth2.

That's the correct place to do it, so that the qdisc applies specifically to traffic coming from the WAN.  If you apply it to the LAN egress, it tends to affect traffic coming through the router from the WiFi or its internal servers, which is not desirable.

These are all questions we've considered at length in the process of developing and deploying Cake and other SQM solutions.

 - Jonathan Morton

  parent reply	other threads:[~2024-01-02 21:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 18:59 dave seddon
2024-01-02 20:52 ` Sebastian Moeller
2024-01-02 21:15   ` dave seddon
2024-01-02 21:24     ` Sebastian Moeller
2024-01-02 21:57 ` Jonathan Morton [this message]
2024-01-03 13:44 ` Pete Heist
2024-01-09 15:39   ` Nils Andreas Svee
2024-01-09 15:59     ` Dave Taht
2024-01-09 16:05     ` Dave Taht
2024-01-09 16:47       ` dave seddon
2024-01-09 16:57       ` Nils Andreas Svee
2024-01-09 17:07         ` dave seddon
2024-01-09 17:17           ` Dave Taht
2024-01-09 23:28             ` Nils Andreas Svee
2024-04-29 21:55               ` dave seddon
2024-01-09 23:17           ` Nils Andreas Svee

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=18F24CCC-76E3-4FB0-AE62-BAAAFDEDB2EC@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.seddon.ca@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