From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] How to test Cake on TP-Link WDR3600
Date: Sun, 26 Jul 2015 22:38:27 +0100 [thread overview]
Message-ID: <55B55353.5030104@gmail.com> (raw)
In-Reply-To: <CAJq5cE0vFCHL=Hg=Aw=cWyDqtt9CDgqXYhwsRHVb-VLDd409Hw@mail.gmail.com>
On 26/07/15 22:20, Jonathan Morton wrote:
>
> Three reasons why a stackable peeler doesn't work so well:
>
> - There is some overhead from stacking, due to passing packets up and
> down the stack.
>
> It also incurs at least one packet of unmanaged buffer.
>
> - A separate qdisc would not have the information about link bandwidth
> and active flow count that cake maintains, and uses to influence the
> peeler.
>
Sold! Not that I'm a netdev reviewer, but it's a nice explanation of
the design.
I.e. cake knows the minimum processing necessary to achieve the goal.
The rest can still be left to hardware.
And now I recall peeling came from tbf, I guess it's not that odd.
Thanks for the illumination.
Alan
> - Peeling to individual IP packets is strictly necessary when
> encapsulation overhead needs to be calculated.
>
> - Jonathan Morton
>
next prev parent reply other threads:[~2015-07-26 21:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 15:45 Alec Robertson
2015-07-25 16:27 ` Sebastian Moeller
2015-07-25 16:40 ` Alec Robertson
2015-07-25 16:49 ` Alec Robertson
2015-07-25 17:15 ` Sebastian Moeller
2015-07-25 17:38 ` Alec Robertson
2015-07-25 18:12 ` Dave Taht
2015-07-25 18:21 ` Alec Robertson
2015-07-25 18:49 ` Sebastian Moeller
2015-07-25 18:47 ` Sebastian Moeller
2015-07-25 18:57 ` Alec Robertson
2015-07-25 19:19 ` Sebastian Moeller
2015-07-25 20:58 ` Alec Robertson
2015-07-26 7:01 ` Sebastian Moeller
2015-07-26 9:11 ` Alan Jenkins
2015-07-26 12:32 ` Alec Robertson
2015-07-26 12:35 ` Jonathan Morton
2015-07-26 20:09 ` Alec Robertson
2015-07-26 21:05 ` Alan Jenkins
2015-07-26 21:20 ` Jonathan Morton
2015-07-26 21:38 ` Alan Jenkins [this message]
2015-07-27 7:17 ` Sebastian Moeller
2015-08-02 19:04 ` Benjamin Cronce
2015-08-02 20:07 ` Dave Taht
2015-07-27 7:13 ` Sebastian Moeller
2015-07-27 7:10 ` 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=55B55353.5030104@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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