Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dennis Fedtke <dennisfedtke@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] overhead and mpu
Date: Tue, 5 Sep 2017 22:19:40 +0200	[thread overview]
Message-ID: <915b0913-0ac5-c6b6-3771-752a9e41dff2@gmail.com> (raw)
In-Reply-To: <CAJq5cE0bh0Wg7tG3D-HOqyD546Nx27SWUcUrNSnk5OGhTF-HVQ@mail.gmail.com>

Hi!

Thank you for all answers.
But for me this still makes no sense.
Assuming we have an ethnernet connection running over a docsis line.
docsis is able to transmit full 1500byte ethernet packets.
Lets say it is an 50 Mbit/s Line. (I dont know now how exactly docsis works)
So to reach the 50Mbit/s ethernet speed the docsis link rate needs to be 
higher 50,6 Mbit/s (50*1518/1500 ??)
But when running a speedtest it will still not show the full speed. 
because of other overhead from underlying protocols (tcp/ip for example)
So the ISP will set the sync rate even higher to compensate for that.

But does this matter for the end user?
In case of docsis does it make sense to account for 18 overhead?
The user will enter 50mbit and it will work. If the isp has provided a 
sligher higher syncrate.

and the mpu setting. i don't know how cake handles this in detail.
How the overhead gets added.
lets i enter mpu 46.
And cake we set 18 as overhead.
Will this result in mpu 46 or 64?
Can someone debug the code maybe please? :>
I have the feeling with mpu 46 my pages lot a bit snappier. but could be 
placebo.

Thank you.





  reply	other threads:[~2017-09-05 20:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  2:46 Dennis Fedtke
2017-09-05  3:26 ` Ryan Mounce
2017-09-05  3:37   ` Ryan Mounce
2017-09-05  6:00 ` Dennis Fedtke
2017-09-05  6:49   ` Ryan Mounce
2017-09-05  6:58   ` Jonathan Morton
2017-09-05 20:19     ` Dennis Fedtke [this message]
2017-09-06  1:45       ` Ryan Mounce
2017-09-06  7:26         ` Sebastian Moeller
2017-09-07  4:11           ` Dennis Fedtke
2017-09-07  4:18             ` Dennis Fedtke
2017-09-07  4:25               ` Jonathan Morton
2017-09-07  7:41                 ` Dennis Fedtke
2017-09-07  7:58                 ` Sebastian Moeller
2017-09-07  7:47             ` Sebastian Moeller
2017-09-07  7:58               ` Dennis Fedtke
2017-09-07  8:07                 ` Sebastian Moeller
2017-09-06  7:22       ` Sebastian Moeller
2017-09-05  8:01   ` Sebastian Moeller
2017-09-05  8:35     ` Kevin Darbyshire-Bryant
2017-09-05  8:58       ` Sebastian Moeller
2017-09-05 14:37         ` Ryan Mounce
2017-09-05 15:06           ` Sebastian Moeller
2017-09-05 15:33           ` Kevin Darbyshire-Bryant

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=915b0913-0ac5-c6b6-3771-752a9e41dff2@gmail.com \
    --to=dennisfedtke@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