Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
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 20:09:40 +0000	[thread overview]
Message-ID: <564A3804.2040306@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw5eM6zC8enmjPWRZPciS0CL1fg7o2C3C1TNU_UwaNuv9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

It is pushed but in a 'squash' branch for review purposes before it gets
merged into master.

Let me ask things in a different way, and as I've had time to think
about the implications of these changes:  By changing how 'squash' is
enabled I've currently broken backwards compatibility between 'new
squash' cake and 'old squash' tc.  Now, bearing in mind that this isn't
upstream yet...how concerned are we/should I be for 'new cake' vs 'old
tc' compatibility?  Again having thought about it more, I'm pretty sure
I can make 'new cake' and 'old tc' work....is it worth the bother?

Kevin

On 16/11/15 18:47, Dave Taht wrote:
> push it then.
> 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 7:43 PM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
>>
>> On 16/11/15 18:35, Dave Taht wrote:
>>> switch (q->tin_mode) { case CAKE_MODE_SQUASH: case
>>> CAKE_MODE_BESTEFFORT: default: cake_config_besteffort(sch); break;
>>>
>>> ?
>>> Dave Täht
>>> Let's go make home routers and wifi faster! With better software!
>>> https://www.gofundme.com/savewifi
>>>
>> Are you sure you're looking at the 'squash' branch Dave?  The 'smarts'
>> of automatically selecting 'besteffort' in the presence of 'squash' has
>> been put into 'tc'.  Thus 'squash' on its own behaves as it always did
>> for backwards compatibility.  'squash' in combination with
>> 'diffserv4/precedence' etc also works as expected.
>>
>> There's also a 'nosquash' option to disable squashing on a 'tc change'
>> if required.  That code now looks like:
>>
>>         switch (q->tin_mode) {
>>         case CAKE_MODE_BESTEFFORT:
>>         default:
>>                 cake_config_besteffort(sch);
>>                 break;
>> ........
>>
>>
>>
>>
>>
>>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

  reply	other threads:[~2015-11-16 20:09 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
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 [this message]
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=564A3804.2040306@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