From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Ryan Mounce <ryan@mounce.com.au>
Cc: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Win10 Updates vs cake
Date: Fri, 22 Dec 2017 09:17:23 +0000 [thread overview]
Message-ID: <67EDDFE2-EFC6-4533-90A5-45171C426035@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAN+fvRb7Gz23QujkMG=UTC5Dwb4NnK5fYhko1aA9Hqtjd+rbAQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
> On 22 Dec 2017, at 03:57, Ryan Mounce <ryan@mounce.com.au> wrote:
>
> Some further reading on the issue
>
> https://www.mail-archive.com/nanog@nanog.org/msg87442.html
> https://forums.whirlpool.net.au/archive/2530363
>
> Regards,
> Ryan Mounce
>
Chaps,
As a result of the following conversation between Dave & myself.
>> Opinions on doing a PR for LEDE so they can enjoy(/crash) the fruits of our latest cobalt. They’re currently missing ingress mode & ack filtering filtering toys.
>
> Nah. Let's get it into net-next first this time. I would hope for some
> good comments.
LEDE master until very recently (a week) still had old versions of cake & tc. Since the upstreaming appears to have stalled on a technical issue, I took the opportunity to update LEDE master. I had submitted patches for 17.01 yesterday, after having let master ’stew’ a bit in case of problems, but subsequently pulled them this morning due to new arrivals (and discrepancies) in the cake repo.
As of this email - LEDE master has a full featured cake/cobalt but with a double overhead bug. LEDE 17.01 has a much older, pre ingress mode, pre ack filter version.
Once the cake repo is sorted out I can redo & resubmit the patches for both master & 1701 - and with a bit of luck we’ll all be in an even place again.
Cheers,
Kevin D-B
+44 7947 355344
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-22 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 2:01 Rich Brown
2017-12-22 2:55 ` Ryan Mounce
2017-12-22 3:57 ` Ryan Mounce
2017-12-22 4:03 ` Jonathan Morton
2017-12-22 5:26 ` Jonathan Morton
2017-12-29 4:49 ` Ryan Mounce
2017-12-22 9:17 ` Kevin Darbyshire-Bryant [this message]
2017-12-22 13:07 ` Rich Brown
2017-12-28 17:48 ` Benjamin Cronce
2017-12-29 4:44 ` Ryan Mounce
2017-12-22 9:12 ` Mario Hock
[not found] <mailman.56.1513933967.3659.bloat@lists.bufferbloat.net>
2017-12-22 13:13 ` Rich Brown
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67EDDFE2-EFC6-4533-90A5-45171C426035@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
--cc=ryan@mounce.com.au \
/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