11 points caminanteblanco 1 hour ago 8 comments
theamk 37 minutes ago | parent
No standard equipment can do 64K+ frames, so you are not going to be connecting to global internet soon.
Plus, why are you doing this at all?
If you are super-concerned with the overhead, you don't want IP stack anyway, with all its layers and tunables - you want something like RDMA which can work very close to metal.
And if you are OK with overhead, then why go with huge frames? Go with small ones and reassemble, your life would be much easier. (Normally reassembling is a pain because of possibility of lost or reordered packets, but if you are willing to go with such huge packet size, it must not be a concern with you)
(this reminds of the opposite direction: people stuffing IPv6 into sensor networks.. your frames are 32/64 _bytes_ and you want IPv6 headers in there???)
caminanteblanco 24 minutes ago | parent
caminanteblanco 27 minutes ago | parent
The only place I could see the layman ever getting close to using this would be loopback. But at that point, you have IPC.
Palomides 7 minutes ago | parent
Pet_Ant 5 minutes ago | parent
I mean inter-container communication on a host?
Also I assume it’s not a design goal to support 4GB but it probably just a result of a power of 2. They just probably declared 32 bit size field and this is the result. Trimming it to 30 bit to cap it at 1GB or something is kore hassle then it’s worth
warkdarrior 2 minutes ago | parent
riffic 2 minutes ago | parent