From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: rjmcmahon <rjmcmahon@rjmcmahon.com>
Cc: Dave Taht <dave.taht@gmail.com>, Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] Almost had a dialog going with juniper...
Date: Sun, 19 Feb 2023 15:37:51 -0800 [thread overview]
Message-ID: <1209c1b2fb917edc8bf33a73782823bd@rjmcmahon.com> (raw)
In-Reply-To: <26ac4e4e00b1d0f20c816630fafb7e58@rjmcmahon.com>
A bit off topic, but the AP/client power asymmetry is another design
flaw similar to bloat.
Not sure why nobody is talking about that.
https://www.youtube.com/watch?v=Ey5jVUXSJn4
Bob
> 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/
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
next prev parent reply other threads:[~2023-02-19 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 23:02 Dave Taht
2023-02-19 23:34 ` rjmcmahon
2023-02-19 23:37 ` rjmcmahon [this message]
2023-02-19 23:44 ` Dave Taht
2023-02-19 23:52 ` rjmcmahon
2023-02-20 0:02 ` rjmcmahon
2023-02-20 17:56 ` Frantisek Borsik
2023-02-20 18:27 ` Dave Taht
2023-02-20 19:22 ` rjmcmahon
2023-02-19 23:40 ` Dave Taht
2023-02-19 23:44 ` rjmcmahon
2023-02-19 23:45 ` Dave Taht
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209c1b2fb917edc8bf33a73782823bd@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=dave.taht@gmail.com \
--cc=rpm@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