General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 400g Tomahawk-3 chip
Date: Sat, 27 Jan 2018 08:35:32 +0200	[thread overview]
Message-ID: <1E00955B-C1C0-42F1-9962-634A90EE78E5@gmail.com> (raw)
In-Reply-To: <CAA93jw6D8_zuo79xOGD5bZ6LiRoK4sOcvO6ik2C4pEU10s-0dg@mail.gmail.com>

> On 27 Jan, 2018, at 5:31 am, Dave Taht <dave.taht@gmail.com> wrote:
> 
> 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.

Just reading what you quoted, it looks like they have a big buffer which can absorb incast bursts effectively (that is, without incurring burst loss), but they also have flow isolation to minimise the inter-flow induced latency that a large buffer would normally imply.  That's definitely a step forward if it's actually in the hardware at those sorts of speeds.

Precisely what counts as "a flow" is not quite clear.  It could be just IP address pairs, rather than 5-tuples.

There doesn't seem to be any explicit mention of AQM here, but that reference to RoCEv2 "congestion control" might imply something in that category - or it could just be a back-pressure mechanism to hint local applications.

 - Jonathan Morton


      reply	other threads:[~2018-01-27  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  3:31 Dave Taht
2018-01-27  6:35 ` Jonathan Morton [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=1E00955B-C1C0-42F1-9962-634A90EE78E5@gmail.com \
    --to=chromatix99@gmail.com \
    --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