[Bloat] The amazon firecracker micro-vm TCP implementation...

[Bloat] The amazon firecracker micro-vm TCP implementation...

[Dave Taht]

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