From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: Dave's wishlist [was: Source-specific routing merged]
Date: Tue, 17 Mar 2015 12:30:37 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1503171226110.23490@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw704gfXgR-viEgD_EuQL7hXoUBqWVyLp3isooZpJ590Hw@mail.gmail.com>
On Tue, 17 Mar 2015, Dave Taht wrote:
> My quest is always for an extra "9" of reliability. Anyplace where you can
> make something more robust (even if it is out at the .9999999999) level, I
> tend to like to do in order to have the highest MTBF possible in
> combination with all the other moving parts on the spacecraft (spaceship
> earth).
There are different ways to add reliability
one is to try and make sure nothing ever fails
the second is to have a way of recovering when things go wrong.
Bufferbloat came about because people got trapped into the first mode of
thinking (packets should never get lost), when the right answer ended up being
to realize that we have a recovery method and use it.
Sometimes trying to make sure nothing ever fails adds a lot of complexity to the
code to handle all the corner cases, and the overall reliability will improve by
instead simplify normal flow, even if it add a small number of failures, if that
means that you can have a common set of recovery code that's well excercised and
tested.
As you are talking about loosing packets with route changes, watch out that you
don't fall into this trap.
David Lang
next prev parent reply other threads:[~2015-03-17 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7i1tkozwf2.wl-jch@pps.univ-paris-diderot.fr>
[not found] ` <CAA93jw7bQHsFe7Jwf8o9QhM31Y0JnZPP9AaxMnm+t_ZC2eq8Vg@mail.gmail.com>
[not found] ` <87pp87x2yp.wl-jch@pps.univ-paris-diderot.fr>
[not found] ` <CAA93jw4UmOGz1+obnpw6Hkyakxd5Yi6TpZ0_6E+t7YcYqxd5BQ@mail.gmail.com>
2015-03-17 14:52 ` Dave Taht
2015-03-17 19:30 ` David Lang [this message]
2015-03-17 20:38 ` dpreed
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=alpine.DEB.2.02.1503171226110.23490@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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