diff options
author | Martin Braun <martin.braun@ettus.com> | 2021-11-16 11:50:55 +0100 |
---|---|---|
committer | Aaron Rossetto <aaron.rossetto@ni.com> | 2021-12-02 05:49:53 -0800 |
commit | d5f7b0cf90f5095059004445852a422e914c52cb (patch) | |
tree | b6bb9f5db14fd5ee06f3a79e87f53ee40e463047 /.clang-tidy | |
parent | 902c8456fbd13e85b930eae423e24b7abfc81869 (diff) | |
download | uhd-d5f7b0cf90f5095059004445852a422e914c52cb.tar.gz uhd-d5f7b0cf90f5095059004445852a422e914c52cb.tar.bz2 uhd-d5f7b0cf90f5095059004445852a422e914c52cb.zip |
mpmd: Add MTU plausibility check
We have noticed that on 1 GbE connections, MTU discovery can become
unreliable. Since we now use the MTU directly for deriving spp and other
values, a correct MTU is important.
Because we don't have a way of knowing if MTU discovery worked or not,
we add some heuristics in form of a plausibility check. For now, the
only rule in this check is if that the detected MTU is a bit larger than
1472 bytes, we coerce down to 1472, because this is such a standard
value (most 1 GbE interfaces default to an IPv4 MTU of 1500 bytes).
For the cases where the interface MTU is set to be between 1500 and 1528
bytes, this would cause a very minor performance loss. We accept this
performance loss as it is small, and those cases are very rare. MTUs are
usually 1500 bytes, or >= 8000 bytes for high-speed links using jumbo
frames.
Diffstat (limited to '.clang-tidy')
0 files changed, 0 insertions, 0 deletions