From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] The amazon firecracker micro-vm TCP implementation...
Date: Sat, 28 Jan 2023 11:13:30 -0800 [thread overview]
Message-ID: <CAA93jw5dYLEYGwhHLBoxvgJjRc6nhZ_zUSQ2kkumKWh7SSBBWA@mail.gmail.com> (raw)
has no congestion controls. I was hearing some good things about the
overall microvm concept (see here:
https://firecracker-microvm.github.io/
) so I briefly took a look at the code.
/// The current implementation does not do any kind of congestion
control, expects segments to
/// arrive in order, triggers a retransmission after the first
duplicate `ACK`, and relies on the
/// user to supply an opaque `u64` timestamp value when invoking send
or receive functionality. The
/// timestamps must be non-decreasing, and are mainly used for
retransmission timeouts.
https://github.com/firecracker-microvm/firecracker/blob/main/src/dumbo/src/tcp/connection.rs#L148
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2023-01-28 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw5dYLEYGwhHLBoxvgJjRc6nhZ_zUSQ2kkumKWh7SSBBWA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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