From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] How can I tell if fq_codel is running?
Date: Tue, 30 Jul 2019 15:34:21 -0700 [thread overview]
Message-ID: <6232ad09-4d8b-c953-9e67-7fe774bb9a80@sewingwitch.com> (raw)
I'm running CentOS 7 on a Dell R230 as a small office router. It's on a
slow ADSL link, 1.5 Mbps down and 150 kbps up. The kernel supports
fq_codel, as does the tg3 driver used by the interfaces.
In the past I've run the Wondershaper script and now I'm hoping the new
codel improves on that. I think it's installed but I don't see its name
in a "tc show". Should I see it there? Is there additional setup I need
to do?
The system seems responsive but I've been tasked with prioritizing the
network for certain users. Before, I set up some buckets in the
wondershaper for that. I'm now trying to figure out how that's supposed
to work with codel, which is ostensibly "knob-free".
[root@saruman ~]# tc -s class show dev em2
class mq :1 root
Sent 127961591021 bytes 412946653 pkt (dropped 0, overlimits 0
requeues 2726)
backlog 0b 0p requeues 2726
class mq :2 root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
class mq :3 root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
class mq :4 root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
class mq :5 root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
[root@saruman ~]# sysctl net.core.default_qdisc
net.core.default_qdisc = fq_codel
next reply other threads:[~2019-07-30 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 22:34 Kenneth Porter [this message]
2019-07-30 22:45 ` Stephen Hemminger
2019-07-30 22:58 ` Dave Taht
2019-07-31 0:01 ` Kenneth Porter
[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=6232ad09-4d8b-c953-9e67-7fe774bb9a80@sewingwitch.com \
--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