From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Thanks to Toke
Date: Sat, 28 Apr 2018 08:48:17 +0000 [thread overview]
Message-ID: <684633C8-153D-46D9-9184-31F5AF4DA475@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <877eos4rl3.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
> On 27 Apr 2018, at 16:06, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Kevin Darbyshire-Bryant via Cake <cake@lists.bufferbloat.net> writes:
>
>> Thank you Toke for your continued and continuing efforts in submitting
>> CAKE to upstream kernel land. I am at least one person who greatly
>> values and appreciates your time and efforts in doing so…. and
>> wrangling the rest of us into ‘little’ tweaks here & there.
>
> Thanks, much appreciated!
>
> On that note, if someone could take a look at the changes to the ACK
> filtering I just pushed, that would be awesome (running a test with it,
> but would be good if someone else could sanity-check it).
Well I have it running based on commit 729c81a3be16cdd574935cc9de62ba1d5ce52fcf from last night with ack filtering enabled, not that my link’s 4:! up/down ratio really needs it :-)
I also unleashed my misbehaving ECN box on (qnap linux 4.2…goodness knows what bugs they’ve put in) to check nothing has dented cobalts ability to deal with unresponsive ECN flows. All is good :-)
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-28 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.323.1524837102.3573.cake@lists.bufferbloat.net>
2018-04-27 15:06 ` Toke Høiland-Jørgensen
2018-04-28 8:48 ` Kevin Darbyshire-Bryant [this message]
2018-04-28 9:59 ` Toke Høiland-Jørgensen
2018-04-28 14:04 ` 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=684633C8-153D-46D9-9184-31F5AF4DA475@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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