From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake infinite loop(?) with hfsc on one-armed router
Date: Sat, 5 Jan 2019 16:34:24 +0100 [thread overview]
Message-ID: <797FCC60-0048-4EF6-80BC-19707E9173FB@heistp.net> (raw)
In-Reply-To: <87o98vxm57.fsf@toke.dk>
> On Jan 5, 2019, at 2:35 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Pete Heist <pete@heistp.net> writes:
>
>>> On Jan 5, 2019, at 2:10 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>>
>>> Hmm, that's odd. Could you try adding this debugging line in
>>> adjust_parent_qlen(), right before the sch->q.qlen += n line:
>>>
>>> net_info_ratelimited("Adjusting parent qdisc %d with pkt += %d, len += %d",
>>> parentid, n, len);
>>>
>>> And see if you actually get any of those lines in your dmesg?
>>
>> I do see the messages twice, then not after that in the rest of the
>> output...
>
> Right. Looking at the HFSC code some more, I think the bug is actually
> caused by another, but related, interaction between HFSC and CAKE.
>
> Specifically, this line:
>
> https://elixir.bootlin.com/linux/v3.16.7/source/net/sched/sch_hfsc.c#L1605
>
> where HFSC checks whether the child queue len is 1, which it interprets
> as the event that activates that queue. However, because CAKE splits the
> packet, this check will fail, and the HFSC class will not be activated.
> This also explains why you only see the bug with HFSC, and not with HTB
> (although I do think that we still need to update the hierarchy).
>
> The good news it that it is a fairly simple to fix in HFSC. The bad news
> is that it's something that's hard to work around from the out-of-tree
> CAKE...
Aha, well, I wonder if we’ll see this problem with other qdiscs- maybe cbq, if I ever get a chance to try it (not hurrying yet). Ideally this interaction between qdiscs would be clarified somewhere, at some point. :)
Thanks a lot for doing the discovery though! We may not have hfsc+cake with GSO splitting on older kernels very soon, but what should we do with this? There’s nobody in MAINTAINERS for hfsc, so we may not get much of a response to any bug submissions...
Pete
next prev parent reply other threads:[~2019-01-05 15:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 23:30 Pete Heist
2018-12-28 12:58 ` Pete Heist
2018-12-28 21:22 ` Pete Heist
2018-12-28 22:07 ` Jonathan Morton
2018-12-28 22:42 ` Pete Heist
2019-01-04 21:34 ` Toke Høiland-Jørgensen
2019-01-04 22:10 ` Pete Heist
2019-01-04 22:12 ` Pete Heist
2019-01-04 22:34 ` Toke Høiland-Jørgensen
2019-01-05 5:58 ` Pete Heist
2019-01-05 10:06 ` Toke Høiland-Jørgensen
2019-01-05 10:59 ` Pete Heist
2019-01-05 11:06 ` Pete Heist
2019-01-05 11:18 ` Toke Høiland-Jørgensen
2019-01-05 11:26 ` Pete Heist
2019-01-05 11:35 ` Pete Heist
2019-01-05 12:38 ` Toke Høiland-Jørgensen
2019-01-05 12:51 ` Pete Heist
2019-01-05 13:10 ` Toke Høiland-Jørgensen
2019-01-05 13:20 ` Pete Heist
2019-01-05 13:35 ` Toke Høiland-Jørgensen
2019-01-05 15:34 ` Pete Heist [this message]
2019-01-05 15:52 ` Jonathan Morton
2019-01-05 16:32 ` Toke Høiland-Jørgensen
2019-01-05 19:27 ` Sebastian Moeller
2019-01-05 20:01 ` Pete Heist
2019-01-05 20:10 ` Toke Høiland-Jørgensen
2019-01-05 20:31 ` Pete Heist
2019-01-05 22:27 ` Toke Høiland-Jørgensen
2019-01-05 22:41 ` Pete Heist
2019-01-06 9:37 ` Pete Heist
2019-01-06 20:56 ` Toke Høiland-Jørgensen
2019-01-07 0:30 ` Pete Heist
2019-01-07 2:11 ` Dave Taht
2019-01-07 11:30 ` Toke Høiland-Jørgensen
2019-01-07 15:07 ` Pete Heist
2019-01-08 20:03 ` Pete Heist
2019-01-08 20:44 ` Dave Taht
2019-01-08 22:01 ` Pete Heist
2019-01-08 22:33 ` Dave Taht
2019-01-09 6:13 ` Pete Heist
2019-01-08 22:27 ` Toke Høiland-Jørgensen
2019-01-09 5:29 ` Pete Heist
2019-01-09 8:36 ` Toke Høiland-Jørgensen
2019-01-06 20:55 ` Toke Høiland-Jørgensen
2019-01-05 10:44 ` Jonathan Morton
2019-01-05 11:17 ` Toke Høiland-Jørgensen
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=797FCC60-0048-4EF6-80BC-19707E9173FB@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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