From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] 400g Tomahawk-3 chip
Date: Fri, 26 Jan 2018 19:31:18 -0800 [thread overview]
Message-ID: <CAA93jw6D8_zuo79xOGD5bZ6LiRoK4sOcvO6ik2C4pEU10s-0dg@mail.gmail.com> (raw)
If someone could translate the "smart buffering", "flow aware" and
"mice v elephants" comments into how it actually works in the
tomahawk-3 chip... I'd love it.
from: https://www.nextplatform.com/2018/01/20/flattening-networks-budgets-400g-ethernet/
"The packet processing pipeline sits behind the ports, implementing
ingress and egress packet processing, and because the buffer is
shared, it can hold a lot of data if a port that is the destination
becomes clogged and wait out the traffic jam without dropping packets
and forcing a resend. The buffer architecture has support for RoCEv2
remote direct memory access and congestion control, and also has what
Broadcom calls flow-aware traffic scheduling, which is a key for
hyperscalers and cloud builders and more than a few HPC and AI shops,
too.
“Companies are not running monolithic workloads,” explains Sankar.
“They run many different applications, running in parallel, as they go
through the switches. In that case, you have elephants and mice, the
former of which causes queueing delays that affect different flows in
different ways. So in real time, we can see those bandwidth-consuming
elephants and reprioritize them versus the mice to ensure that both
classes of traffic are experiencing the least amount of queueing
delay. This new architecture for buffering ultimately eliminates drops
and has 3X to 5X greater incast absorption and lossless capacity
versus alternatives, and in the process it drives down tail latency.”
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2018-01-27 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 3:31 Dave Taht [this message]
2018-01-27 6:35 ` Jonathan Morton
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=CAA93jw6D8_zuo79xOGD5bZ6LiRoK4sOcvO6ik2C4pEU10s-0dg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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