Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Oct 2024 07:05:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 282095] enic breaks when changing MTU on interfaces with fib other than 0
Message-ID:  <bug-282095-7501-86cnZqFIXV@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-282095-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-282095-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282095

--- Comment #3 from Scott Aitken <freebsd-bugzilla@thismonkey.com> ---
This driver may have multiple issues, and if required I'll raise another for
throughput.

To further the troubleshooting of the MTU change issue, I discovered that
traffic doesn't completely stop after changing the MTU, however continuous
pings with default values results in:

# setfib 1 ping 172.12.2.1
PING 172.12.2.1 (172.12.2.1): 56 data bytes
64 bytes from 172.12.2.1: icmp_seq=3D0 ttl=3D64 time=3D24391.545 ms
64 bytes from 172.12.2.1: icmp_seq=3D1 ttl=3D64 time=3D23332.953 ms
^C
--- 172.12.2.1 ping statistics ---
31 packets transmitted, 2 packets received, 93.5% packet loss
round-trip min/avg/max/stddev =3D 23332.953/23862.249/24391.545/529.296 ms

This was with a PCI NIC rather than the MLOM:
enic2: <Cisco VIC Ethernet NIC> port 0x4000-0x407f mem
0xc7010000-0xc7017fff,0xc7018000-0xc7019fff irq 44 at device 0.0 numa-domai=
n 0
on pci20

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282095-7501-86cnZqFIXV>