From: grenville armitage <garmitage@swin.edu.au>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] fq_pie in FreeBSD... Re: Phoronix: Linux 5.9 to allow FQ_PIE as default
Date: Fri, 17 Jul 2020 11:16:17 +1000 [thread overview]
Message-ID: <446af9fe-c06b-3be9-e1fb-4157dafb481e@swin.edu.au> (raw)
In-Reply-To: <156954CF-BCBC-4B0C-9C42-A2A6F2450185@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
A tangent for anyone who is running a FreeBSD-based gateway, there's also an fq_pie in dummynet (https://reviews.freebsd.org/rS300779). I haven't played with it for a long time, but still curious if anyone's experimented with that combination. (Particularly if the on-the-wire behavior differs from that of linux fq-pie.)
cheers,
gja
On 2020-07-16 10:37, Jonathan Morton wrote:
> > On 16 Jul, 2020, at 12:58 am, Michael Yartys via Bloat <bloat@lists.bufferbloat.net> wrote:
> >
> > Are there any major differences between fq_codel and fq_pie in terms of their performance?
>
> I think some tests were run some time ago which showed significantly better behaviour by fq_codel than fq_pie. In particular, the latter used only a single AQM instead of an independent one for each flow. I'm not sure whether it's been changed since then.
>
> The only advantage I can see for PIE over Codel is, possibly, a reduction of system load for use of the AQM. But fq_codel is already pretty efficient so that would be an edge case.
>
> In any case, it is already possible to chose any qdisc you like (with default parameters) as the default qdisc. I'm really not sure what the fuss is about.
>
> > And how does the improved fq_codel called cobalt, which is used in cake, stack up?
>
> COBALT has some modifications to basic Codel which, I think, could profitably be backported into fq_codel. It also has a particular extra mode, based on BLUE, for dealing with unresponsive traffic (that continued to build queue even after lots of ECN signalling and/or Cdel-scheduled packet drops). It is the latter which inspired the name.
>
> For the other major functional component of fq_codel, Cake also has a set-associative hash function for allocating flows into queues, which substantially reduces the probability of hash collisions in most cases.
>
> - Jonathan Morton
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat <https://lists.bufferbloat.net/listinfo/bloat>
[-- Attachment #2: Type: text/html, Size: 3060 bytes --]
prev parent reply other threads:[~2020-07-17 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 21:58 [Bloat] " Michael Yartys
2020-07-16 0:37 ` Jonathan Morton
2020-07-16 18:07 ` Toke Høiland-Jørgensen
2020-07-17 1:16 ` grenville armitage [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=446af9fe-c06b-3be9-e1fb-4157dafb481e@swin.edu.au \
--to=garmitage@swin.edu.au \
--cc=bloat@lists.bufferbloat.net \
/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