CFT: major update to if_ure (RPi4B uefi/ACPI booted example's iperf3 output)
Mark Millard
marklmi at yahoo.com
Tue Jul 28 20:03:54 UTC 2020
I had reason to switch to using the RPi4B, which happens
to be booted from ACPI. The only Ethernet connection
present for this test is via:
Autoloading module: if_ure.ko
ure0 on uhub1
ure0: <Realtek USB 10/100/1000 LAN, class 0/0, rev 3.00/30.00, addr 2> on usbus0
add host 127.0.0.1: gateway lo0 fib 0: route already in table
miibus0: <MII bus> on ure0
rgephy0: <RTL8251/8153 1000BASE-T media interface> PHY 0 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto
ue0: <USB Ethernet> on ure0
ue0: Ethernet address: ###
. . .
ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=68009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
ether ###
inet 192.168.1.133 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
# iperf3 -c 192.168.1.120 --get-server-output
Connecting to host 192.168.1.120, port 5201
[ 5] local 192.168.1.133 port 15954 connected to 192.168.1.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 83.6 MBytes 702 Mbits/sec 797 17.1 KBytes
[ 5] 1.00-2.00 sec 83.5 MBytes 700 Mbits/sec 797 7.13 KBytes
[ 5] 2.00-3.00 sec 83.7 MBytes 702 Mbits/sec 783 1.43 KBytes
[ 5] 3.00-4.00 sec 83.3 MBytes 699 Mbits/sec 813 127 KBytes
[ 5] 4.00-5.00 sec 82.8 MBytes 695 Mbits/sec 806 18.5 KBytes
[ 5] 5.00-6.00 sec 83.9 MBytes 704 Mbits/sec 822 38.4 KBytes
[ 5] 6.00-7.00 sec 83.7 MBytes 702 Mbits/sec 808 64.2 KBytes
[ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec 787 92.2 KBytes
[ 5] 8.00-9.00 sec 83.2 MBytes 698 Mbits/sec 788 51.2 KBytes
[ 5] 9.00-10.00 sec 83.1 MBytes 697 Mbits/sec 799 47.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 834 MBytes 700 Mbits/sec 8000 sender
[ 5] 0.00-10.24 sec 834 MBytes 683 Mbits/sec receiver
Server output:
Accepted connection from 192.168.1.133, port 18615
[ 5] local 192.168.1.120 port 5201 connected to 192.168.1.133 port 15954
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 63.7 MBytes 535 Mbits/sec
[ 5] 1.00-2.00 sec 83.3 MBytes 699 Mbits/sec
[ 5] 2.00-3.00 sec 83.6 MBytes 701 Mbits/sec
[ 5] 3.00-4.00 sec 83.5 MBytes 700 Mbits/sec
[ 5] 4.00-5.00 sec 83.4 MBytes 699 Mbits/sec
[ 5] 5.00-6.00 sec 83.5 MBytes 700 Mbits/sec
[ 5] 6.00-7.00 sec 83.2 MBytes 698 Mbits/sec
[ 5] 7.00-8.00 sec 83.5 MBytes 701 Mbits/sec
[ 5] 8.00-9.00 sec 83.1 MBytes 697 Mbits/sec
[ 5] 9.00-10.00 sec 83.4 MBytes 700 Mbits/sec
[ 5] 10.00-10.24 sec 19.6 MBytes 693 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.24 sec 834 MBytes 683 Mbits/sec receiver
iperf Done.
# iperf3 -R -c 192.168.1.120 --get-server-output
Connecting to host 192.168.1.120, port 5201
Reverse mode, remote host 192.168.1.120 is sending
[ 5] local 192.168.1.133 port 55961 connected to 192.168.1.120 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 111 MBytes 933 Mbits/sec
[ 5] 1.00-2.00 sec 111 MBytes 933 Mbits/sec
[ 5] 2.00-3.00 sec 111 MBytes 933 Mbits/sec
[ 5] 3.00-4.00 sec 111 MBytes 933 Mbits/sec
[ 5] 4.00-5.00 sec 111 MBytes 932 Mbits/sec
[ 5] 5.00-6.00 sec 111 MBytes 933 Mbits/sec
[ 5] 6.00-7.00 sec 111 MBytes 933 Mbits/sec
[ 5] 7.00-8.00 sec 111 MBytes 933 Mbits/sec
[ 5] 8.00-9.00 sec 111 MBytes 933 Mbits/sec
[ 5] 9.00-10.00 sec 111 MBytes 933 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.23 sec 1.09 GBytes 914 Mbits/sec 498 sender
[ 5] 0.00-10.00 sec 1.09 GBytes 933 Mbits/sec receiver
Server output:
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.1.133, port 51297
[ 5] local 192.168.1.120 port 5201 connected to 192.168.1.133 port 55961
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 87.5 MBytes 734 Mbits/sec 72 1.60 MBytes
[ 5] 1.00-2.00 sec 111 MBytes 933 Mbits/sec 92 1.60 MBytes
[ 5] 2.00-3.00 sec 111 MBytes 933 Mbits/sec 96 191 KBytes
[ 5] 3.00-4.00 sec 111 MBytes 933 Mbits/sec 99 234 KBytes
[ 5] 4.00-5.00 sec 111 MBytes 933 Mbits/sec 87 1.06 MBytes
[ 5] 5.00-6.00 sec 111 MBytes 932 Mbits/sec 50 529 KBytes
[ 5] 6.00-7.00 sec 111 MBytes 933 Mbits/sec 0 779 KBytes
[ 5] 7.00-8.00 sec 111 MBytes 933 Mbits/sec 0 964 KBytes
[ 5] 8.00-9.00 sec 111 MBytes 933 Mbits/sec 2 469 KBytes
[ 5] 9.00-10.00 sec 111 MBytes 933 Mbits/sec 0 739 KBytes
[ 5] 10.00-10.23 sec 25.4 MBytes 932 Mbits/sec 0 787 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.23 sec 1.09 GBytes 914 Mbits/sec 498 sender
iperf Done.
For reference, the RPi4B's CortextA72 is speed controlled via:
over_voltage=6
arm_freq=2000
in the RPi4's config.txt . As stands UEFI is configured to
impose a 3 GiByte RAM limit to avoid FreeBSD not handling
it DMA address-range limitations yet.
My prior A72 test was on a MACCHIATObin Double Shot (where
EtherNet via USB3 is the only type of EtherNet available
in my context).
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
More information about the freebsd-current
mailing list