From: Michael Richardson <mcr@sandelman.ca>
To: bloat <bloat@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Bloat] aquila interconnect
Date: Thu, 09 Feb 2023 15:23:38 -0500 [thread overview]
Message-ID: <28493.1675974218@localhost> (raw)
In-Reply-To: <CAA93jw6n82vaOx6PmLfyTCXtQ=igdym17u7P4b1ST5AXxjSsuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
Interesting read.
my takehome is that google is now building cabinet-sized NUMA clusters with
hot-swappable 1U "cards".
It's not the Aquila replaces ethernet, it's that the compute cluster has
eaten the ToR switch, and moved the ethernet ports outward.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-02-09 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 17:09 Dave Taht
2023-02-09 20:23 ` Michael Richardson [this message]
2023-02-10 2:50 ` [Bloat] [Starlink] " Jeff Tantsura
2023-02-10 15:28 ` Hesham ElBakoury
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=28493.1675974218@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
/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