From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] lan keyword affects host fairness
Date: Fri, 24 Nov 2017 20:41:36 +0100 [thread overview]
Message-ID: <B073471D-B8D2-4718-9C4E-77D60DDD3E4C@gmail.com> (raw)
In-Reply-To: <0D339F2F-F2CB-4800-84B9-E7321AE4D15E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
> On Nov 24, 2017, at 2:49 PM, Pete Heist <peteheist@gmail.com> wrote:
>
> Removing the bandwidth keywords altogether and going back to fq_codel’s specification of target and interval would be my personal preference (unless we can figure out how to make the keywords work well with one another in all cases).
To add to my comments, this probably came across as too harsh or discontinuous an idea at this stage when we’re in the process of shoring things up- that wasn’t my intent!
There is the other side that these keywords save people from having to know more. Which is better, explaining target and interval to everyone or having them use these? I imagine that was the logic that went into it. Also, if it’s not a good idea to be changing the configuration interface at this point (and it may not be), then there are alternatives, and the man page addition will definitely help people. Maybe I’ll make some runs across a range of rtts to understand this better…
[-- Attachment #2: Type: text/html, Size: 2072 bytes --]
next prev parent reply other threads:[~2017-11-24 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 9:21 Pete Heist
2017-11-23 9:44 ` Jonathan Morton
2017-11-23 10:25 ` Pete Heist
2017-11-23 17:03 ` Dave Taht
2017-11-24 11:21 ` Toke Høiland-Jørgensen
2017-11-24 12:06 ` Sebastian Moeller
2017-11-24 13:15 ` Marcelo Ricardo Leitner
2017-11-24 13:49 ` Pete Heist
2017-11-24 19:41 ` Pete Heist [this message]
2017-11-24 19:48 ` Jonathan Morton
2017-11-24 20:24 ` Pete Heist
[not found] ` <CAJq5cE2eX4AJCPaBL-FW7Oj_afthXKnZn1RHQPH1VBCJfCyXDg@mail.gmail.com>
2017-11-24 20:32 ` Jonathan Morton
2017-11-25 7:18 ` Pete Heist
2017-11-24 20:03 ` Dave Taht
2017-11-24 20:40 ` Dave Taht
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=B073471D-B8D2-4718-9C4E-77D60DDD3E4C@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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