From owner-freebsd-arm@freebsd.org Tue Jul 7 06:44:06 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E052C3574D5 for ; Tue, 7 Jul 2020 06:44:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-54.consmr.mail.gq1.yahoo.com (sonic307-54.consmr.mail.gq1.yahoo.com [98.137.64.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B1CZs5v4cz4875 for ; Tue, 7 Jul 2020 06:44:05 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 5SEo1b0VM1n0h5o56u6piHqKQpd6Rz8ZCWqyMehq1dnGZzs9zCQGRfUR7HsAs07 p3T1EegRYpIvqY8AyYQRClVa9D8cRS.kaxgsu7qvAeYP.MnrXinPHsnuWMxUTwCvIw72_VCcdg4S l69fTrYkqrnm_t3kr6NL07uVQ50K7962SEKS1jZN2gluanIxGUbCIq4rN.mIwoAMLY5uC.Ac_ggW 0r0FeC46G62Stc15f6iD.nOmp.XwYDNlkXhkGQZ5Ti5o5rudDfxIlD_rFd2une1DEn.Tmllb_FeI ysgqoOMCZVWEB9mg1skR1f.WnTUu9Saf.kupPLLoPqgPN3qqPkqTypNCuIJQypS3A30bygO3Gn51 Ba7xmVUSNItH.ItBaGcfmPICxH_qgQFAGU.AIsskNMfuh0.7s_4YYAzuA5ImygC.jCaSegSazMzU SHLCn_y8fT6Ek5eEq81XWuTH5xLYx5txQz6wPKAftPgdp1leD.R1UmZK54wMBwmE2FKh_JqyHwh6 Heu7MCURHOVm2v7i05mBMSLtwb_ZxScwU9aukBdQvnu.yD5DUly8daeOxGMuyYJIvAtbwop4unMl hJ2waYpNsLDgvkqUXARImW3BwDAoGM1yF1tKKaAi_Jyt8rQWgkyNAjdF8vWc1_HjGdVKy5S30o1R rHVd9IrblUs5nVqgVTPiCrudwcmuMx7hDGzfwAPfonlG0asYA2HOY1PU2fASYz3P6mrDsrrbHDWH WWa3ZE8Hm1AQuH6zRt4uQF7JHBI4031VN0SGBTxaFkdNUnQe024txnsLL8CoA7341N97gKXWGrzM pE6dZNnah.Ti.9DqNzD7W9BaN0nvyDEHP33cbe7HshyzLpFJWKAHVm7QW_F3uTudwPtEkMiCWEpL HtnPVjWvMt3VBb2LzZUr9AkQWyavLUY_uXVhD36P5wQlKE2IAc30plYr2h13XEtHlLaX1hrSBhfb s0zoUY4DmPEaxL0dOZ6dmUZYLTQ.AEJtwBUT7mBVckCyn7GeG8i4WgmZtv_oq7K7kAiJj8oGW6FV cwPFwhvC_j5XeQD89Eve95JhLtLlqvqKt_Mga7jpBOR8sjzPvrogq6f6hXfsB1D7r1zbX3Ni5UMA cdu26YkJwMg8220l1MeEwjJz064dPttn.RmjDzXemWA.29ehOGGAvyE4aC0u_dhjHYCsmBSokiQz 0lwI2EheQwLBuQeNix46K2gE5DGqxO35MXIf92x8WBrKJl.JAva.BL7.GuRiWmQFS.BVn_Y5Bauf YcWuRk4k3j_jx2Rh5kMqQU0wtpMhjhcGG_EPfnGf6XCvlX4GE_Av8eOAN2qZyBda2EkGL_.RX2.f TpzG1XT5mCQ7e.w.B_1Q4rU3Qi9nQNiMGZblMEtrOmHHRVizpt5X6T1D8uHGcRK5iV5FrY1ZktnY rMPiWZLk6LVQk6pOOnSZGJhN7WFMQHuTOggRSsVcgnbYpiWIj Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Tue, 7 Jul 2020 06:44:02 +0000 Received: by smtp423.mail.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID e9349ee6ad9b847e386dd754cd8fca37; Tue, 07 Jul 2020 06:44:00 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: freebsd-arm Digest, Vol 740, Issue 7 (Rock64 Ethernet testing) From: Mark Millard In-Reply-To: Date: Mon, 6 Jul 2020 23:43:59 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <1731fbded28.10a3342f0357159.8148813293316485882@fkardame.com> <20200706204707.GA94158@bluezbox.com> <0A2E974E-39D3-46C8-8791-3BD914EBE7E9@yahoo.com> <0C77695E-A9D0-410A-B105-5B69823E17E2@yahoo.com> To: Oleksandr Tymoshenko , Peter Jeremy X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 4B1CZs5v4cz4875 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.38 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.30:from]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-1.00)[-0.997]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.30:from]; NEURAL_HAM_SHORT(-0.89)[-0.890]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2020 06:44:06 -0000 On 2020-Jul-6, at 23:22, Mark Millard wrote: > On 2020-Jul-6, at 23:03, Mark Millard wrote: >=20 >=20 >> On 2020-Jul-6, at 14:21, Mark Millard wrote: >>=20 >>> On 2020-Jul-6, at 13:47, Oleksandr Tymoshenko wrote: >>>=20 >>>> 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. >>>=20 >>> 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. >>>=20 >>> 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. >>=20 >> I put a copy of the -r362982 *debug* kernel from >> artifacts.ci.freebsd.org on the Rock64 V2.0 that >> I sometimes have access to. There are no hardware >> mods to the Rock64 V2.0. >>=20 >> It did DHCP to pick up an address just fine during >> the boot. I ssh'd into it just fine after the boot. >>=20 >> # uname -apKU >> FreeBSD Rock64orRPi4 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r362982: = Tue Jul 7 03:41:02 UTC 2020 = root@FreeBSD-head-aarch64-build.jail.ci.FreeBSD.org:/usr/obj/usr/src/arm64= .aarch64/sys/GENERIC arm64 aarch64 1300100 1300092 >>=20 >> # ifconfig >> dwc0: flags=3D8843 metric 0 = mtu 1500 >> options=3D80008 >> ether # >> hwaddr # >> inet # netmask # broadcast # >> media: Ethernet autoselect (1000baseT ) >> status: active >> nd6 options=3D29 >> . . . >>=20 >> I'll note that the Rock64 is the only thing running a debug >> kernel for this note. >>=20 >> An rsync copying an approximately 4 GiByte tar file to the Rock64 >> reported: >>=20 >> # rsync -axHh --info=3Dprogress2 --delete -r = /usr/obj/clang-cortexA53-installworld-poud.tar X@Y:/tmp/ >>=20 >> 4.01G 100% 28.91MB/s 0:02:12 (xfr#1, to-chk=3D0/1) >>=20 >> I'll note that at times it listed over 32MB/s. The storage media >> is a USB3 SSD plugged into the USB3 port. It has the Rock64's >> root filesystem. >>=20 >> For reference, locally duplicating the file on the Rock64 via >> rsync reported: >>=20 >> # rsync -axHh --info=3Dprogress2 -r = /tmp/clang-cortexA53-installworld-poud.tar /tmp/mmjnk.tar >> 4.01G 100% 38.48MB/s 0:01:39 (xfr#1, to-chk=3D0/1) >>=20 >> (from/to: same media). I do not expect that the rsync over the >> network was limited by the target media on the Rock64. >>=20 >> Copying from the same machine to a large, fast machine instead >> of to the Rock64: >>=20 >> # rsync -axHh --info=3Dprogress2 --delete -r = /usr/obj/clang-cortexA53-installworld-poud.tar X@Y:/tmp/ >> 4.01G 100% 77.32MB/s 0:00:49 (xfr#1, to-chk=3D0/1) >>=20 >> So that should not be the side constraining the to-Rock64 >> rate. >>=20 >> Copying from the Rock64 to the large, fast machine: >>=20 >> rsync -axHh --info=3Dprogress2 --delete -r = /tmp/clang-cortexA53-installworld-poud.tar X@Y:/tmp/ >> 4.01G 100% 21.35MB/s 0:02:59 (xfr#1, to-chk=3D0/1) >>=20 >> It did not list figures much higher than above, so slower than >> the copy to the Rock64 fairly generally. >>=20 >> All this activity is over the local network, nothing remote. >> All machines were running head -r360311 (non-debug), except >> for the Rock64 having the -r362982 *debug* kernel instead.=20 >>=20 >> I hope that the above helps. >>=20 >> I see that there are now iperf3 usage instructions so at some >> point I may get that going and report the results, including >> doing a non-debug kernel build and install. >>=20 >=20 > Still using the debug kernel, but I figured I'd show > the results from proving that I can get iperf3 to do > the requested type of testing: >=20 > # iperf3 -c 192.168.1.122 > Connecting to host 192.168.1.122, port 5201 > [ 5] local 192.168.1.109 port 17015 connected to 192.168.1.122 port = 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 45.4 MBytes 381 Mbits/sec 0 730 = KBytes =20 > [ 5] 1.00-2.00 sec 45.4 MBytes 380 Mbits/sec 0 730 = KBytes =20 > [ 5] 2.00-3.00 sec 44.9 MBytes 376 Mbits/sec 0 730 = KBytes =20 > [ 5] 3.00-4.00 sec 45.3 MBytes 380 Mbits/sec 0 730 = KBytes =20 > [ 5] 4.00-5.00 sec 44.7 MBytes 375 Mbits/sec 0 730 = KBytes =20 > [ 5] 5.00-6.00 sec 45.2 MBytes 378 Mbits/sec 0 730 = KBytes =20 > [ 5] 6.00-7.00 sec 44.7 MBytes 376 Mbits/sec 0 730 = KBytes =20 > [ 5] 7.00-8.00 sec 44.6 MBytes 374 Mbits/sec 0 730 = KBytes =20 > [ 5] 8.00-9.00 sec 44.7 MBytes 375 Mbits/sec 0 730 = KBytes =20 > [ 5] 9.00-10.00 sec 45.3 MBytes 380 Mbits/sec 0 730 = KBytes =20 > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.00 sec 450 MBytes 377 Mbits/sec 0 = sender > [ 5] 0.00-10.62 sec 450 MBytes 355 Mbits/sec = receiver >=20 > # iperf3 -R -c 192.168.1.122 > Connecting to host 192.168.1.122, port 5201 > Reverse mode, remote host 192.168.1.122 is sending > [ 5] local 192.168.1.109 port 54738 connected to 192.168.1.122 port = 5201 > [ ID] Interval Transfer Bitrate > [ 5] 0.00-1.00 sec 61.4 MBytes 515 Mbits/sec =20= > [ 5] 1.00-2.00 sec 61.3 MBytes 514 Mbits/sec =20= > [ 5] 2.00-3.00 sec 61.3 MBytes 515 Mbits/sec =20= > [ 5] 3.00-4.00 sec 61.4 MBytes 515 Mbits/sec =20= > [ 5] 4.00-5.00 sec 61.4 MBytes 515 Mbits/sec =20= > [ 5] 5.00-6.00 sec 61.2 MBytes 513 Mbits/sec =20= > [ 5] 6.00-7.00 sec 61.4 MBytes 515 Mbits/sec =20= > [ 5] 7.00-8.00 sec 61.3 MBytes 514 Mbits/sec =20= > [ 5] 8.00-9.00 sec 61.4 MBytes 515 Mbits/sec =20= > [ 5] 9.00-10.00 sec 61.3 MBytes 514 Mbits/sec =20= > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.61 sec 614 MBytes 486 Mbits/sec 28 = sender > [ 5] 0.00-10.00 sec 613 MBytes 515 Mbits/sec = receiver >=20 > I'll note that I run with the following in /etc/sysctl.conf : >=20 > # The Rock64 does not seem to automatically adjust from 600MHz, > # so do so manually. (The specifics likely would not be > # appropriate to the RPi4/3.) > dev.cpu.0.freq=3D1200 >=20 > It is a historical artifact that I've not checked on the > status of in a very long time: it works so I leave it > there. Looks like it will be some time before I deal with updating to a more modern kernel/world (non-debug). But I switched back to my non-debug head -r360311 kernel (and dtb) build and here are the iperf3 results for that context: # iperf3 -c 192.168.1.122 Connecting to host 192.168.1.122, port 5201 [ 5] local 192.168.1.109 port 39541 connected to 192.168.1.122 port = 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 73.6 MBytes 617 Mbits/sec 0 1.07 MBytes = =20 [ 5] 1.00-2.00 sec 72.9 MBytes 612 Mbits/sec 0 1.60 MBytes = =20 [ 5] 2.00-3.00 sec 72.9 MBytes 611 Mbits/sec 0 1.60 MBytes = =20 [ 5] 3.00-4.00 sec 72.8 MBytes 611 Mbits/sec 0 1.60 MBytes = =20 [ 5] 4.00-5.00 sec 72.9 MBytes 611 Mbits/sec 0 1.60 MBytes = =20 [ 5] 5.00-6.00 sec 72.9 MBytes 611 Mbits/sec 0 1.60 MBytes = =20 [ 5] 6.00-7.00 sec 72.7 MBytes 610 Mbits/sec 0 1.60 MBytes = =20 [ 5] 7.00-8.00 sec 72.8 MBytes 610 Mbits/sec 0 1.60 MBytes = =20 [ 5] 8.00-9.00 sec 72.8 MBytes 611 Mbits/sec 0 1.60 MBytes = =20 [ 5] 9.00-10.00 sec 72.8 MBytes 610 Mbits/sec 0 1.60 MBytes = =20 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 729 MBytes 611 Mbits/sec 0 = sender [ 5] 0.00-10.32 sec 729 MBytes 593 Mbits/sec = receiver # iperf3 -R -c 192.168.1.122 Connecting to host 192.168.1.122, port 5201 Reverse mode, remote host 192.168.1.122 is sending [ 5] local 192.168.1.109 port 50696 connected to 192.168.1.122 port = 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec =20 [ 5] 2.00-3.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 3.00-4.00 sec 84.4 MBytes 708 Mbits/sec =20 [ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 5.00-6.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 6.00-7.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 7.00-8.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 8.00-9.00 sec 112 MBytes 941 Mbits/sec =20 [ 5] 9.00-10.00 sec 112 MBytes 941 Mbits/sec =20 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.31 sec 1.07 GBytes 892 Mbits/sec 55 = sender [ 5] 0.00-10.00 sec 1.07 GBytes 918 Mbits/sec = receiver =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)