Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "R." <redag2@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Ideas on how to simplify and popularize bufferbloat control for consideration.
Date: Fri, 25 Jul 2014 14:37:34 -0400	[thread overview]
Message-ID: <13144.1406313454@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 24 May 2014 10:02:53 -0400." <CACj-SW2xRzNJa_c7CyOGzY-Yvun7UjNyp0W0aeF5DjO_Guu=ag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]

On Sat, 24 May 2014 10:02:53 -0400, "R." said:

> Further, this function could be auto-scheduled or made enabled on
> router boot up.

Yeah, if such a thing worked, it would be good.

(Note in the following that a big part of my *JOB* is doing "What could
possibly go wrong?" analysis on mission-critical systems, which tends to color
my viewpoint on projects. I still think the basic concept is good, just
difficult to do, and am listing the obvious challenges for anybody brave
enough to tackle it... :)

> I must be missing something important which prevents this. What is it?

There's a few biggies.  The first is what the linux-kernel calls -ENOPATCH -
nobody's written the code.  The second is you need an upstream target someplace
to test against.  You need to deal with both the "server is unavalailable due
to a backhoe incident 2 time zones away" problem (which isn't *that* hard, just
default to Something Not Obviously Bad(TM), and "server is slashdotted" (whci
is a bit harder to deal with.  Remember that there's some really odd corner
cases to worry about - for instance, if there's a power failure in a town, then
when the electric company restores power you're going to have every cerowrt box
hit the server within a few seconds - all over the same uplink most likely.  No
good data can result from that... (Holy crap, it's been almost 3 decades since
I first saw a Sun 3/280 server tank because 12 Sun 3/50s all rebooted over the
network at once when building power was restored).

And if you're in Izbekistan and the closest server netwise is at 60 Hudson, the
analysis to compute the correct values becomes.... interesting.

Dealing with non-obvious error conditions is also a challenge - a router
may only boot once every few months.  And if you happen to be booting just
as a BGP routing flap is causing your traffic to take a vastly suboptimal
path, you may end up encoding a vastly inaccurate setting and have it stuck
there, causing suckage for non-obvious reasons for the non-technical, so you
really don't want to enable auto-tuning unless you also have a good plan for
auto-*RE*tuning....




[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-07-25 18:37 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 14:03 R.
2014-07-25 18:37 ` Valdis.Kletnieks [this message]
2014-07-25 21:03   ` David Lang
2014-07-26 11:30     ` Sebastian Moeller
2014-07-26 20:39       ` David Lang
2014-07-26 21:25         ` Sebastian Moeller
2014-07-26 21:45           ` David Lang
2014-07-26 22:24             ` David Lang
2014-07-27  9:50               ` Sebastian Moeller
2014-07-26 22:39             ` Sebastian Moeller
2014-07-26 22:53               ` David Lang
2014-07-26 23:39                 ` Sebastian Moeller
2014-07-27  0:49                   ` David Lang
2014-07-27 11:17                     ` Sebastian Moeller
2014-08-01  4:21       ` Michael Richardson
2014-08-01 18:28         ` Sebastian Moeller
2014-07-25 20:48 ` Wes Felter
2014-07-25 20:57   ` David Lang
2014-07-26 11:18     ` Sebastian Moeller
2014-07-26 20:21       ` David Lang
2014-07-26 20:54         ` Sebastian Moeller
2014-07-26 21:14           ` David Lang
2014-07-26 21:48             ` Sebastian Moeller
2014-07-26 22:23               ` David Lang
2014-07-26 23:08                 ` Sebastian Moeller
2014-07-27  1:04                   ` David Lang
2014-07-27 11:38                     ` Sebastian Moeller
2014-08-01  4:51                       ` Michael Richardson
2014-08-01 18:04                         ` Sebastian Moeller
2014-08-02 20:17                           ` Michael Richardson
2014-08-01  4:40       ` Michael Richardson
2014-07-26 11:01   ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2014-05-24 14:12 R.
2014-05-24 17:31 ` Sebastian Moeller
2014-05-24 19:05 ` David P. Reed
2014-05-20 22:11 Frits Riep
2014-05-20 23:14 ` Dave Taht
2014-05-21 11:42   ` Frits Riep
2014-05-21 14:51     ` dpreed
2014-05-21 15:19       ` Dave Taht
2014-05-21 16:03         ` dpreed
2014-05-21 16:30           ` Dave Taht
2014-05-21 17:55             ` dpreed
2014-05-21 17:47           ` Jim Gettys
2014-05-21 17:53             ` Dave Taht
2014-05-21 17:56               ` dpreed
2014-05-21 17:57                 ` Jim Gettys
2014-05-21 18:31                   ` Dave Taht
2014-05-21 15:07     ` Dave Taht
2014-05-21 16:50       ` Michael Richardson
2014-05-21 17:58       ` David Lang

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=13144.1406313454@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=redag2@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