From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] How can I tell if fq_codel is running?
Date: Tue, 30 Jul 2019 17:01:11 -0700 [thread overview]
Message-ID: <E136E8699FCBCE46AB566940@[192.168.1.16]> (raw)
In-Reply-To: <CAA93jw6vY0oMa1PF5EWBXWX_+9QZf_aY+YkcnuMvsVhQzq_bGg@mail.gmail.com>
--On Tuesday, July 30, 2019 4:58 PM -0700 Dave Taht <dave.taht@gmail.com>
wrote:
> see also
> https://www.bufferbloat.net/projects/bloat/wiki/Wondershaper_Must_Die/
>
> and https://github.com/tohojo/sqm-scripts
Coincidentally, I found sgm-scripts right after posting. What prereqs are
there to using that? I'm poking through the code and it looks like it
should work, although I don't know if the CentOS 7 kernel has cake.
next prev parent reply other threads:[~2019-07-31 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 22:34 Kenneth Porter
2019-07-30 22:45 ` Stephen Hemminger
2019-07-30 22:58 ` Dave Taht
2019-07-31 0:01 ` Kenneth Porter [this message]
[not found] ` <E136E8699FCBCE46AB566940@192.168.1.16>
2019-07-31 0:13 ` Dave Taht
2019-07-30 23:58 ` Kenneth Porter
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='E136E8699FCBCE46AB566940@[192.168.1.16]' \
--to=shiva@sewingwitch.com \
--cc=bloat@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