From: Sebastian Moeller <moeller0@gmx.de>
To: Y <intruder_tkyf@yahoo.fr>
Cc: Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Stab overhead caliculation and mpu for ingress shaping. 2
Date: Wed, 1 Mar 2017 22:37:16 +0100 [thread overview]
Message-ID: <08601E69-3BF3-419E-B06C-E788D3257ACE@gmx.de> (raw)
In-Reply-To: <1488393866.15525.1.camel@yahoo.fr>
> On Mar 1, 2017, at 19:44, Y <intruder_tkyf@yahoo.fr> wrote:
>
>> oevrhead for ingress in myscript = -4.
>> Because I want to shape connection , so , must set speed setting * 48
> /53.
>
> This is wrong explaination.
> I cannot understand what is correct overhead for ingress.
Again, I would try to measure it instead of trying to divine it…
Best Regards
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2017-03-01 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 18:44 Y
2017-03-01 21:37 ` Sebastian Moeller [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08601E69-3BF3-419E-B06C-E788D3257ACE@gmx.de \
--to=moeller0@gmx.de \
--cc=Bloat@lists.bufferbloat.net \
--cc=intruder_tkyf@yahoo.fr \
/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