Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: cake@lists.bufferbloat.net
Subject: [Cake] feature request ;)
Date: Thu, 20 Aug 2015 21:41:17 +0200	[thread overview]
Message-ID: <EAD94E9F-C14C-48F5-9756-1D6AE8793F36@gmx.de> (raw)

Hi Jonathan,

I believe we already established that cake will start out with whatever per packet overhead value the kernel already added for us (skb->pkt_len or so). Would it be possible to export the maximum of (skb->len - skb->data_len) seen over the life time of a cake instance somewhere in the statistics output? Since the kernel rules for pre-adding headers are a bit opaque this would be really helpful to select the correct per packet overhead. Say if the kernel added the ethernet header size already we do not need to use the ethernet keyword, but if it did not we should, currently the only way to figure this out is to set up an elaborate shaper and feed it with custom tailored packets and then look at the reported packet size in the qdsc statistics (if I recall correctly). It would be so much niched if cake just told us… (Case in point if I establish a shaper on eth0 the kernel helpfully adds the ethernet header, but if I use pppoe-eth0 which uses eth0 as underlayig transport the kernel does not add the ethernet header, but it MIGHT add the pppoe header size (not sure)).
	And if the max() of that field is too computationally expensive the first non-zero value would also do...


Best Regards
	Sebastian

             reply	other threads:[~2015-08-20 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 19:41 Sebastian Moeller [this message]
2015-08-20 19:50 ` Jonathan Morton
2015-08-20 19:53   ` 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=EAD94E9F-C14C-48F5-9756-1D6AE8793F36@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