News for hackers. Stuff that matters.
Re:IP traffic over ICMP tunneling by dogma1138 on Wednesday November 11, 2015 @07:26PM (#10550441)
Poor choice of words on my part, if you configure jump frames on your uplink you are going to kill your network stack, if you limit it too much you'll have a huge overhead. The point being is that for transferring data especially when responsiveness is important if not paramount utilizing the maximum potential frame size you can push without fragmentation would generally yield a poorer result in real world applications.
Re:IP traffic over ICMP tunneling by simoncion on Wednesday November 11, 2015 @08:36PM (#10550739)
> [I]f you configure [jumbo] frames on your uplink you are going to kill your network stack...

I can't agree with that statement. If upstream devices support larger than 1500 byte MTU, OR PTMU works correctly, then you are absolutely not going to "kill your network stack". At worst, (in the PMTU discovery phase) you'll see poor performance for a few moments while the MTU for the path is worked out, and then nothing but smooth sailing from then on.

> The point being is that for transferring data especially when responsiveness is important if not paramount utilizing the maximum potential frame size you can push without fragmentation would generally yield a poorer result in real world applications.

I'm not sure what you're saying here. Are you saying:

"If you configure your networking equipment to always wait to fill up a full L2 frame before sending it off, you'll harm perf on latency-sensitive applications."?

If you're not, would you be so kind as to rephrase your statement? I may be particularly dense today. :)

However, if you are, then that statement is pretty obvious. I expect that few people configure their networks to do that. However, I don't see what that has to do with the link's MTU. Just because you have a 9k+ MTU, doesn't mean that you have to transmit 9k of data at a time. :)