From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rjmcmahon@rjmcmahon.com>
Received: from bobcat.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 329CA3B2A4
 for <rpm@lists.bufferbloat.net>; Sun, 19 Feb 2023 18:34:28 -0500 (EST)
Received: from mail.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123])
 by bobcat.rjmcmahon.com (Postfix) with ESMTPA id 5AAA31B258;
 Sun, 19 Feb 2023 15:34:27 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bobcat.rjmcmahon.com 5AAA31B258
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjmcmahon.com;
 s=bobcat; t=1676849667;
 bh=tCnkN2qjlabADrj5gRFuRRl9p1zQHjseeagGhk47UpQ=;
 h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
 b=CHIgjNk9C7PoBWjBFnU0iGo2tyWgsCYezT4NQWzPIikzitCGnMB0cDnFyvG71cXXO
 aFT4dew/eyiKehNhgTEmhd3yjDYovAIF183UDzDCmOGuNJ91pdeWpCrmcKr4CXeRd9
 TBHJ7Z94ZrE51/BjM9uxu1hHw268HfErU/IzffpE=
MIME-Version: 1.0
Date: Sun, 19 Feb 2023 15:34:27 -0800
From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
In-Reply-To: <CAA93jw6Si5wWhfM4PS0VAWjPJhcSNvN7+098SQCLuqODPohsvA@mail.gmail.com>
References: <CAA93jw6Si5wWhfM4PS0VAWjPJhcSNvN7+098SQCLuqODPohsvA@mail.gmail.com>
Message-ID: <26ac4e4e00b1d0f20c816630fafb7e58@rjmcmahon.com>
X-Sender: rjmcmahon@rjmcmahon.com
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Rpm] Almost had a dialog going with juniper...
X-BeenThere: rpm@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: revolutions per minute - a new metric for measuring responsiveness
 <rpm.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/rpm>,
 <mailto:rpm-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/rpm>
List-Post: <mailto:rpm@lists.bufferbloat.net>
List-Help: <mailto:rpm-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/rpm>,
 <mailto:rpm-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2023 23:34:28 -0000

Their post isn't really about bloat. It's about the discrepancy in i/o 
bw of memory off-chip and on-chip.

My opinion is that the off-chip memory or hybrid approach is a design 
flaw for a serious router mfg. The flaw is thinking the links' rates and 
the chip memory i/o rates aren't connected when obviously they are. Just 
go fast as possible and let some other device buffer, e.g. the end host 
or the server in the cloud.

Bob
> https://blog.cerowrt.org/post/juniper/
> 
> But they deleted the comment thread. It is interesting, I suppose, to
> see how they frame the buffering problems to themselves in their post:
> https://www.linkedin.com/pulse/sizing-router-buffers-small-new-big-sharada-yeluri/