From: Jonathan Morton <chromatix99@gmail.com>
To: Evan Mesterhazy <evan.mesterhazy@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Do codel or fq-codel need to know the link bandwidth?
Date: Sun, 8 Dec 2024 04:53:46 +0200 [thread overview]
Message-ID: <F0E1E61A-6CCE-4D8B-819E-0DA5D9510F70@gmail.com> (raw)
In-Reply-To: <CAN2qZSN53zHBszcW1-kY5+SLvAVaNAHZnGJeiM1vJJEbbS0VKg@mail.gmail.com>
> On 7 Dec, 2024, at 11:27 pm, Evan Mesterhazy <evan.mesterhazy@gmail.com> wrote:
>
> However, I have noticed that the commercial implementations for at least two firewalls that I have used (OPNsense and a Unifi gateway) both require the user to input the upload and download bandwidths of the link.
That's because they combine three algorithms into a coherent package. All three algorithms do something different which is a crucial part of the whole.
FQ_Codel is a combination of two of these algorithms: the Codel AQM (which signals to traffic when it's passing through a congested link) and the DRR++ Fair Queuing algorithm, which essentially isolates different flows from interfering with each other.
The third algorithm is called a "shaper". It moves the bottleneck out of the link hardware itself (which isn't smart enough to run FQ_Codel) and into the CPU (which is). It is the shaper that needs to know what bandwidth to use, because it can't directly sense the link characteristics from where it is.
- Jonathan Morton
prev parent reply other threads:[~2024-12-08 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 21:27 Evan Mesterhazy
2024-12-07 22:25 ` Dave Taht
2024-12-07 22:31 ` Dave Taht
2024-12-07 22:57 ` Evan Mesterhazy
2024-12-08 2:53 ` Jonathan Morton [this message]
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F0E1E61A-6CCE-4D8B-819E-0DA5D9510F70@gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=evan.mesterhazy@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