| ▲ | Pet_Ant 2 hours ago | |
> loopback I mean inter-container communication on a host? Also I assume it’s not a design goal to support 4GB but it is just a result of a power of 2. They are basically just doubling the size from 16 to 32 bits. Trimming it to 30 bit to cap it at something "reasonable" 1GB or something is more hassle then it’s worth. I just cannot imagine the error correction on those packets. I mean if anything goes wrong that's a lot to toss away. | ||
| ▲ | wahern 14 minutes ago | parent | next [-] | |
> I just cannot imagine the error correction on those packets. I mean if anything goes wrong that's a lot to toss away. I think the original jumbogram work occurred back when alot of people were still convinced end-to-end IP alone wasn't suitable for many uses. This was the era when, e.g., people were still pitching ATM or exploring bespoke solutions for linking research centers. So basically jumbograms were presumed to be delivered atop another long-haul, multi-link protocol that would provide reliability. Jumbograms were a way to improve the throughput and latency between IP peers with minimal but high-impact changes to application and kernel network stacks (presuming IPv6 adoption), placing most of the complexity in the network transit layers. What we ended up with, ironically, was the reverse, everything IP and below largely ossified from software perspective, some minor evolution at the TCP layer, but most progress happening above TCP/UDP, and alot of work invested in local hardware link layers that remains opaque to IP or even the ethernet software stack, effectively placing a ceiling on dividends. | ||
| ▲ | caminanteblanco 2 hours ago | parent | prev [-] | |
I hadn't thought of that, that would be a potential use case for sure. And I agree that literal 4GB packets probably aren't what's in mind here, but I think it is an oddity that a confluence of other factors has it allowed by the RFC. | ||