Date: Mon, 6 Jul 2020 14:21:33 -0700 From: Mark Millard <marklmi@yahoo.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: freebsd-arm Digest, Vol 740, Issue 7 Message-ID: <0A2E974E-39D3-46C8-8791-3BD914EBE7E9@yahoo.com> In-Reply-To: <20200706204707.GA94158@bluezbox.com> References: <mailman.75.1593950402.45034.freebsd-arm@freebsd.org> <1731fbded28.10a3342f0357159.8148813293316485882@fkardame.com> <20200706204707.GA94158@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Jul-6, at 13:47, Oleksandr Tymoshenko <gonzo at bluezbox.com> = wrote: > Furkan Salman (furkan@fkardame.com) wrote: >> Hello Peter, >>=20 >> I have rockpiE which is somewhat similar to Rock64, If s133pwa1k9r@ = or gonzo@ can confirm if rockpie can be used to test RK3328 Lan issue = then I am happy to help with testing. >=20 >=20 > Hi Furkan, >=20 > Yes, RockPi E seems to be a good test target. If you could check the > GigE interface before and after the patch. Whether it works/doesn't = work > and if it works in both cases - try testing performance with iperf3, > just to see if performance was affected in any way. For folks not familiar with the general type of activity or specifically with iperf3 (or other specifics), more detailed information to "collect and report . . ., collecting the information via the commands . . ." could help: more step-by-step. Also: Do you care between debug kernels vs. non-debug kernels? Debug ones of the appropriate vintage for head are available via artifacts.ci.freebsd.org but there might be performance consequences to using such. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0A2E974E-39D3-46C8-8791-3BD914EBE7E9>