From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: dave.collier-brown@indexexchange.com,
Jonathan Morton <chromatix99@gmail.com>,
David Collier-Brown <davecb@spamcop.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Adding CAKE "tc qdisc" options to NetworkManager
Date: Mon, 05 Oct 2020 23:10:01 +0200 [thread overview]
Message-ID: <87362spefq.fsf@toke.dk> (raw)
In-Reply-To: <5ceadc22-89e7-6ea4-6252-9e82645eae80@indexexchange.com>
Dave Collier-Brown <dave.collier-brown@indexexchange.com> writes:
> Alas, once I looked under the covers, it doesn't look easy at all.
> Definitely not a weekend project.
>
> I used to use QEF, and this reminds me of it.
Looks eminently copy-paste'able from that sfq commit you linked, though :)
-Toke
prev parent reply other threads:[~2020-10-05 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201005155644.GA1072516@tp>
2020-10-05 16:13 ` David Collier-Brown
2020-10-05 17:33 ` Jonathan Morton
2020-10-05 18:28 ` Dave Collier-Brown
2020-10-05 18:54 ` Dave Collier-Brown
2020-10-05 21:10 ` Toke Høiland-Jørgensen [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=87362spefq.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.collier-brown@indexexchange.com \
--cc=davecb@spamcop.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