From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] lockup with cake and veth
Date: Fri, 6 Jul 2018 15:37:24 +0200 [thread overview]
Message-ID: <1CFA01E7-2B3C-42C7-B102-3D0516EDCE43@heistp.net> (raw)
In-Reply-To: <87y3eoa3wn.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
> On Jul 6, 2018, at 3:29 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Thanks for investigating! I'll take a look later. The fact that it
> happens with sfq as well means it's probably not cake-specific, though,
> so I don't think we should hold off on the upstream submission until
> we've figured it out. Using leaf qdiscs with netem has been dodgy for a
> while IIRC...
Yeah, I’m seeing now that the lockup does _not_ occur when netem is not used and cake is the root.
I’m also satisfied for now that this shouldn’t hold us up. However, what I’ll also want to try next is netem on a separate veth device from cake. I believe Dave’s veth testing earlier was using three namespaces / veth devices, maybe for this reason(?)
Nice work Jon on the lockup bug also- it’s nice seeing this come together… :)
Pete
[-- Attachment #2: Type: text/html, Size: 5020 bytes --]
next prev parent reply other threads:[~2018-07-06 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 13:17 Pete Heist
2018-07-06 13:29 ` Toke Høiland-Jørgensen
2018-07-06 13:34 ` Georgios Amanakis
2018-07-06 13:37 ` Pete Heist [this message]
2018-07-06 19:24 ` Pete Heist
2018-07-06 19:40 ` Dave Taht
2018-07-06 22:12 ` 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=1CFA01E7-2B3C-42C7-B102-3D0516EDCE43@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