Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: cake@lists.bufferbloat.net
Subject: [Cake] Peeling question
Date: Wed, 26 Aug 2015 16:52:14 +0200	[thread overview]
Message-ID: <E8B8D732-3EFC-486D-BC8F-C69D0FB776F6@gmx.de> (raw)

Hi Jonathan, hi Dave,

I have just been discussing GRO/LRO/TSO/GSO type meta packets (for lack of a better name) and their influence on temporal traffic shaping granularity (and fine timescale fairness). I know that cake solves this problem the most elegant way by peeling/decomposing the meta packets into nice pMTU sized chunks, but until cake hits openwrt or mainline we need to get away with bigger hammers, namely disabling meta-packets entirely. I believe that they need to be disabled on all interfaces to be effective as say a meta-packets assembled on say a WLAN-interface with GRO enabled will e passed onto WAN even if the WAN-interface has GSO disabled, is that correct? 
	So the 1. question boils down to on which interfaces the offloads need to be disabled, on all interfaces or only on “real” interfaces? Or more specifically with cerowrt nomenclature: will ge00 be sufficient or do I also disable it in pppoe-ge00 and ifb4pppoe-ge00? By default GSO and GRO are enabled on those interfaces?
	My second question is how do you guys actually test this? How can I create a situation with a very high likelihood of meta-packets appearing? (If I know this I can go figure question 1 myself…)

On a related note it would be sweet if cake could report the maximal sizes of packets it gets fed in and the maximum sizes it ejects; so for non-peeled meta-packets I expect to see say in: 64K out: 64K and for peeled rather in: 64K out: 1514 or so.

Best Regards
	Sebastian
	


             reply	other threads:[~2015-08-26 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 14:52 Sebastian Moeller [this message]
2015-08-27  5:25 ` Jonathan Morton

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=E8B8D732-3EFC-486D-BC8F-C69D0FB776F6@gmx.de \
    --to=moeller0@gmx.de \
    --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