From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net,
Alan Jenkins <alan.christopher.jenkins@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Latest build test - new sqm-scripts seem to work; "cake overhead 40" [still] didn't
Date: Sat, 20 Jun 2015 05:48:45 -0700 [thread overview]
Message-ID: <CAA93jw6=c0uHQ=rXmd4hp1sPhw8yrFUeM2uHDF_uMz5TFkPwyg@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE1Wzhcg76txR78dHv2gsV9ZvKku-PyKoX7z97M2uhxAxQ@mail.gmail.com>
huh? I pulled from the repo you were committing to, I thought.... is
that not correct?
I can do a build of a newer cake... before I get on the plane...
On Sat, Jun 20, 2015 at 5:46 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> It looks like your cake is new enough to support set associative hashing,
> but not the new overhead handling. The ATM flag was put in a long time ago.
>
> Looking at the code which grabs those options (cake_change), there doesn't
> seem to be a way to detect whether an unsupported option was provided by
> userspace, unless nla_parse_nested returns an error if the provided option
> struct would be overflowed. Clearly it doesn't, but just truncates it to
> fit.
>
> - Jonathan Morton
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
prev parent reply other threads:[~2015-06-20 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 10:55 Alan Jenkins
2015-06-20 11:00 ` Jonathan Morton
2015-06-20 11:54 ` Alan Jenkins
2015-06-20 12:46 ` Jonathan Morton
2015-06-20 12:48 ` Dave Taht [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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6=c0uHQ=rXmd4hp1sPhw8yrFUeM2uHDF_uMz5TFkPwyg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@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