From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Update kernel version check in cake
Date: Tue, 29 Sep 2015 17:10:14 +0200 [thread overview]
Message-ID: <FBB40428-1FB2-4EF8-86D5-C693FB76DFB1@gmx.de> (raw)
In-Reply-To: <CAA93jw61tZg7cp-Fh=kExe=OCVXN_TSOnF1r4zAvSo=7Os+dVA@mail.gmail.com>
Hi Dave,
On Sep 29, 2015, at 13:10 , Dave Taht <dave.taht@gmail.com> wrote:
> I added support for squashing to both sch_cake and tc-adv repos. Sort
> of compile tested
> only. (my laptop's kernel is 3.16 and doesn't build, my virtuals in
> linode do not come with
> kernel sources, snapon crashed two weeks ago, and so on)
>
Just played a bit with the shiny new squash option. For my limited testing it seems to work. I do wonder whether the automatic default to besteffort is the ideal behavior though. For example on egress it would be nice to be able to use the internal set DSCP markings but clean them from the outgoing packets as not to leak “information” to the ISP, similarly but more contrived the same could be agued for ingress ;)
Best Regards
> but it was nice to write a few lines of code, knowing that someone
> here will fix 'em if
> I broke something.
>
>
> On Tue, Sep 29, 2015 at 2:55 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> On Tue, Sep 29, 2015 at 2:42 AM, Kevin Darbyshire-Bryant
>> <kevin@darbyshire-bryant.me.uk> wrote:
>>>
>>>
>>> On 29/09/15 00:01, Jonathan Morton wrote:
>>>>
>>>> I actually had the version check fix locally, but for some reason it
>>>> hadn't been picked up by a push yet.
>>>>
>>> Yep, I have those moments. Just when I think I've got git sussed it
>>> goes and does something completely logical but totally unexpected :-)
>>>>
>>>> Squashing would involve writing to the TOS byte, which is already done
>>>> by ECN marking, via a helper function.
>>>>
>>> Ah, so if I can work out how that's done I'm 50% of the way there.
>>> Should keep me amused for a few days.
>>>>
>>>> I tried removing the cow stuff once before. Everything promptly
>>>> stopped working until I put it back. I have no idea why.
>>>>
>>> Well here's interesting. I got brave and put my suggested change into
>>> action. So far: 1) router not blown up 2) tc -s still shows traffic in
>>> different Classes (Dave, I prefer your term 'Bin' here too - I
>>> considered 'Bucket' for a laugh) which suggests the reading of ip_hdr is
>>> still working. 3) This hasn't been thoroughly tested in any way
>>> whatsoever but i've tried diffserv4 & besteffort and both don't appear
>>> broken.
>>
>> I agree with bin. Wouldn't mind it if that made it into the variable
>> name instead of class.
>>
>>> Pull request: https://github.com/dtaht/sch_cake/pull/6
>>
>> It would be my hope also that killing the cow would speed it up.
>>
>> Untested by me, but pulled.
>>
>>
>>> Kevin
>>>>
>>>> - Jonathan Morton
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Dave Täht
>> Do you want faster, better, wifi? https://www.patreon.com/dtaht
>
>
>
> --
> Dave Täht
> Do you want faster, better, wifi? https://www.patreon.com/dtaht
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
prev parent reply other threads:[~2015-09-29 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 11:52 Kevin Darbyshire-Bryant
2015-09-28 12:09 ` Dave Taht
2015-09-28 16:25 ` Kevin Darbyshire-Bryant
2015-09-28 23:01 ` Jonathan Morton
2015-09-29 9:42 ` Kevin Darbyshire-Bryant
2015-09-29 9:55 ` Dave Taht
2015-09-29 11:10 ` Dave Taht
2015-09-29 15:10 ` Sebastian Moeller [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/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=FBB40428-1FB2-4EF8-86D5-C693FB76DFB1@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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