From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] is there a patch for tc-adv somewhere for showing active_flows
Date: Wed, 30 Sep 2015 04:28:55 -0700 [thread overview]
Message-ID: <CAA93jw67BkoKTyAf1ASffC8PkOdB6XNbB4wCw=BPe_2jFXSuJQ@mail.gmail.com> (raw)
In-Reply-To: <55822F58-63E5-4A5F-8B89-77D22F46C2D0@gmx.de>
at the moment it seems best to keep working these out of tree versions, imho.
On Wed, Sep 30, 2015 at 4:27 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Jonathan,
>
> is Tokes repository the next best to master, or will all eventually accumulate in Dave’s repository? I just wonder which iproute2 to actually build on my test machine ;)
>
> Best Regards
> Sebastian
>
> On Sep 30, 2015, at 11:55 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>> Dave,
>>
>> I've pulled the commits from Toke's iproute2 repo in which Jonathan is
>> placing his stats & other tweaks and sent you a pull request:
>> https://github.com/dtaht/tc-adv/pull/3 to get them into your tc-adv repo
>> (which is slightly more cero/openwrt facing)
>>
>> All the recent changes to cake & tc are running here.... livin' on the
>> bleeding edge :-)
>>
>> Kevin
>>
>>
>>
>> On 29/09/15 16:22, Jonathan Morton wrote:
>>>
>>> The big api change is in the stats output, which I'm still working
>>> on. As a stop gap, I have already pushed a version with both sparse
>>> and bulk flows reporting.
>>>
>>> The config api is inherently extensible.
>>>
>>> - Jonathan Morton
>>>
>>>
>>>
>>> _______________________________________________
>>> Cake mailing list
>>> Cake@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cake
>>
>>
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Dave Täht
Do you want faster, better, wifi? https://www.patreon.com/dtaht
next prev parent reply other threads:[~2015-09-30 11:28 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
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 [this message]
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='CAA93jw67BkoKTyAf1ASffC8PkOdB6XNbB4wCw=BPe_2jFXSuJQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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