From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] ECN marking and latest cake
Date: Sun, 18 Oct 2015 11:20:01 +0100 [thread overview]
Message-ID: <56237251.6000700@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <76A7ED19-2239-4364-877B-2FF266EC4148@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On 18/10/15 08:32, Jonathan Morton wrote:
>> On 17 Oct, 2015, at 18:45, Antoine Deschênes <antdes45@gmail.com> wrote:
>>
>> I built the latest cake yesterday night and noticed I don't see any changes between enabling and disabling ECN on Windows with this version anymore.
>>
>> (DSLreports speedtest Re-xmit avg becomes 5x lower with ECN working on the client)
> ECN marking still seems to work at this end.
>
> - Jonathan Morton
It works here too. I see far more ECN marks & drops on my egress than
ingress; gigabit to 10mbit is quite a transition that needs to be
managed. 40mbit to gigabit ingress is less of a problem *and* my ISP
(and BT's infrastructure over which it runs) has a rate limiter to help
prevent overfilling the link. As an experiment I artificially set the
ingress bandwidth to 1/4 actual and ran a few speed & other tests. ECN
marks worked a treat.
Also, in terms of Openwrt/cerowrt, the versions of cake/tc-adv have been
behind those in the source repositories of sch_cake & tc-adv. As of
approx 10:00 GMT Oct 18th 2015 (and compile/run test on Archer C7 v2) I
updated ceropackages-3.10 to point to the latest commits to those source
repositories. Those commits are
0251bc5fa32a2caff32b108e55239bf667e851c2 &
256fbf86642f7e180d507be2c0824c03536ac140 in Dave's sch_cake & tc-adv
repos respectively.
I hope that explanation in some way helps :-)
Kevin
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-10-18 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 15:45 Antoine Deschênes
2015-10-18 7:32 ` Jonathan Morton
2015-10-18 10:20 ` Kevin Darbyshire-Bryant [this message]
[not found] ` <CACBEuKAfR6z5Ak-7kA6BKd9FoRHjjh846JWV80_CeK4wdA0eVQ@mail.gmail.com>
[not found] ` <56430FF0.5050107@darbyshire-bryant.me.uk>
2015-11-12 1:32 ` Antoine Deschênes
2015-11-12 13:19 ` 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=56237251.6000700@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--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