From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Lockup at high speeds
Date: Fri, 01 Jun 2018 19:53:57 +0200 [thread overview]
Message-ID: <87k1ri9yve.fsf@toke.dk> (raw)
In-Reply-To: <C6871EDD-5176-4338-891F-7A11D81F0C49@gmail.com>
Jonathan Morton <chromatix99@gmail.com> writes:
>> On 1 Jun, 2018, at 8:46 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> As you may have seen, I hit a lockup bug when testing Cake at high
>> speeds. I am not quite sure what is happening, but we seem to be looping
>> forever either in cake_dequeue() or cake_enqueue(), causing deadlocks.
>>
>> Unfortunately, I have no more time to debug this for now. As far as I
>> can tell, it only seems to be happening as the shaped rate approaches or
>> exceeds the link speed, or when running in unlimited mode. So for all I
>> know it might be possible to trigger it at lower speeds as well...
>>
>> Anyone with any bright ideas?
>
> Is there a complete copy of the code somewhere I can look at it? I'm
> still running the cobalt branch.
I've been trying to keep everything in sync. The upstream-4.18 branch is
identical to what I've been submitting; the only thing missing from the
cobalt branch should be the classification stuff.
The tests I just did where I saw the lockup was the current cobalt
branch.
-Toke
next prev parent reply other threads:[~2018-06-01 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 17:46 Toke Høiland-Jørgensen
2018-06-01 17:49 ` Jonathan Morton
2018-06-01 17:53 ` Toke Høiland-Jørgensen [this message]
2018-06-01 19:03 ` Georgios Amanakis
2018-06-01 19:23 ` Toke Høiland-Jørgensen
[not found] ` <9A273CA6-FDF6-485D-B466-8B01D4573BD9@gmail.com>
2018-06-01 19:58 ` Toke Høiland-Jørgensen
2018-06-02 17:08 ` Dave Taht
2018-06-02 18:21 ` Toke Høiland-Jørgensen
2018-06-02 18:55 ` Dave Taht
2018-06-02 19:25 ` Toke Høiland-Jørgensen
2018-06-03 14:56 ` Georgios Amanakis
2018-06-03 23:26 ` Toke Høiland-Jørgensen
2018-06-05 11:46 ` Pete Heist
2018-06-05 14:24 ` Pete Heist
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=87k1ri9yve.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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