Date: Sun, 22 Aug 2021 15:37:03 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 257989] Traffic shaper unable to perform beyond 1Gbit/s limit Message-ID: <bug-257989-7501-ZOfzHeOJlz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257989-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-257989-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=3D257989 Kevin Bowling <kbowling@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #6 from Kevin Bowling <kbowling@freebsd.org> --- Without evidence it sounds like the user may be running out of CPU budget rather than any particular bug. I agree with Kristof that we need more information and the vendor/project needs to help qualify what and where iss= ues are first or this will fatigue devs if it turn into a raw support forum for issues like that. If there is an obvious FreeBSD defect (for instance a panic in unmodified c= ode) I'd send it here right away. Otherwise I think you should figure out how to help users produce more qualified reports, a debug bundle including things = like dmesg, pciconf -lv, relevant sysctls (to include stats ones for the NIC), netstat etc is the standard Mellanox wants when I interact with them in my dayjob, maybe worth consideration here. In this case I'd suggest a more di= rect approach of some 'top' output while bw limited, and even better some pmcstat for at least instructions retired https://wiki.freebsd.org/PmcTools/PmcTop. --=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-257989-7501-ZOfzHeOJlz>