From: John Yates <john@yates-sheets.org>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Richard Smith <smithbone@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Linksys wrt1900acs rrul traces
Date: Fri, 8 Apr 2016 09:55:21 -0400 [thread overview]
Message-ID: <CAJnXXohuBkmtjEy8210hLXK4c4D4DD0x=o6c6fEjU9jnizbH_Q@mail.gmail.com> (raw)
In-Reply-To: <66A42333-0801-45AF-B67E-B7CFAF22FE43@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Sebastian,
Recently you wrote:
In your case select Ethernet with overhead, and manually put 24 into these
> packet overhead field, as the kernel already accounted for 14 of the total
> of 38.
>
and further down:
> I assume in your case this will not change your results a lot, as you most
> likely used full MTU packets in the test flows, I believe your low latency
> under load increases show that you have not much buffer bloat left... I
> would still recommend to use the correct per packet overhead to be on the
> right side...
>
As a layman hoping to use some of this great technology on my forth coming
Omni Turris boxes how am I supposed to derive these numbers? Is there a
simple series of questions and answers that could figure them out? Could
those be turned into some kind of "wizard"? Otherwise how do you expect
large numbers of users to get their systems properly configured? Surely
you do not want to engage in an email thread with each user who even
attempts such configuration :-)
/john
[-- Attachment #2: Type: text/html, Size: 1466 bytes --]
next prev parent reply other threads:[~2016-04-08 13:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:58 Richard Smith
2016-04-07 15:24 ` Dave Taht
2016-04-08 11:51 ` Richard Smith
2016-04-07 16:16 ` moeller0
2016-04-07 16:40 ` Dave Taht
2016-04-08 11:51 ` Richard Smith
2016-04-08 13:17 ` Sebastian Moeller
2016-04-08 13:55 ` John Yates [this message]
2016-04-08 19:20 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces ko Sebastian Moeller
2016-04-07 17:42 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces Aaron Wood
2016-04-07 17:48 ` Dave Taht
2016-04-07 17:50 ` moeller0
2016-04-07 18:05 ` Dave Taht
2016-04-07 20:36 ` Aaron Wood
2016-04-08 11:51 ` Richard Smith
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJnXXohuBkmtjEy8210hLXK4c4D4DD0x=o6c6fEjU9jnizbH_Q@mail.gmail.com' \
--to=john@yates-sheets.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=smithbone@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