From: Dennis Fedtke <dennisfedtke@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] overhead and mpu
Date: Tue, 5 Sep 2017 08:00:04 +0200 [thread overview]
Message-ID: <a8c755c0-4c98-d4bb-263c-0491674a5777@gmail.com> (raw)
In-Reply-To: <d8d9280a-f2db-5def-2e11-e7c69f769107@gmail.com>
Hi Ryan,
Thanks for you answers.
Lets assume again ethernet over docsis connection at 50 Mbit/s.
So to get 50 Mbit/s ethernet perfomance, the docsis link speed needs to be set at a higher link speed to compensate for the 18 header ethernet overhead, or?
or
Assuming:
The docsis link syncs at exactly 50Mbit/s. When cake is set to exactly 50Mbit/s, it is actually set at a higher speed then the link actually is.
For mpu why 64?
I assume minimum 46bytes ethernet payload + 18bytes header?
But why does cake use hard_header_len for the header size which is 14 bytes?
I don't know how packet sheduler system works, but maybe it is not needed to include the ethernet header.
cake does work on ip pakets or? so this is layer3 i think.
the hole thing with ethernet headers is happening in layer2.
This would change the minimum packet size to 46 or?
Thanks.
next prev parent reply other threads:[~2017-09-05 6:00 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 [this message]
2017-09-05 6:49 ` Ryan Mounce
2017-09-05 6:58 ` Jonathan Morton
2017-09-05 20:19 ` Dennis Fedtke
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=a8c755c0-4c98-d4bb-263c-0491674a5777@gmail.com \
--to=dennisfedtke@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