From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] is there a patch for tc-adv somewhere for showing active_flows
Date: Tue, 29 Sep 2015 14:06:40 +0100 [thread overview]
Message-ID: <560A8CE0.7040503@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw4xUBVMBc6-u8LCuooVRibyZ_s7DQLwzaHDzNjRAk+UnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On 29/09/15 12:12, Dave Taht wrote:
> I seem to recall one... and also doing up
> a patch to cake that shipped it
>
> don't see it...
>
> boy it has been a while
>
Are you thinking of Toke's iproute2 repo?
http://kau.toke.dk/git/cake/iproute2/ - There's something there which
adds cake stats and I think is the real source of the pull request I
recently sent you.
Your tc-adv repo never got those updates and since openwrt references
the cerowrt-packages repo which then reference your cake, pie & tc-adv
repos neither did it.
The situation is I think best described as lacking clarity. Certainly
I've found it confusing and ended up maintaining my own branch of
cerowrt-packages, and in some cases (eg tc-adv sparse/bulk/active flows)
generated quilt style patches for my local openwrt build.
Ideally I'd have offered this to all here, the closest I got was a quick
write-up of some build instructions. I do know how time consuming this
can become.
As a 'for example' the recent changes to cake & tc-adv should also
result in cerowrt-packages having the git SHA ref updated in the package
Makefiles. That way at least cerowrt-package subscribers get to test
the bleeding edge code :-)
I've no idea how this then gets into upstream openwrt. I'm willing to
try and maintain as long as I get some support, otherwise I'm going to
find myself doing a lot of guessing again which is exhausting.
Happy to receive private emails :-)
Kevin (onboard train dodgy wifi)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-09-29 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 11:12 Dave Taht
2015-09-29 13:06 ` Kevin Darbyshire-Bryant [this message]
2015-09-29 13:15 ` Toke Høiland-Jørgensen
2015-09-29 13:24 ` Dave Taht
2015-09-29 13:27 ` Toke Høiland-Jørgensen
2015-09-29 14:22 ` Sebastian Moeller
2015-09-29 14:26 ` Dave Taht
2015-09-29 15:22 ` Jonathan Morton
2015-09-30 9:55 ` Kevin Darbyshire-Bryant
2015-09-30 10:06 ` Dave Taht
2015-09-30 11:27 ` Sebastian Moeller
2015-09-30 11:28 ` Dave Taht
2015-10-01 12:00 ` Kevin Darbyshire-Bryant
2015-10-01 13:31 ` Dave Taht
2015-10-01 14:17 ` Kevin Darbyshire-Bryant
2015-10-03 13:43 ` Dave Taht
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=560A8CE0.7040503@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