General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Holland, Jake" <jholland@akamai.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dave Taht <dave@taht.net>, Pete Heist <pete@heistp.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] one benefit of turning off shaping + fq_codel
Date: Tue, 27 Nov 2018 19:11:00 +0000	[thread overview]
Message-ID: <5714B373-6809-440D-92DE-721D4F7DE3C7@akamai.com> (raw)
In-Reply-To: <20181127103114.3f403d8a@xeon-e3>

On 2018-11-27, 10:31, "Stephen Hemminger" <stephen@networkplumber.org> wrote:
    With asynchronous circuits there is too much unpredictablity and instability.
    Seem to remember there are even cases where two inputs arrive at once and output is non-determistic.
    
IIRC they talked about that some too. I think maybe some papers were going back and forth. But last I heard, they proved that this is not a real objection, in that:
1. you can quantify the probability of failure and ensure a design keeps it under threshold when operating within specified conditions (e.g. normal temperature and voltage thresholds)
2. you can work around the issues where it's critical by adding failure detection and faults, and
3. you have the exact same fundamental theoretical problem with synchronous circuits, particularly in registers that can keep a value through a clock cycle, but it hasn't stopped them from being useful.

I'm not an expert and this was all a long time ago for me, but  the qdi wiki page doesn't disagree with what I'm remembering here, and has some good references on the topic:
https://en.wikipedia.org/wiki/Quasi-delay-insensitive_circuit#Stability_and_non-interference
https://en.wikipedia.org/wiki/Quasi-delay-insensitive_circuit#Timing



      parent reply	other threads:[~2018-11-27 19:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 16:54 Dave Taht
2018-11-14 17:09 ` Mikael Abrahamsson
2018-11-15  0:56   ` David Lang
2018-11-15  3:44     ` Dave Taht
2018-11-23 11:47 ` Pete Heist
2018-11-23 16:26   ` Dave Taht
2018-11-23 16:43     ` Jonathan Morton
2018-11-23 16:48       ` Dave Taht
2018-11-23 17:16         ` Luca Muscariello
2018-11-23 17:27           ` Dave Taht
2018-11-23 17:32             ` Luca Muscariello
2018-11-25 21:14               ` Toke Høiland-Jørgensen
2018-11-26 12:52                 ` Pete Heist
2018-11-26 12:54                   ` Dave Taht
2018-11-26 13:30                     ` Toke Høiland-Jørgensen
2018-11-26 13:26                   ` Toke Høiland-Jørgensen
2018-11-24 11:49     ` Pete Heist
2018-12-05  0:25       ` David Lang
2018-11-27 18:14     ` Holland, Jake
2018-11-27 18:31       ` Stephen Hemminger
2018-11-27 19:09         ` Dave Taht
2018-11-27 22:07           ` Pete Heist
2018-11-27 22:33             ` Jonathan Morton
2018-11-27 22:36               ` Jonathan Morton
2018-11-28  7:23                 ` [Bloat] hardware diversions Dave Taht
2018-11-27 19:11         ` Holland, Jake [this message]

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5714B373-6809-440D-92DE-721D4F7DE3C7@akamai.com \
    --to=jholland@akamai.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=pete@heistp.net \
    --cc=stephen@networkplumber.org \
    /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