> The situation with encapsulation is even more complicated: > > We are basically only interested in the UDP/vxlan/Ethernet/IP/UDP > constellation. If we do the fragmentation inside the vxlan tunnel and > carry over the skb hash to all resulting UDP/vxlan packets source ports, > we are fine and reordering on the receiver NIC won't happen in this > case. If the fragmentation happens on the outer UDP header, this will > result in reordering of the inner L2 flow. Unfortunately this depends on > how the vxlan tunnel was set up, how other devices do that and (I > believe so) on the kernel version. > This really isn't that complicated. The assumption that an IP network always delivers packets in order is simply wrong. The inventors of VXLAN must have know full well that when you use IP, packets can and eventually will be delivered out of order. This isn't just because of fragmentation, there are many other reasons that packets can be delivered OOO. This also must have been known when IP/GRE and any other protocol that carries L2 over IP was invented. If OOO is an issue for these protocols then they need to be fixed-- this is not a concern with IP protocol nor the stack.
Tom
