Date: Thu, 03 Jun 2021 04:25:37 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 256375] iflib/if_em: unplugging network cable causes huge KTorrent slowdown Message-ID: <bug-256375-7501-WeYd7jeVWA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256375-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-256375-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=3D256375 --- Comment #3 from Alexey Dokuchaev <danfe@FreeBSD.org> --- Created attachment 225516 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D225516&action= =3Dedit dtrace output, cable unplugged Alexander suggested I run the following DTrace script, with and without the cable, to see if the problem has something to do with the lock or rather em_if_update_admin_status(): dtrace -n 'fbt::iflib_media_status:entry { self->ts =3D timestamp; } fbt::iflib_media_status:return /self->ts/ {@[execname, "ns"] =3D quantize(timestamp - self->ts); self->ts =3D 0; }' So, two things: 1) KTorrent is not required to reproduce the bug (good), ifconfig(8) is also slowed down, these is actually a visible delay of its console output when I run without the cable; and 2) apparently em_if_update_admin_status() is bogusly and repeatedly checking hw link stat= us despite, as Alexander had mentioned, that there actually is a link status f= ield which is being checked in other functions. --=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-256375-7501-WeYd7jeVWA>