From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] A brick wall threshold for SCE_threshold
Date: Tue, 9 Mar 2021 11:20:22 -0800 [thread overview]
Message-ID: <CAA93jw6Wu4n+kgXmcqvG60OtiwW9X61EeH_rO+HEJC0OVG9jmg@mail.gmail.com> (raw)
In-Reply-To: <C8E7CA7B-55A8-4174-98F3-885A236BE955@gmail.com>
On Tue, Mar 9, 2021 at 10:58 AM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 9 Mar, 2021, at 8:48 pm, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I do not think anything other than a brick wall can be implemented in high speed hardware.
>
> We've spoken to a Cisco guy who says they can already do Approximate Fairness at 100Gbps per port. That's our benchmark.
I have long wondered how much of AFD they were selling.
>
> > I really wish you'd try a brick wall
>
> We did. We didn't like the results.
But you did not try a bbr-like approach. Observe a mark, and the rtt inflation.
bbrv2 works pretty decently with CE_threshold already. making it work
with a brick wall
SCE made some sense.
>
> - Jonathan Morton
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
prev parent reply other threads:[~2021-03-09 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 0:36 [Ecn-sane] ect(1) queue selector question Pete Heist
2021-03-09 1:18 ` Dave Taht
2021-03-09 9:11 ` Pete Heist
2021-03-09 15:19 ` Rodney W. Grimes
2021-03-09 15:28 ` Dave Taht
2021-03-09 15:38 ` Rodney W. Grimes
2021-03-09 18:09 ` [Ecn-sane] A brick wall threshold for SCE_threshold Dave Taht
2021-03-09 18:42 ` Jonathan Morton
2021-03-09 18:48 ` Dave Taht
2021-03-09 18:58 ` Jonathan Morton
2021-03-09 19:20 ` Dave Taht [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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6Wu4n+kgXmcqvG60OtiwW9X61EeH_rO+HEJC0OVG9jmg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=4bone@gndrsh.dnsmgr.net \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@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