From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net, Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cake] cake work needed for openwrt merge
Date: Mon, 7 Sep 2015 09:35:55 +0200 [thread overview]
Message-ID: <71816189-BFBB-4E6D-AE82-1B6B2EE67A89@gmx.de> (raw)
In-Reply-To: <CAA93jw7Os9GN6TxvfzrmXidS3Qx_47NDFMb0rbYPy4JAc51u9g@mail.gmail.com>
Hi Dave hi List,
not that I have contributed to cake at all...
On Sep 7, 2015, at 00:35 , Dave Taht <dave.taht@gmail.com> wrote:
> In discussing with felix what is needed for cake to go into openwrt
> trunk, we came up with the following list:
>
> * Cake work needed
> ** Add squash option (besteffort + squashing diffserv)
I believe this should be two independent options, best effort already exists, so it is really a "re-mapp all DSCPs to 0” option that would be great to have (this would allow a simple.qos equivalent without needing iptables)
> ** Fix diffserv
What is broken in cake’s diffserv, that is not already broken under-specified in the diffserv RFC?
> ** Add man page
> ** Clean up patches to only do cake
What are the current patches do that falls outside of cake itself?
> *** Reformat for kernel_style
> *** IProute patches for mainline iproute
In preparation for an upstream merge?
> ** Submit as a single patch to openwrt for each
> ** cake patches goes into the openwrt iproute directly
> ** continues to be built externally as kmod-sched-cake
> ** Needs update to the new kernel hashing api
> ** Openwrt is stablizing for now, on linux 4.1
> ** CC is essentially done, but there will a CC.1 release at some point
> ** Add better statistics (like active_flows) - have part of this already
What is the ETA, I still want to add a maxpacket statistic to the outputs, and want to know how much time I have. Getting maxpackets is quite helpful for dealing with different encapsulations (especially in figuring out which headers the kernel does or does not add automatically).
Best Regards
Sebastian
>
>
> --
> Dave Täht
> endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2015-09-07 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 22:35 Dave Taht
2015-09-07 7:35 ` Sebastian Moeller [this message]
2015-09-07 10:45 ` Dave Taht
2015-09-07 11:21 ` Sebastian Moeller
2015-09-07 19:43 ` Benjamin Cronce
2015-09-07 20:35 ` Sebastian Moeller
2015-09-07 20:37 ` Dave Taht
2015-09-07 22:31 ` Benjamin Cronce
2015-09-07 22:44 ` Jonathan Morton
2015-09-08 7:20 ` Sebastian Moeller
2015-09-09 23:54 ` Benjamin Cronce
2015-09-29 13:41 ` Sebastian Moeller
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=71816189-BFBB-4E6D-AE82-1B6B2EE67A89@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
/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