From: Pete Heist <pete@heistp.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] one benefit of turning off shaping + fq_codel
Date: Tue, 27 Nov 2018 23:07:12 +0100 [thread overview]
Message-ID: <C1068E9D-CB97-48CC-BC97-3319E95A3815@heistp.net> (raw)
In-Reply-To: <CAA93jw5P=WTKjTeG8usPJs4DdRO2juQZ-Pk9sEcJtVv032vy4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
> On Nov 27, 2018, at 8:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I wish I knew of a mailing list where I could get a definitive answer
> on "modern problems with async circuits", or an update on the kind of
> techniques the new AI chips were using to keep their power consumption
> so low. I'll keep googling.
I’d be interested in knowing this as well. This gives some examples of async circuits: https://web.stanford.edu/class/archive/ee/ee371/ee371.1066/lectures/lect_12.pdf <https://web.stanford.edu/class/archive/ee/ee371/ee371.1066/lectures/lect_12.pdf>
Page 43, “Bottom Line” mentions that asynchronous design has “some delay matching / overhead issues”. Apparently delay matching means getting the signal outputs on two separate paths to arrive at the same time(?) Presumably overhead refers to the 2x space on the die previously mentioned, for completion detection. Pages 23-25 on “data-bundling constraints” might also highlight some other challenges. Some more current material would be interesting though...
[-- Attachment #2: Type: text/html, Size: 4489 bytes --]
next prev parent reply other threads:[~2018-11-27 22:07 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 [this message]
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 ` [Bloat] one benefit of turning off shaping + fq_codel Holland, Jake
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=C1068E9D-CB97-48CC-BC97-3319E95A3815@heistp.net \
--to=pete@heistp.net \
--cc=bloat@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