From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] cake coding comments
Date: Thu, 19 Nov 2015 09:55:08 +0100 [thread overview]
Message-ID: <CAA93jw70hj05ktSVW4qeX5ofXZmnBgy4nVAakFODsuO1GXDcEg@mail.gmail.com> (raw)
I sat down to try and think outside the boxes we are in...
dropping: Dropping an 3+ packet TSO "superpacket" will cause a tcp
reset - would split and drop be possible/useful?
backports as far back as 3.2 seem to be needed.
- breaking out all the compatability cruft to a separate file
would be good
codel5.h - I've longed to clean this up to make the state machine more
clear and to fit in 80 columns for years now
- we also still use 64 bit time - which I'd intended for the
never started cake_drop monitor and also
- because 32 bit wraparound gave me a headache.
- some notes in the file about differences from this and
published codel would be good
- can't we use the skb->timestamp nowadays rather than the
control block?
hashing on the mac address seems to be possible in the new dissect
api? How? mpls?
What proof do we have that 8 way set associative hash is efficient?
Would 4 way be OK?
How correct is the dynamic quantum scaling?
What is an optimal trade-off between the total number of flows, the
size of the hash, and bandwidth?
At 1GigE? 10GigE and higher?
Autosizing the memory limit is good only when bandwidth is specified.
Does a bandwidth 100mbit exactly = ethernet at 100Mbit? Is it better than BQL?
Should we be able to increase or decrease the number of flows in the API?
Is there a way to get away from act_mirred for inbound shaping and
stick cake in there directly?
How low can we cut the interval to in a DC scenario?
VPNs vs the Tin system?
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
next reply other threads:[~2015-11-19 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 8:55 Dave Taht [this message]
2015-11-19 10:23 ` Sebastian Moeller
2015-11-19 12:20 ` Kevin Darbyshire-Bryant
2015-11-19 12:24 ` 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=CAA93jw70hj05ktSVW4qeX5ofXZmnBgy4nVAakFODsuO1GXDcEg@mail.gmail.com \
--to=dave.taht@gmail.com \
--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