From: Eric Dumazet <eric.dumazet@gmail.com>
To: John Fastabend <john.fastabend@gmail.com>,
Networking <netdev@vger.kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: [BUG] net/sched : qlen can not really be per cpu ?
Date: Mon, 25 Feb 2019 22:42:17 -0800 [thread overview]
Message-ID: <5fb87db3-d5bd-714b-213d-6821f4bf37da@gmail.com> (raw)
HTB + pfifo_fast as a leaf qdisc hits badly the following warning in htb_activate() :
WARN_ON(cl->level || !cl->leaf.q || !cl->leaf.q->q.qlen);
This is because pfifo_fast does not update sch->q.qlen, but per cpu counters.
So cl->leaf.q->q.qlen is zero.
HFSC, CBQ, DRR, QFQ have the same problem.
Any ideas how we can fix this ?
Thanks !
next reply other threads:[~2019-02-26 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 6:42 Eric Dumazet [this message]
2019-02-26 23:19 ` [BUG] net/sched : qlen can not really be per cpu ? Eric Dumazet
2019-02-26 23:51 ` Cong Wang
2019-02-27 0:56 ` Eric Dumazet
2019-02-27 16:59 ` Eric Dumazet
2019-02-28 2:46 ` Cong Wang
2019-02-28 5:15 ` Eric Dumazet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fb87db3-d5bd-714b-213d-6821f4bf37da@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).