Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] increasing the *codel target for DSL at really low bandwidths
Date: Fri, 20 Dec 2013 18:33:25 -0800	[thread overview]
Message-ID: <CAA93jw4NbOJEW45S4HKDOYtgz5jDz3XCow_fWDrWb-gdWTNNJA@mail.gmail.com> (raw)

I have struggled with really low bandwidths. Folk like fred have
really struggled with low bandwidths (to the point of switching to pie
on his workload, which has a 20ms target), and having got some
configuration info from maxime over free.fr (biggest ecn enabled
fq_codel'd deployment I know of), and finally having reasonable
confidence that the
htb to atm cell size compensation stuff is *fixed*...

I'd like to suggest to those with bandwidths under 5mbit try something
like this to calculate a larger target variable for *codel. (might
make sense on pie, too)

There are many significant variables at these speeds, not least of
which are fixed constants like iw10. It would not surprise me if we
needed to ramp up the curve even further below 1mbit, or double it
from what stands here. This curve is good down to almost 128kbit
before it overshoots the interval, which regardless needs to be
modified too...

suggestions? Who here runs at under a mbit on any form of technology?

#!/bin/sh
# 13000000us for 1 1500 byte packet at 1kbit.

bw_up=$1

delay=$((13500000/($bw_up)))
[ "$delay" -lt 5000 ] && delay=5000

echo target ${delay}us


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

                 reply	other threads:[~2013-12-21  2:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4NbOJEW45S4HKDOYtgz5jDz3XCow_fWDrWb-gdWTNNJA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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