From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] tc coding comments
Date: Thu, 19 Nov 2015 09:56:41 +0100 [thread overview]
Message-ID: <CAA93jw4y0yqWXRRsVX0Jz3o8Wegy6OAvgggK159P6DyVXyRbEA@mail.gmail.com> (raw)
Maybe: squash and wash? Squash would be best effort only, wash would
be whatever diffserv model
The "tc standard" for compound variables is mostly whatever_it_is, not
whatever-it-is or "whatever it is"
drops: Dropped_bytes might be a good indicator also
indentation is needed to differentiate between qdisc invocations on mq
and full blown dumps
tc qdisc add dev whatever root cake bandwidth 50gbit does not work
"unlimited" vs "bandwidth X" is asymmetric. "bandwidth unlimited"?
is tc qdisc change dev whatever root cake bandwidth new_bandwidth
Xmbit # is efficient, not drop packets on the change itself?
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
next reply other threads:[~2015-11-19 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 8:56 Dave Taht [this message]
2015-11-19 11:03 ` Sebastian Moeller
2015-11-19 11:11 ` Kevin Darbyshire-Bryant
2015-11-19 11:15 ` Toke Høiland-Jørgensen
2015-11-19 11:25 ` Kevin Darbyshire-Bryant
2015-11-19 12:05 ` Kevin Darbyshire-Bryant
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=CAA93jw4y0yqWXRRsVX0Jz3o8Wegy6OAvgggK159P6DyVXyRbEA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@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