Netdev List
 help / color / mirror / Atom feed
From: Marco Berizzi <pupilla@libero.it>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: WARNING: CPU: 3 PID: 0 at net/sched/sch_hfsc.c:1388 hfsc_dequeue+0x319/0x350 [sch_hfsc]
Date: Fri, 22 Jun 2018 13:05:04 +0200 (CEST)	[thread overview]
Message-ID: <337910499.641877.1529665504565@mail.libero.it> (raw)
In-Reply-To: <CAM_iQpVEZFL==0BuQh26Wh-TEJ-hmz7NwGry2g7EZiK-FCjKAQ@mail.gmail.com>

> Il 21 giugno 2018 alle 1.00 Cong Wang <xiyou.wangcong@gmail.com> ha scritto:
> Please also test HFSC_RSC ("rt") if possible.

Hi Cong,

sorry for the delayed response.
I have tested this hfsc rt setup:

tc class add dev eth2 parent 1:2 classid 1:16 hfsc rt m2 500kbit
and
tc class add dev eth2 parent 1:2 classid 1:16 hfsc rt m2 5000kbit
and
tc class add dev eth2 parent 1:2 classid 1:16 hfsc rt m2 20000kbit

and I was getting the expected throughput specified by the m2
parameter.

> If you can confirm nothing breaks, I will send it out formally.

after 52 hours uptime I don't see the previous error anymore.
 
> Thanks for testing!

and thanks for the patch.

      reply	other threads:[~2018-06-22 11:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:58 WARNING: CPU: 3 PID: 0 at net/sched/sch_hfsc.c:1388 hfsc_dequeue+0x319/0x350 [sch_hfsc] Marco Berizzi
2018-03-08 16:02 ` Marco Berizzi
2018-03-08 23:14   ` Cong Wang
2018-03-14  8:10     ` Marco Berizzi
2018-03-16  0:48       ` Cong Wang
2018-03-19 10:07         ` Jamal Hadi Salim
2018-03-22 14:12           ` Marco Berizzi
2018-04-06 10:53           ` Marco Berizzi
2018-06-05  6:39   ` Marco Berizzi
2018-06-18 19:28     ` Cong Wang
2018-06-19 11:42       ` Marco Berizzi
2018-06-20  7:00         ` Marco Berizzi
2018-06-20 23:00           ` Cong Wang
2018-06-22 11:05             ` Marco Berizzi [this message]

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=337910499.641877.1529665504565@mail.libero.it \
    --to=pupilla@libero.it \
    --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