From: Dave Taht <dave.taht@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Somebody want to hit me with a clue-by-four regarding fq_codel?
Date: Sat, 2 Jan 2021 10:26:44 -0800 [thread overview]
Message-ID: <CAA93jw7DUinr_drxCLfNmk3J793_XbqWWrMev48-p5i9tW2gEA@mail.gmail.com> (raw)
In-Reply-To: <11136.1609611669@turing-police>
wlan0 is using the native fq_codel implementation if you see a aqm
field in the sysfs, and noqueue for all other wifi devices as the
drivers themselves were so overbuffered there was no point in
pfifo_fast for them.
systemd is supposed to set fq_codel for you in /etc/sysctl.conf or
elsewhere, for your ethernet.
On Sat, Jan 2, 2021 at 10:21 AM Valdis Klētnieks
<valdis.kletnieks@vt.edu> wrote:
>
> 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"... :)
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-01-02 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 18:21 Valdis Klētnieks
2021-01-02 18:26 ` Dave Taht [this message]
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=CAA93jw7DUinr_drxCLfNmk3J793_XbqWWrMev48-p5i9tW2gEA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=valdis.kletnieks@vt.edu \
/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