General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Bruno George Moraes <brunogm0@gmail.com>
Cc: Bufferbloat lists bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] known buffer sizes on switches
Date: Wed, 28 Nov 2018 08:55:17 -0800	[thread overview]
Message-ID: <87y39dywei.fsf@taht.net> (raw)
In-Reply-To: <CAJpr3FMOr+zC1_oEnDU0s+67b2SLPSELo4esLQY-UCJtOGtKNw@mail.gmail.com> (Bruno George Moraes's message of "Wed, 28 Nov 2018 14:32:10 -0200")

Bruno George Moraes <brunogm0@gmail.com> writes:

>     Nice resource, thanks.
>
> If someone wonders why things look the way they do, so it's all about 
> on-die and off-die memory. Either you use off-die or on-die memory, often 
> SRAM which requires 6 gates per bit. So spending half a billion gates 
> gives you ~10MB buffer on-die. If you're doing off-die memory (DRAM or 
> similar) then you'll get the gigabytes of memory seen in some equipment. 
> There basically is nothing in between. As soon as you go off-die you might 
> as well put at least 2-6 GB in there.
>
> There are some reasearch on new memory devices with unexpected
> results...
> https://ieeexplore.ieee.org/document/8533260
>
>     The HMC memory allows improvements in execution time and consumed
>     energy. In some situations, this memory type permits removing the
>     L2 cache from the memory hierarchy. 
>
> HMC parts start at 2GB 

Thank you for that. I do have a long standing dream of a single chip
wifi router, with the lowest SNR possible, and the minimum number of
pins coming off of it. I'd settle for 32MB of (static?) ram on chip as
that has proven sufficient to date to drive 802.11n....

which would let you get rid of both the L2 and L1 cache. That said, I
think the cost of 32MB of on-chip static ram remains a bit high, and
plugging it into a mips cpu, kind of silly. Someday there will be a case
to just doing everything on a single chip, but...

>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2018-11-28 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 16:32 Bruno George Moraes
2018-11-28 16:55 ` Dave Taht [this message]
2018-11-28 18:25   ` Dave Collier-Brown
2018-11-28 18:26   ` David Collier-Brown
2018-11-28 19:02     ` Dave Taht
2018-11-28 20:34       ` David Collier-Brown
2018-11-29  2:33   ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2018-11-24 23:29 Dave Taht
2018-11-25  6:44 ` Mikael Abrahamsson

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=87y39dywei.fsf@taht.net \
    --to=dave@taht.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=brunogm0@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