diff options
| author |   Alexey Kodanev <alexey.kodanev@oracle.com> | 2018-04-19 15:42:32 +0300 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2018-04-20 11:20:05 -0400 |
| commit | c40e89fd358e94a55d6c1475afbea17b5580f601 (patch) | |
| tree | d8bcd490b48b2f93f91f7da0e8e96ac7336958f3 /.get_maintainer.ignore | |
| parent | geneve: check MTU for a minimum in geneve_change_mtu() (diff) | |
| download | linux-dev-c40e89fd358e94a55d6c1475afbea17b5580f601.tar.xz linux-dev-c40e89fd358e94a55d6c1475afbea17b5580f601.zip | |
geneve: configure MTU based on a lower device
Currently, on a new link creation or when 'remote' address parameter
is updated, an MTU is not changed and always equals 1500. When a lower
device has a larger MTU, it might not be efficient, e.g. for UDP, and
requires the manual MTU adjustments to match the MTU of the lower
device.
This patch tries to automate this process, finds a lower device using
the 'remote' address parameter, then uses its MTU to tune GENEVE's MTU:
* on a new link creation
* when 'remote' parameter is changed
Also with this patch, the MTU from a user, on a new link creation, is
passed to geneve_change_mtu() where it is verified, and MTU adjustments
with a lower device is skipped in that case. Prior that change, it was
possible to set the invalid MTU values on a new link creation.
Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '.get_maintainer.ignore')
0 files changed, 0 insertions, 0 deletions