From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Sebastian Moeller" <moeller0@gmx.de>,
cake@lists.bufferbloat.net,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [Cake] [PATCH net-next] sched: sch_cake: Align QoS treatment to Windows and Zoom
Date: Fri, 10 Jan 2025 11:43:33 -0800 [thread overview]
Message-ID: <CAA93jw7XUfR7Ww40nh5EZ8U8pMUezhSY6PFLoaGj+pGnzeYZbg@mail.gmail.com> (raw)
In-Reply-To: <898E9FB0-D92E-4421-8CCD-1B9F4A3D9D5D@gmail.com>
ok, I concede on NQB. Do we at least have agreement that CS5 belongs
in the VI queue, not the VO queue, on diffserv4?
On Fri, Jan 10, 2025 at 9:43 AM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 10 Jan, 2025, at 7:07 pm, Dave Taht via Cake <cake@lists.bufferbloat.net> wrote:
> >
> > I do not think NQB belongs in Voice (which shares priority with
> > netcontrol, etc). I also do not think it belongs in best effort as the
> > intent is to get a quick response to a short flow. yes, FQ solves a
> > lot of problems, but
>
> As far as I'm concerned, FQ implements everything that NQB wants. In a system implementing FQ, treating NQB traffic as best-effort is the Right Thing.
>
> And I second the notion that slavishly copying wthe broken default behaviour of WiFi routers is the Wrong Thing.
>
> - Jonathan Morton
>
--
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2025-01-10 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 15:55 Toke Høiland-Jørgensen
2025-01-10 16:24 ` Sebastian Moeller
2025-01-10 16:34 ` Dave Taht
2025-01-10 17:02 ` Sebastian Moeller
2025-01-10 17:07 ` Dave Taht
2025-01-10 17:17 ` Sebastian Moeller
2025-01-10 17:43 ` Jonathan Morton
2025-01-10 19:43 ` Dave Taht [this message]
2025-01-10 20:34 ` Sebastian Moeller
2025-01-22 19:35 ` Dave Taht
2025-01-22 21:18 ` Sebastian Moeller
2025-01-10 19:06 ` 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=CAA93jw7XUfR7Ww40nh5EZ8U8pMUezhSY6PFLoaGj+pGnzeYZbg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=moeller0@gmx.de \
--cc=toke@redhat.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