From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "bloat" <bloat@lists.bufferbloat.net>,
"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>,
"Scott Manley" <scottmanley1972@gmail.com>
Subject: Re: [Bloat] [Cerowrt-devel] my thx to spacex (and kerbal space program) forcheering me up all year
Date: Fri, 1 Jan 2021 18:31:12 -0500 (EST) [thread overview]
Message-ID: <1609543872.082620517@apps.rackspace.com> (raw)
It has bufferbloat?
Why am I not surprised?
I can share that one stack hasn't had it from the start, by design. That is one implemented for trading at 10+ GB/sec, implemented in Verilog, and now apparently in production use at one of the largest NY trading intermediaries.
Why? Simply two reasons:
1. People who design parallel hardware systems are trained to focus on closing timing constraints. Which means never using FIFOs that are longer than absolute minimum. The designer is a VLSI designer by trade, not a networking guy.
2. Trading is all about managing delay. In this case, 100 msec packet delay is worst allowable case end to end.
Yet it is full TCP in hardware.
Can't share more, because I don't know more, it being all proprietary to the bank in question.
Now, one wonders: why can't Starlink get it right first time?
It's not like bufferbloat is hard on a single bent pipe hop, which is all Starlink does today.
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Thu, Dec 31, 2020 at 1:37 pm
To: "bloat" <bloat@lists.bufferbloat.net>, "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>, "Scott Manley" <scottmanley1972@gmail.com>
Cc: "bloat" <bloat@lists.bufferbloat.net>, "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>, "Scott Manley" <scottmanley1972@gmail.com>
Subject: [Cerowrt-devel] my thx to spacex (and kerbal space program) forcheering me up all year
If it wasn't for such a long list of wonderful accomplishments in
space, it would have been a sadder year. i just re-recorded my song
"one first landing" out on my dinghy:
https://www.youtube.com/watch?v=wjur0RG-v-I&feature=youtu.be
Maybe someday I'll get scott manley to do his verse on this. Try as I
might over the past few years, I still can't cop his accent.
Now if we can only fix starlink's bufferbloat! It looks to me like the
firmware is QCA's openwrt derivative...
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net CTO, TekLibre, LLC Tel: 1-831-435-0729
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next reply other threads:[~2021-01-01 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 23:31 David P. Reed [this message]
2021-01-02 0:18 ` Jonathan Morton
2021-01-02 17:16 ` Dave Taht
2021-01-02 21:39 ` Scott Manley
2021-01-03 5:48 ` Dave Taht
2021-01-03 1:22 ` Michael Richardson
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=1609543872.082620517@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=scottmanley1972@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