From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] making peeling more aggressive?
Date: Fri, 14 Aug 2015 07:22:59 -0700 [thread overview]
Message-ID: <CAA93jw7v+EsaBHKEAFA=mELqGeV_Cknbib78iYOgvL9WH3Gt_A@mail.gmail.com> (raw)
I have been running this in production.
http://snapon.lab.bufferbloat.net/~d/0001-make-peeling-more-aggressive.patch
It is hard to discern differences between these two variants, but I am
a big believer in trying to get the peeling threshold down below what
can be effectively scheduled by the cpu, which is less than 250us on
many platforms.
Also for those trying to make this work on current kernels, a quick
and dirty patch to get it basically running is below. If someone can
grok the new kernel hashing API enough to make it usable for cake, I'd
love it.
On Fri, Aug 14, 2015 at 7:16 AM, Dave Taht <dave.taht@gmail.com> wrote:
> damn me, I did this patch back in early june.
>
> http://snapon.lab.bufferbloat.net/~d/0001-hacked-to-more-or-less-support-netnext-4.2-change-in.patch
>
> On Fri, Aug 14, 2015 at 7:09 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Dave Taht <dave.taht@gmail.com> writes:
>>
>>> want a patch
>>> I guess you
>>
>> Yes, please :)
>>
>> -Toke
>
>
>
> --
> 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
--
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
reply other threads:[~2015-08-14 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw7v+EsaBHKEAFA=mELqGeV_Cknbib78iYOgvL9WH3Gt_A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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