Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Somebody want to hit me with a clue-by-four regarding fq_codel?
Date: Sat, 02 Jan 2021 13:21:09 -0500	[thread overview]
Message-ID: <11136.1609611669@turing-police> (raw)

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

OK, what am I missing here?  Laptop, linux-next kernel from last week.
And we'll skip the food fight about whether fq_codel makes sense for
end nodes - this is a different issue..

I've set fq_codel as the default qdisc

[/proc/sys/net] cat core/default_qdisc
fq_codel

but it's not being used?

[/proc/sys/net] tc -s qdisc show
qdisc noqueue 0: dev lo root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan0 root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0

But if I give it a kick in the head...

[/proc/sys/net] tc qdisc add dev wlan0 root fq_codel
[/proc/sys/net] tc -s qdisc show dev wlan0
qdisc fq_codel 8001: root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
 Sent 812 bytes 12 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0

(Admittedly, my first guess is "systemd is probably being its fascist self
and setting it to what *it* thinks things should be like"... :)




[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2021-01-02 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 18:21 Valdis Klētnieks [this message]
2021-01-02 18:26 ` Dave Taht
2021-01-02 19:49   ` Valdis Klētnieks

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11136.1609611669@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@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