From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Announce - possible new feature - DSCP cleaning
Date: Mon, 16 Nov 2015 17:47:09 +0000 [thread overview]
Message-ID: <564A169D.1060307@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw4T_C+FNnhEXm4Ke7A9L0GLybOU5RtaBX6vfM+SjgHF6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Does this
https://github.com/dtaht/sch_cake/commit/d05cf7e003d9c13d8382c881655807bda7ab3616
improve your happiness factor?
Kevin
On 16/11/15 15:57, Dave Taht wrote:
> isn't there some other boolean variable somewhere ?
>
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> https://www.gofundme.com/savewifi
>
>
> On Mon, Nov 16, 2015 at 4:20 PM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
>>
>> On 16/11/15 15:03, Dave Taht wrote:
>>> I have not been doing any active development until... tomorrow.
>>>
>>> A goal I have for today is to actually build a version of openwrt +
>>> all this stuff for the linksys ac1200.
>>>
>>> I was not particularly huge on using another field (q->squash) to
>>> trigger squashing, and I cannot come up with a use case that makes
>>> sense to me.
>>>
>>> Under what circumstances do you think separating these two functions
>>> to be useful?
>> I wanted to be able to use diffserv marking for internal bandwidth
>> policing purposes whilst clearing those bits by the time they hit the
>> ISP. On ingress it makes no sense, on egress I can see a use.
>>
>>
>>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-11-16 17:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 15:00 Kevin Darbyshire-Bryant
2015-11-16 14:59 ` Kevin Darbyshire-Bryant
2015-11-16 15:03 ` Dave Taht
2015-11-16 15:20 ` Kevin Darbyshire-Bryant
2015-11-16 15:57 ` Dave Taht
2015-11-16 16:25 ` Kevin Darbyshire-Bryant
2015-11-16 17:47 ` Kevin Darbyshire-Bryant [this message]
2015-11-16 17:59 ` Dave Taht
2015-11-16 18:11 ` Kevin Darbyshire-Bryant
2015-11-16 18:25 ` Dave Taht
2015-11-16 18:32 ` Sebastian Moeller
2015-11-16 18:35 ` Dave Taht
2015-11-16 18:43 ` Kevin Darbyshire-Bryant
2015-11-16 18:47 ` Dave Taht
2015-11-16 20:09 ` Kevin Darbyshire-Bryant
2015-11-17 10:12 ` Dave Taht
2015-11-17 18:52 ` Kevin Darbyshire-Bryant
2015-11-16 15:33 ` Sebastian Moeller
2015-11-17 19:05 Dave Taht
2015-11-18 11:17 ` Kevin Darbyshire-Bryant
2015-11-18 11:57 ` Toke Høiland-Jørgensen
2015-11-18 18:56 ` Kevin Darbyshire-Bryant
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=564A169D.1060307@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--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