Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] uplink_buffer_adjustment
Date: Tue, 25 Feb 2014 15:05:42 +0100	[thread overview]
Message-ID: <CAMZR1YDj1agLvJfsj8bAvuzxr1NRhsWh5C7Q+S+DryhxLEwTDg@mail.gmail.com> (raw)
In-Reply-To: <247B6C2F-1A7E-41F8-9E59-04419060E702@gmx.de>

On Tue, Feb 25, 2014 at 1:08 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>         TL:DR version, netalyzr probes a buffer depth that while existing has not much relevance on the latency behavior under load for cerowrt.
Yes, it doesn't have much relevance for latency where fq_codel or
similar are employed.
But where it's not (or where fq_codel is defeated by DOS style
traffic), it seems this comes back as a meaningful metric. In the end
codel is workaround for overbuffering, which is not being removed very
hastily.

Best regards,
Maciej

  reply	other threads:[~2014-02-25 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 11:14 Oliver Niesner
2014-02-25 12:08 ` Sebastian Moeller
2014-02-25 14:05   ` Maciej Soltysiak [this message]
2014-02-25 14:19     ` Sebastian Moeller
2014-02-25 15:59 ` Jim Gettys
     [not found]   ` <D82FF87B-F220-45B4-AA87-27037DB472C9@icsi.berkeley.edu>
2014-02-25 16:46     ` Jim Gettys
2014-02-25 21:27       ` dpreed
2014-02-25 17:10   ` Dave Taht

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=CAMZR1YDj1agLvJfsj8bAvuzxr1NRhsWh5C7Q+S+DryhxLEwTDg@mail.gmail.com \
    --to=maciej@soltysiak.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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