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: Tue, 29 Sep 2015 15:41:25 +0200 [thread overview]
Message-ID: <1B94E21B-A04D-48D1-83FB-5DE1D747F5B3@gmx.de> (raw)
In-Reply-To: <CAA93jw7Os9GN6TxvfzrmXidS3Qx_47NDFMb0rbYPy4JAc51u9g@mail.gmail.com>
Hi Dave,
revisiting your old plan:
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)
Done, as of 444f9e5c0fde1400f21175eacfa7ced60b410e49 ?
> ** Fix diffserv
What needs fixing there?
> ** Add man page
> ** Clean up patches to only do cake
Was that fq_pie only? Then done as of dca3df3490470af6b134b7015559d9416f3a7616 ?
> *** Reformat for kernel_style
> *** IProute patches for mainline iproute
I thought this requires sch_cake to be upstream already?
> ** 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
Isn’t that diner as well, as of f3289fe8ae2a28640616bf3f3289fe8ae2a2864061 ?
> ** 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
I would still like maxpacket per bin just as fq_codel does, this is really really helpful to figure out how much overhead accounting the kernel adds by itself.
Let me expand: the kernel does not simply give the payload size of a packet but, depending on the interface type in use, adds for example 14 byte “virtual size” for ethernet. But it is not well documented how much is added for which interface type, if a diffserv capable qdisc emits the packet sizes it is pretty easy to test what the kernel does, by simply sending an know sized packet on the relevant interface and ask the qdisc how large that packet was (rem how many bits were accounted). It also is helpful in figuring out whether GRO/GSO and friends are in use…
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
prev parent reply other threads:[~2015-09-29 13:41 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
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 [this message]
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=1B94E21B-A04D-48D1-83FB-5DE1D747F5B3@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