diff options
| author |   Vratko Polak <vrpolak@cisco.com> | 2023-05-22 10:14:09 +0200 |
|---|---|---|
| committer | Vratko Polak <vrpolak@cisco.com> | 2023-05-22 10:14:09 +0200 |
| commit | 6e862ec7b63e177b9b0103612848b3377271729b (patch) | |
| tree | 66cc7d86e049536acf5246c4159c9483df2ee1aa /topologies/available/lf_3na_spr_testbed21.yaml | |
| parent | ec194ef8ecfa656b9b1d5056b49dd3877d1268e1 (diff) | |
feat(interface): apply MTU for dpdk plugin ifaces
When changing MTU on a running VPP, the interface has to be down.
- Other plugins (rdma, avf, af_xdp) need vastly different logic,
so support for them will be added later.
+ Mlx5-core does not need to set MTU on Linux interface.
+ MTU setting now does not happen at final setting path up,
it happens in driver initialization layer instead
E.g. AVF tests will not attempt to change MTU.
+ MTU edit removed from some non-hardware interfaces (including memif)
e.g. bond interfaces. MTU on parent hw interface seems to be enough.
+ The non-jumbo MTU value used is 1800,
so 1518B tests with additional encapsulation can still work.
+ When VPP MTU setting fails, the failure is now propagated.
Previously, the failure was just logged and ignored,
but now there is no reason to hide it.
Ticket: CSIT-1797
Change-Id: I3b853f1faf90001d544cbbb87b2affbb882ffba0
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'topologies/available/lf_3na_spr_testbed21.yaml')
0 files changed, 0 insertions, 0 deletions