Date: Mon, 11 Jun 2018 10:52:51 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 228802] [aarch64] network throughput regression in 12.0-CURRENT Message-ID: <bug-228802-7501-sjsaHXBfKO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228802-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-228802-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=228802 --- Comment #16 from Eugene Grosbein <eugen@freebsd.org> --- Unified diff for dmesg.boot files is still useful and lack of it won't make it easier to understand the problem for an arm64 developer. Interrupts are assigned in very different ways for those revisions. Are there exactly same pieces of hardware used? We still need "vmstat -ai" output for same volume of data transferred. Make 10MB file or so and repeate the test, please. Does r334436 have any problems with time management, e.g. too slow wall clock? Can you start ntpd, wait for 20-60 minutes then show contents of drift file /var/db/ntpd.drift ? -- 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-228802-7501-sjsaHXBfKO>