From: Jonathan Morton <chromatix99@gmail.com>
To: LeetMniWheat <leetminiwheat@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] sch_cake broken on 4.4.11 and 4.5.5?
Date: Fri, 20 May 2016 12:46:48 +0300 [thread overview]
Message-ID: <DAE9C868-5B81-4B90-A090-8E92B528EBB5@gmail.com> (raw)
In-Reply-To: <CAHesu+syoy4absZCqD0Hn2832huPRtm3QEXsySow+r19c6MO5w@mail.gmail.com>
> On 19 May, 2016, at 13:44, LeetMniWheat <leetminiwheat@gmail.com> wrote:
>
> I must also point out that my own issues could be a platform-specific for
> x86/Debian, though chromi@github had commented previously that the current code
> is unstable with diffserv turned on so I am unsure if this is related but I
> have not been able to reproduce the stack traces after removing sch_cake.
There was a bugfix for this applied quite early on. Please ensure that you’re running the latest version.
- Jonathan Morton
next prev parent reply other threads:[~2016-05-20 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 10:44 LeetMniWheat
2016-05-20 9:18 ` Jonathan Morton
2016-05-20 9:46 ` Jonathan Morton [this message]
2016-05-20 12:39 ` Jonathan Morton
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=DAE9C868-5B81-4B90-A090-8E92B528EBB5@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=leetminiwheat@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