diff options
| author | Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com> | 2018-04-11 11:50:16 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-04-11 14:42:00 -0400 |
| commit | 9d96465b111edd6c4f94345783e6e01db7f435d6 (patch) | |
| tree | 9072e876117fb50427696013dd58e9a9e1916803 /init/do_mounts_initrd.c | |
| parent | 479ca3bf91da971fcefc003cf5773e8d7db24794 (diff) | |
| download | linux-stable-9d96465b111edd6c4f94345783e6e01db7f435d6.tar.gz linux-stable-9d96465b111edd6c4f94345783e6e01db7f435d6.tar.bz2 linux-stable-9d96465b111edd6c4f94345783e6e01db7f435d6.zip | |
bnxt_en: Support max-mtu with VF-reps
While a VF is configured with a bigger mtu (> 1500), any packets that
are punted to the VF-rep (slow-path) get dropped by OVS kernel-datapath
with the following message: "dropped over-mtu packet". Fix this by
returning the max-mtu value for a VF-rep derived from its corresponding VF.
VF-rep's mtu can be changed using 'ip' command as shown in this example:
$ ip link set bnxt0_pf0vf0 mtu 9000
Signed-off-by: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init/do_mounts_initrd.c')
0 files changed, 0 insertions, 0 deletions