From: Peter Lepeska <bizzbyster@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Enforcing video quality question
Date: Thu, 18 Feb 2021 14:43:18 -0500 [thread overview]
Message-ID: <CANmPAYFviqW_FekQ-xag-i1qhZ1JHP71MvB+M-qFKdOXLKEUaw@mail.gmail.com> (raw)
In-Reply-To: <87im6pkweq.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Ok that makes sense. I'll do some reading. Thank you!
On Thu, Feb 18, 2021 at 2:28 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Peter Lepeska <bizzbyster@gmail.com> writes:
>
> > A user on the OpenWrt forum suggested hashlimit rules supported by
> > iptables. How does that idea sound to you?
>
> That will result in a cliff-edge policer (i.e., as soon as a device goes
> over its limits it will see every packet get dropped). This doesn't
> interact too well with the burstiness of TCP, so you'll likely get
> erratic behaviour of the traffic if you do that. Doing the same thing
> with HTB means the router will queue+shape each class (and with FQ-CoDel
> on the leaves, you'll get a nice AQM behaviour as well), so that will be
> smoother and less prone to bloat :)
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 1191 bytes --]
next prev parent reply other threads:[~2021-02-18 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 17:40 Peter Lepeska
2021-02-18 19:10 ` Toke Høiland-Jørgensen
2021-02-18 19:13 ` Peter Lepeska
2021-02-18 19:28 ` Toke Høiland-Jørgensen
2021-02-18 19:43 ` Peter Lepeska [this message]
2021-02-18 19:55 ` N0man Tech
2021-02-18 22:05 ` John Yates
2021-02-19 12:16 ` John Sager
2021-02-19 15:02 ` Peter Lepeska
2021-02-19 19:04 ` John Sager
2021-02-19 20:33 ` Peter Lepeska
2021-02-19 23:06 ` John Sager
2021-02-19 23:26 ` Jeremy Marks
2021-02-20 11:53 ` Toke Høiland-Jørgensen
2021-02-20 15:09 ` John Sager
2021-02-20 11:54 ` Toke Høiland-Jørgensen
2021-02-23 11:15 ` John Sager
2021-02-23 20:37 ` Peter Lepeska
2021-02-23 20:52 ` Jeremy Marks
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=CANmPAYFviqW_FekQ-xag-i1qhZ1JHP71MvB+M-qFKdOXLKEUaw@mail.gmail.com \
--to=bizzbyster@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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