Re: slow USB 3.0 on -current
On 2020-Jul-13, at 13:18, Mark Millard wrote: > [Just a correction to a side comment.] > > On 2020-Jul-13, at 12:46, Mark Millard wrote: > >> On 2020-Jul-13, at 12:03, John-Mark Gurney wrote: >> >>> Mark Millard wrote this message on Mon, Jul 13, 2020 at 00:44 -0700: On 2020-Jul-12, at 21:51, John-Mark Gurney wrote: > . . . Hmm. I only seem to be able to find one type. Its been a while since I've used the other and I do not know where it is at. For what I found: ugen0.2: at usbus0 axge0 on uhub0 axge0: on usbus0 miibus1: on axge0 rgephy0: PHY 3 on miibus1 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow (I have access to more than one instance of the above.) >>> >>> Yeah, these are the ones that are known to not be able to get close >>> to gige speeds, unlike the RealTek one that I am using now... >> >> Hmm, in one direction anyway? >> >> NetBSD current testing on a RPi4 for >> iperf3 -R -c 192.168.1.120 -B 192.168.1.140 : >> >> Server listening on 5201 >> --- >> Accepted connection from 192.168.1.140, port 65525 >> [ 5] local 192.168.1.120 port 5201 connected to 192.168.1.140 port 65524 >> [ ID] Interval Transfer Bitrate Retr Cwnd >> [ 5] 0.00-1.00 sec 33.7 MBytes 282 Mbits/sec0 33.9 KBytes >> >> [ 5] 1.00-2.00 sec 96.0 MBytes 805 Mbits/sec2 48.9 KBytes >> >> [ 5] 2.00-3.00 sec 111 MBytes 930 Mbits/sec 12 81.9 KBytes >> >> [ 5] 3.00-4.00 sec 83.8 MBytes 703 Mbits/sec 18114 KBytes >> >> [ 5] 4.00-5.00 sec 83.7 MBytes 702 Mbits/sec 42145 KBytes >> >> [ 5] 5.00-6.00 sec 84.8 MBytes 712 Mbits/sec 50178 KBytes >> >> [ 5] 6.00-7.00 sec 111 MBytes 929 Mbits/sec 40194 KBytes >> >> [ 5] 7.00-8.00 sec 83.6 MBytes 701 Mbits/sec 40194 KBytes >> >> [ 5] 8.00-9.00 sec 111 MBytes 930 Mbits/sec 47194 KBytes >> >> [ 5] 9.00-10.00 sec 111 MBytes 927 Mbits/sec 50193 KBytes >> >> [ 5] 10.00-10.62 sec 68.4 MBytes 929 Mbits/sec 46193 KBytes >> >> - - - - - - - - - - - - - - - - - - - - - - - - - >> [ ID] Interval Transfer Bitrate Retr >> [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender >> >> and as seen on the receiver: >> >> # iperf3 -R -c 192.168.1.120 -B 192.168.1.140 >> Connecting to host 192.168.1.120, port 5201 >> Reverse mode, remote host 192.168.1.120 is sending >> [ 5] local 192.168.1.140 port 65524 connected to 192.168.1.120 port 5201 >> [ ID] Interval Transfer Bitrate >> [ 5] 0.00-1.00 sec 87.8 MBytes 736 Mbits/sec >> [ 5] 1.00-2.00 sec 110 MBytes 924 Mbits/sec >> [ 5] 2.00-3.00 sec 83.7 MBytes 702 Mbits/sec >> [ 5] 3.00-4.00 sec 83.6 MBytes 701 Mbits/sec >> [ 5] 4.00-5.00 sec 84.8 MBytes 711 Mbits/sec >> [ 5] 5.00-6.00 sec 111 MBytes 931 Mbits/sec >> [ 5] 6.00-7.00 sec 83.4 MBytes 700 Mbits/sec >> [ 5] 7.00-8.00 sec 111 MBytes 930 Mbits/sec >> [ 5] 8.00-9.00 sec 111 MBytes 929 Mbits/sec >> [ 5] 9.00-10.00 sec 111 MBytes 929 Mbits/sec >> - - - - - - - - - - - - - - - - - - - - - - - - - >> [ ID] Interval Transfer Bitrate Retr >> [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender >> [ 5] 0.00-10.00 sec 977 MBytes 819 Mbits/sec >> receiver >> >> This is faster than the built-in EtherNet results. >> (But the built-in is also USB based.) > > The built-in EtherNet does not show in usbdevs output. > I got the context wrong for the ()'d note. > >> As for iperf3 -c 192.168.1.120 -B 192.168.1.140 it is >> slower: >> >> Connecting to host 192.168.1.120, port 5201 >> [ 5] local 192.168.1.140 port 65526 connected to 192.168.1.120 port 5201 >> [ ID] Interval Transfer Bitrate Retr Cwnd >> [ 5] 0.00-1.00 sec 62.5 MBytes 522 Mbits/sec0 4.00 MBytes >> >> [ 5] 1.00-2.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes >> >> [ 5] 2.01-3.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes >> >> [ 5] 3.01-4.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes >> >> [ 5] 4.01-5.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes >> >> [ 5] 5.01-6.01 sec 62.5 MBytes 523 Mbits/sec0 4.00 MBytes >> >> [ 5] 6.01-7.01 sec 62.5 MBytes
Re: slow USB 3.0 on -current
[Just a correction to a side comment.] On 2020-Jul-13, at 12:46, Mark Millard wrote: > On 2020-Jul-13, at 12:03, John-Mark Gurney wrote: > >> Mark Millard wrote this message on Mon, Jul 13, 2020 at 00:44 -0700: >>> On 2020-Jul-12, at 21:51, John-Mark Gurney wrote: >>> . . . >>> >>> Hmm. I only seem to be able to find one type. Its been a >>> while since I've used the other and I do not know where >>> it is at. For what I found: >>> >>> ugen0.2: at usbus0 >>> axge0 on uhub0 >>> axge0: on usbus0 >>> miibus1: on axge0 >>> rgephy0: PHY 3 on miibus1 >>> rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, >>> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, >>> 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow >>> >>> (I have access to more than one instance of the above.) >> >> Yeah, these are the ones that are known to not be able to get close >> to gige speeds, unlike the RealTek one that I am using now... > > Hmm, in one direction anyway? > > NetBSD current testing on a RPi4 for > iperf3 -R -c 192.168.1.120 -B 192.168.1.140 : > > Server listening on 5201 > --- > Accepted connection from 192.168.1.140, port 65525 > [ 5] local 192.168.1.120 port 5201 connected to 192.168.1.140 port 65524 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 33.7 MBytes 282 Mbits/sec0 33.9 KBytes > [ 5] 1.00-2.00 sec 96.0 MBytes 805 Mbits/sec2 48.9 KBytes > [ 5] 2.00-3.00 sec 111 MBytes 930 Mbits/sec 12 81.9 KBytes > [ 5] 3.00-4.00 sec 83.8 MBytes 703 Mbits/sec 18114 KBytes > [ 5] 4.00-5.00 sec 83.7 MBytes 702 Mbits/sec 42145 KBytes > [ 5] 5.00-6.00 sec 84.8 MBytes 712 Mbits/sec 50178 KBytes > [ 5] 6.00-7.00 sec 111 MBytes 929 Mbits/sec 40194 KBytes > [ 5] 7.00-8.00 sec 83.6 MBytes 701 Mbits/sec 40194 KBytes > [ 5] 8.00-9.00 sec 111 MBytes 930 Mbits/sec 47194 KBytes > [ 5] 9.00-10.00 sec 111 MBytes 927 Mbits/sec 50193 KBytes > [ 5] 10.00-10.62 sec 68.4 MBytes 929 Mbits/sec 46193 KBytes > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender > > and as seen on the receiver: > > # iperf3 -R -c 192.168.1.120 -B 192.168.1.140 > Connecting to host 192.168.1.120, port 5201 > Reverse mode, remote host 192.168.1.120 is sending > [ 5] local 192.168.1.140 port 65524 connected to 192.168.1.120 port 5201 > [ ID] Interval Transfer Bitrate > [ 5] 0.00-1.00 sec 87.8 MBytes 736 Mbits/sec > [ 5] 1.00-2.00 sec 110 MBytes 924 Mbits/sec > [ 5] 2.00-3.00 sec 83.7 MBytes 702 Mbits/sec > [ 5] 3.00-4.00 sec 83.6 MBytes 701 Mbits/sec > [ 5] 4.00-5.00 sec 84.8 MBytes 711 Mbits/sec > [ 5] 5.00-6.00 sec 111 MBytes 931 Mbits/sec > [ 5] 6.00-7.00 sec 83.4 MBytes 700 Mbits/sec > [ 5] 7.00-8.00 sec 111 MBytes 930 Mbits/sec > [ 5] 8.00-9.00 sec 111 MBytes 929 Mbits/sec > [ 5] 9.00-10.00 sec 111 MBytes 929 Mbits/sec > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender > [ 5] 0.00-10.00 sec 977 MBytes 819 Mbits/sec receiver > > This is faster than the built-in EtherNet results. > (But the built-in is also USB based.) The built-in EtherNet does not show in usbdevs output. I got the context wrong for the ()'d note. > As for iperf3 -c 192.168.1.120 -B 192.168.1.140 it is > slower: > > Connecting to host 192.168.1.120, port 5201 > [ 5] local 192.168.1.140 port 65526 connected to 192.168.1.120 port 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 62.5 MBytes 522 Mbits/sec0 4.00 MBytes > [ 5] 1.00-2.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes > [ 5] 2.01-3.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes > [ 5] 3.01-4.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes > [ 5] 4.01-5.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes > [ 5] 5.01-6.01 sec 62.5 MBytes 523 Mbits/sec0 4.00 MBytes > [ 5] 6.01-7.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes > [ 5] 7.01-8.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes > [ 5] 8.01-9.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes > [ 5] 9.01-10.0
Re: slow USB 3.0 on -current
On 2020-Jul-13, at 12:03, John-Mark Gurney wrote: > Mark Millard wrote this message on Mon, Jul 13, 2020 at 00:44 -0700: >> On 2020-Jul-12, at 21:51, John-Mark Gurney wrote: >> >>> . . . >> >> Hmm. I only seem to be able to find one type. Its been a >> while since I've used the other and I do not know where >> it is at. For what I found: >> >> ugen0.2: at usbus0 >> axge0 on uhub0 >> axge0: on usbus0 >> miibus1: on axge0 >> rgephy0: PHY 3 on miibus1 >> rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, >> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, >> 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow >> >> (I have access to more than one instance of the above.) > > Yeah, these are the ones that are known to not be able to get close > to gige speeds, unlike the RealTek one that I am using now... Hmm, in one direction anyway? NetBSD current testing on a RPi4 for iperf3 -R -c 192.168.1.120 -B 192.168.1.140 : Server listening on 5201 --- Accepted connection from 192.168.1.140, port 65525 [ 5] local 192.168.1.120 port 5201 connected to 192.168.1.140 port 65524 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 33.7 MBytes 282 Mbits/sec0 33.9 KBytes [ 5] 1.00-2.00 sec 96.0 MBytes 805 Mbits/sec2 48.9 KBytes [ 5] 2.00-3.00 sec 111 MBytes 930 Mbits/sec 12 81.9 KBytes [ 5] 3.00-4.00 sec 83.8 MBytes 703 Mbits/sec 18114 KBytes [ 5] 4.00-5.00 sec 83.7 MBytes 702 Mbits/sec 42145 KBytes [ 5] 5.00-6.00 sec 84.8 MBytes 712 Mbits/sec 50178 KBytes [ 5] 6.00-7.00 sec 111 MBytes 929 Mbits/sec 40194 KBytes [ 5] 7.00-8.00 sec 83.6 MBytes 701 Mbits/sec 40194 KBytes [ 5] 8.00-9.00 sec 111 MBytes 930 Mbits/sec 47194 KBytes [ 5] 9.00-10.00 sec 111 MBytes 927 Mbits/sec 50193 KBytes [ 5] 10.00-10.62 sec 68.4 MBytes 929 Mbits/sec 46193 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender and as seen on the receiver: # iperf3 -R -c 192.168.1.120 -B 192.168.1.140 Connecting to host 192.168.1.120, port 5201 Reverse mode, remote host 192.168.1.120 is sending [ 5] local 192.168.1.140 port 65524 connected to 192.168.1.120 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 87.8 MBytes 736 Mbits/sec [ 5] 1.00-2.00 sec 110 MBytes 924 Mbits/sec [ 5] 2.00-3.00 sec 83.7 MBytes 702 Mbits/sec [ 5] 3.00-4.00 sec 83.6 MBytes 701 Mbits/sec [ 5] 4.00-5.00 sec 84.8 MBytes 711 Mbits/sec [ 5] 5.00-6.00 sec 111 MBytes 931 Mbits/sec [ 5] 6.00-7.00 sec 83.4 MBytes 700 Mbits/sec [ 5] 7.00-8.00 sec 111 MBytes 930 Mbits/sec [ 5] 8.00-9.00 sec 111 MBytes 929 Mbits/sec [ 5] 9.00-10.00 sec 111 MBytes 929 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.62 sec 977 MBytes 772 Mbits/sec 347 sender [ 5] 0.00-10.00 sec 977 MBytes 819 Mbits/sec receiver This is faster than the built-in EtherNet results. (But the built-in is also USB based.) As for iperf3 -c 192.168.1.120 -B 192.168.1.140 it is slower: Connecting to host 192.168.1.120, port 5201 [ 5] local 192.168.1.140 port 65526 connected to 192.168.1.120 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 62.5 MBytes 522 Mbits/sec0 4.00 MBytes [ 5] 1.00-2.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes [ 5] 2.01-3.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes [ 5] 3.01-4.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes [ 5] 4.01-5.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes [ 5] 5.01-6.01 sec 62.5 MBytes 523 Mbits/sec0 4.00 MBytes [ 5] 6.01-7.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes [ 5] 7.01-8.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes [ 5] 8.01-9.01 sec 62.5 MBytes 524 Mbits/sec0 4.00 MBytes [ 5] 9.01-10.01 sec 62.5 MBytes 525 Mbits/sec0 4.00 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 625 MBytes 524 Mbits/sec0 sender [ 5] 0.00-10.62 sec 625 MBytes 494 Mbits/sec receiver This is again
Re: slow USB 3.0 on -current
Hans Petter Selasky wrote this message on Mon, Jul 13, 2020 at 10:50 +0200: > On 2020-07-13 03:02, John-Mark Gurney wrote: > > MB means megabytes.. I would use Mbps for bits... so, on Win10 and > > NetBSD, I'm able to get 100 MBytes/sec on Win10/NetBSD, and FreeBSD, > > I'm only getting a tenth the capability of gige at 9-10 MBytes/sec... > > > > I'll note that fetch reports numbers of MBps, which is one of the tools > > I've been using for testing. > > Could you have a look at the traffic pattern, when using iperf? > > usbdump -i usbusX -f Y > > Where X and Y are the numbers after ugen . > > Many of the network USB drivers are single buffered, because that's what > older USB host controllers support. Then the IRQ rate 8000 for USB > 2.0/3.0 and 1000 for USB 1.0, limits the number of packets per second. Hmm... now that I do the math, that sounds very likely what the problem is: 8000 int/s * 1480 bytes/int * 8 bits/byte /1000/1000 == 94.72 Mbps add in the delay to swap buffers... and this is very close to the speed that I'm seeing... I wasn't sure what to look for, but the output is here: https://www.funkthat.com/~jmg/FreeBSD/usb.a78/usbdump.0.4.txt.xz Also, the output does not match what the man page says.. It implies that OUT or IN, but I'm seeing SUBM and DONE instead, and the delimiters between the feels don't make sense... This was running: gold,pts,/home/jmg,521$iperf3 -b 240m -u -c 192.168.0.80 Connecting to host 192.168.0.80, port 5201 [ 5] local 192.168.0.2 port 65117 connected to 192.168.0.80 port 5201 [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 28.6 MBytes 240 Mbits/sec 20531 [ 5] 1.00-2.00 sec 28.6 MBytes 240 Mbits/sec 20548 [ 5] 2.00-3.00 sec 28.6 MBytes 240 Mbits/sec 20550 [ 5] 3.00-4.00 sec 28.6 MBytes 240 Mbits/sec 20546 [ 5] 4.00-5.00 sec 28.6 MBytes 240 Mbits/sec 20551 [ 5] 5.00-6.00 sec 28.6 MBytes 240 Mbits/sec 20545 [ 5] 6.00-7.00 sec 28.6 MBytes 240 Mbits/sec 20548 [ 5] 7.00-8.01 sec 28.1 MBytes 234 Mbits/sec 20175 [ 5] 8.01-9.00 sec 29.1 MBytes 246 Mbits/sec 20921 [ 5] 9.00-10.00 sec 28.6 MBytes 240 Mbits/sec 20548 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate JitterLost/Total Datagrams [ 5] 0.00-10.00 sec 286 MBytes 240 Mbits/sec 0.000 ms 0/205463 (0%) sender [ 5] 0.00-10.35 sec 107 MBytes 87.1 Mbits/sec 0.172 ms 128298/205436 (62%) receiver Which is trying to send 240Mbps UDP traffic to the USB3 ethernet machine, and the machine only receives the usual 91Mbps... I have also published: https://www.funkthat.com/~jmg/FreeBSD/usb.a78/umass.debug.txt.xz Which shows the umass issue that I've been having where any umass device on this system almost never attaches... This was takes w/ hw.usb.umass.debug=-1 hw.usb.xhci.debug=17 I set those sysctl's, then attached the umass device (as USB3.0 SD card reader), waited for the five retries.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: slow USB 3.0 on -current
Mark Millard wrote this message on Mon, Jul 13, 2020 at 00:44 -0700: > On 2020-Jul-12, at 21:51, John-Mark Gurney wrote: > > > Mark Millard wrote this message on Sun, Jul 12, 2020 at 18:26 -0700: > >> John-Mark Gurney jmg at funkthat.com wrote on > >> Sat Jul 11 22:44:36 UTC 2020 : > >> > >>> I'm having issues getting good ethernet performance from a USB ethernet > >>> adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > >>> AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > >>> > >>> Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > >>> adapter only gets around 10MB/sec performance. During the transfer, > >>> the CPU usage is only around 3-5%, so it's definitely not CPU bound. > >>> > >>> I have tested Windows 10 and NetBSD 9.0 performance, and both provide > >>> 100MB/sec+ w/o troubles. > >>> > >>> I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > >>> > >>> Any hints on how to fix this? > >>> > >>> This may be related, but I'm also having issues w/ booting when I have > >>> both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > >>> > >>> If I move the SD card reader to USB 2.0, the umass device will attach > >>> and work. I have also attached a clip of the dmesg from that > >>> happening. > >>> > >>> Has anyone else seen this issue? Ideas or thoughts on how to resolve > >>> the performance issues? > >> > >> It might prove useful to use iperf3 with > >> > >> # iperf3 -s > >> > >> on one machine and doing > >> > >> # iperf3 -c ADDR > >> . . . > >> # iperf3 -R -c ADDR > >> . . . > >> > >> on the other. (That last swaps the > >> sender/receiver status.) > >> > >> All 3 commands will have output. The > >> -s one will produce output for each of > >> the -c ones. > >> > >> The outputs for the sender(s) will include Cwnd > >> (congestion window size) information that may > >> be relevant. It will report bit rate and > >> retry count sampling (and overall figures). [...] > The "iperf3 -s" should have had output with the Cwnd > figures for the "Reverse mode" case above (and the > distribution for the 1381 Retr total). They might > not match when the earlier figures that you did report > for the non-Reverse mode. If you can tell how the Cwnd figures would help you figure out how to make the USB3 bus run faster, I'll spend the time to retest and give you the numbers, but I don't see how they can... [...] > > As you can see, both match approximately what I measured other methods, > > so, it's definitely not the way I measured performance. > > > >> My observation would be that neither type > >> of USB3 Ethernet adapter that I've tried > > > > What is the chipset that you tried? One of the earlier ones that I > > tried was an axe iirc, and was limited to around 500Mbps or so... > > Hmm. I only seem to be able to find one type. Its been a > while since I've used the other and I do not know where > it is at. For what I found: > > ugen0.2: at usbus0 > axge0 on uhub0 > axge0: on usbus0 > miibus1: on axge0 > rgephy0: PHY 3 on miibus1 > rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, > 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow > > (I have access to more than one instance of the above.) Yeah, these are the ones that are known to not be able to get close to gige speeds, unlike the RealTek one that I am using now... I forgot that axge is the gigabit version of axe... > The iperf3 output that I reported was for using > of of the above. Note that when the USB3 EtherNet > was reciveing Cwnd was reported as 29.8 KBytes > or smaller for the example run, much like your > output reporting 34.4 KBytes or less for the > example run. They grew to match the speeds that the link could do.. > This may suggest some common constraint across various > USB3 EtherNet devices. The Cwnd figures are probably > too small to get near 900 Mbit/s+. As you can see, the NetBSD results was able to grow the Cwnd large enough to obtain performance... The stats that I provided were from the non-USB3 machine, and for tx'ing to matches the issue I raised in the original post... I could provide the Cwnd, but I don't see how that will debug a USB3 speed issue... The stats show that the Cwnd can grow on other OS's (NetBSD), and on wired (bge) fine. > But, even with a (smaller but) similar Cwnd figure > my example was getting faster transfers than your > example. I got smaller Retr figures as well. It > leaves me wondering if there are packets being > rejected in your context that are not in my > context. ping times to the machine via USB3 is higher than native gige, but that isn't too surprising due to the extra latency introduced by them.. it's: round-trip min/avg/max/stddev = 0.743/0.826/0.963/0.074 ms Where as to a slower machine (PINE A64-LTS, arm64) with a couple extra switches in between: round-trip min/avg/ma
Re: slow USB 3.0 on -current
On 2020-Jul-12, at 21:51, John-Mark Gurney wrote: > Mark Millard wrote this message on Sun, Jul 12, 2020 at 18:26 -0700: >> John-Mark Gurney jmg at funkthat.com wrote on >> Sat Jul 11 22:44:36 UTC 2020 : >> >>> I'm having issues getting good ethernet performance from a USB ethernet >>> adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an >>> AMD PRO A10-8700B based system using the AMD A78 FCH chipset. >>> >>> Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB >>> adapter only gets around 10MB/sec performance. During the transfer, >>> the CPU usage is only around 3-5%, so it's definitely not CPU bound. >>> >>> I have tested Windows 10 and NetBSD 9.0 performance, and both provide >>> 100MB/sec+ w/o troubles. >>> >>> I have attached dmesg from both FreeBSD -current and NetBSD 9.0. >>> >>> Any hints on how to fix this? >>> >>> This may be related, but I'm also having issues w/ booting when I have >>> both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. >>> >>> If I move the SD card reader to USB 2.0, the umass device will attach >>> and work. I have also attached a clip of the dmesg from that >>> happening. >>> >>> Has anyone else seen this issue? Ideas or thoughts on how to resolve >>> the performance issues? >> >> It might prove useful to use iperf3 with >> >> # iperf3 -s >> >> on one machine and doing >> >> # iperf3 -c ADDR >> . . . >> # iperf3 -R -c ADDR >> . . . >> >> on the other. (That last swaps the >> sender/receiver status.) >> >> All 3 commands will have output. The >> -s one will produce output for each of >> the -c ones. >> >> The outputs for the sender(s) will include Cwnd >> (congestion window size) information that may >> be relevant. It will report bit rate and >> retry count sampling (and overall figures). > > Here is the results for FreeBSD w/ USB3 ure. .80 is the USB3 > adapter side: > gold,pts,/home/jmg,502$iperf3 -c 192.168.0.80 > Connecting to host 192.168.0.80, port 5201 > [ 5] local 192.168.0.2 port 50042 connected to 192.168.0.80 port 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 8.94 MBytes 75.0 Mbits/sec 931 15.5 KBytes > [ 5] 1.00-2.00 sec 9.98 MBytes 83.7 Mbits/sec 919 27.3 KBytes > [ 5] 2.00-3.00 sec 9.95 MBytes 83.5 Mbits/sec 954 5.71 KBytes > [ 5] 3.00-4.00 sec 9.97 MBytes 83.7 Mbits/sec 939 28.7 KBytes > [ 5] 4.00-5.00 sec 9.97 MBytes 83.6 Mbits/sec 951 17.3 KBytes > [ 5] 5.00-6.00 sec 9.99 MBytes 83.8 Mbits/sec 913 31.5 KBytes > [ 5] 6.00-7.00 sec 9.96 MBytes 83.5 Mbits/sec 956 20.1 KBytes > [ 5] 7.00-8.00 sec 10.0 MBytes 83.9 Mbits/sec 913 33.0 KBytes > [ 5] 8.00-9.00 sec 9.97 MBytes 83.6 Mbits/sec 945 24.4 KBytes > [ 5] 9.00-10.00 sec 9.99 MBytes 83.8 Mbits/sec 916 34.4 KBytes > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.00 sec 98.7 MBytes 82.8 Mbits/sec 9337 sender > [ 5] 0.00-10.25 sec 98.7 MBytes 80.8 Mbits/sec receiver > > iperf Done. > gold,pts,/home/jmg,503$iperf3 -R -c 192.168.0.80 > Connecting to host 192.168.0.80, port 5201 > Reverse mode, remote host 192.168.0.80 is sending > [ 5] local 192.168.0.2 port 51024 connected to 192.168.0.80 port 5201 > [ ID] Interval Transfer Bitrate > [ 5] 0.00-1.00 sec 9.69 MBytes 81.3 Mbits/sec > [ 5] 1.00-2.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 2.00-3.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 3.00-4.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 4.00-5.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 5.00-6.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 6.00-7.00 sec 10.7 MBytes 89.8 Mbits/sec > [ 5] 7.00-8.00 sec 10.4 MBytes 87.6 Mbits/sec > [ 5] 8.00-9.00 sec 10.7 MBytes 89.9 Mbits/sec > [ 5] 9.00-10.00 sec 10.7 MBytes 89.8 Mbits/sec > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.00 sec 106 MBytes 88.9 Mbits/sec 1381 sender > [ 5] 0.00-10.00 sec 106 MBytes 88.7 Mbits/sec receiver > > iperf Done. The "iperf3 -s" should have had output with the Cwnd figures for the "Reverse mode" case above (and the distribution for the 1381 Retr total). They might not match when the earlier figures that you did report for the non-Reverse mode. > As you can see, it matches what I measured earlier. > > And just to prove that the machine CAN move 100MB/sec, I've run iperf3 > using the onboard wired ethernet... I need multiple interfaces, which is > why I'm bothering trying to get USB3 ethernet working. > > This is using the onboard bge interface. It's IP is .79: > gold,pts,/home/jmg,507$iperf3 -c 192.168.0.79 > Connecting to host 192.168.0.79, port 5201 > [ 5] local 192.168.0.2 port 61500 connected to 192.168.
Re: slow USB 3.0 on -current
On 2020-07-13 03:02, John-Mark Gurney wrote: MB means megabytes.. I would use Mbps for bits... so, on Win10 and NetBSD, I'm able to get 100 MBytes/sec on Win10/NetBSD, and FreeBSD, I'm only getting a tenth the capability of gige at 9-10 MBytes/sec... I'll note that fetch reports numbers of MBps, which is one of the tools I've been using for testing. Hi, Could you have a look at the traffic pattern, when using iperf? usbdump -i usbusX -f Y Where X and Y are the numbers after ugen . Many of the network USB drivers are single buffered, because that's what older USB host controllers support. Then the IRQ rate 8000 for USB 2.0/3.0 and 1000 for USB 1.0, limits the number of packets per second. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: slow USB 3.0 on -current
John-Mark Gurney jmg at funkthat.com wrote on Sat Jul 11 22:44:36 UTC 2020 : > I'm having issues getting good ethernet performance from a USB ethernet > adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > > Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > adapter only gets around 10MB/sec performance. During the transfer, > the CPU usage is only around 3-5%, so it's definitely not CPU bound. > > I have tested Windows 10 and NetBSD 9.0 performance, and both provide > 100MB/sec+ w/o troubles. > > I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > > Any hints on how to fix this? > > This may be related, but I'm also having issues w/ booting when I have > both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > > If I move the SD card reader to USB 2.0, the umass device will attach > and work. I have also attached a clip of the dmesg from that > happening. > > Has anyone else seen this issue? Ideas or thoughts on how to resolve > the performance issues? > It might prove useful to use iperf3 with # iperf3 -s on one machine and doing # iperf3 -c ADDR . . . # iperf3 -R -c ADDR . . . on the other. (That last swaps the sender/receiver status.) All 3 commands will have output. The -s one will produce output for each of the -c ones. The outputs for the sender(s) will include Cwnd (congestion window size) information that may be relevant. It will report bit rate and retry count sampling (and overall figures). Comparing the output of using iperf3 under NetBSD 9.0 or Windows 10 could be instructive. My observation would be that neither type of USB3 Ethernet adapter that I've tried (different chipsets) get anywhere near 100 MByte/s when ifconfig reports 1000baseT . The Cwnd figures are smaller than for the built-in Ethernets that manage much faster overall transfer rates. Example where 192.168.1.112 has the USB3 EtherNet based adapter in use and 192.168.1.120 has built-in EtherNet that can do 900 Mbit/s+ on the network: # iperf3 -s --- Server listening on 5201 --- Accepted connection from 192.168.1.112, port 20519 [ 5] local 192.168.1.120 port 5201 connected to 192.168.1.112 port 44212 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 23.8 MBytes 200 Mbits/sec [ 5] 1.00-2.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 2.00-3.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 3.00-4.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 4.00-5.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 5.00-6.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 6.00-7.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 7.00-8.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 8.00-9.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 9.00-10.00 sec 27.6 MBytes 232 Mbits/sec [ 5] 10.00-10.19 sec 5.13 MBytes 231 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.19 sec 277 MBytes 228 Mbits/sec receiver --- Server listening on 5201 --- Accepted connection from 192.168.1.112, port 18711 [ 5] local 192.168.1.120 port 5201 connected to 192.168.1.112 port 48624 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 22.5 MBytes 188 Mbits/sec 273 17.0 KBytes [ 5] 1.00-2.00 sec 19.0 MBytes 159 Mbits/sec 214 14.3 KBytes [ 5] 2.00-3.00 sec 22.6 MBytes 190 Mbits/sec 271 29.8 KBytes [ 5] 3.00-4.00 sec 10.6 MBytes 88.9 Mbits/sec 131 28.4 KBytes [ 5] 4.00-5.00 sec 28.2 MBytes 237 Mbits/sec 343 17.0 KBytes [ 5] 5.00-6.01 sec 25.7 MBytes 214 Mbits/sec 310 14.3 KBytes [ 5] 6.01-7.00 sec 15.4 MBytes 130 Mbits/sec 178 19.8 KBytes [ 5] 7.00-8.00 sec 20.6 MBytes 173 Mbits/sec 229 21.3 KBytes [ 5] 8.00-9.00 sec 29.8 MBytes 250 Mbits/sec 345 19.8 KBytes [ 5] 9.00-10.00 sec 29.9 MBytes 251 Mbits/sec 325 17.0 KBytes [ 5] 10.00-10.19 sec 7.54 MBytes 332 Mbits/sec 89 2.83 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.19 sec 232 MBytes 191 Mbits/sec 2708 sender --- Server listening on 5201 --- # iperf3 -c 192.168.1.120 Connecting to host 192.168.1.120, port 5201 [ 5]
Re: slow USB 3.0 on -current
Mark Millard wrote this message on Sun, Jul 12, 2020 at 18:26 -0700: > John-Mark Gurney jmg at funkthat.com wrote on > Sat Jul 11 22:44:36 UTC 2020 : > > > I'm having issues getting good ethernet performance from a USB ethernet > > adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > > AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > > > > Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > > adapter only gets around 10MB/sec performance. During the transfer, > > the CPU usage is only around 3-5%, so it's definitely not CPU bound. > > > > I have tested Windows 10 and NetBSD 9.0 performance, and both provide > > 100MB/sec+ w/o troubles. > > > > I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > > > > Any hints on how to fix this? > > > > This may be related, but I'm also having issues w/ booting when I have > > both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > > > > If I move the SD card reader to USB 2.0, the umass device will attach > > and work. I have also attached a clip of the dmesg from that > > happening. > > > > Has anyone else seen this issue? Ideas or thoughts on how to resolve > > the performance issues? > > It might prove useful to use iperf3 with > > # iperf3 -s > > on one machine and doing > > # iperf3 -c ADDR > . . . > # iperf3 -R -c ADDR > . . . > > on the other. (That last swaps the > sender/receiver status.) > > All 3 commands will have output. The > -s one will produce output for each of > the -c ones. > > The outputs for the sender(s) will include Cwnd > (congestion window size) information that may > be relevant. It will report bit rate and > retry count sampling (and overall figures). Here is the results for FreeBSD w/ USB3 ure. .80 is the USB3 adapter side: gold,pts,/home/jmg,502$iperf3 -c 192.168.0.80 Connecting to host 192.168.0.80, port 5201 [ 5] local 192.168.0.2 port 50042 connected to 192.168.0.80 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 8.94 MBytes 75.0 Mbits/sec 931 15.5 KBytes [ 5] 1.00-2.00 sec 9.98 MBytes 83.7 Mbits/sec 919 27.3 KBytes [ 5] 2.00-3.00 sec 9.95 MBytes 83.5 Mbits/sec 954 5.71 KBytes [ 5] 3.00-4.00 sec 9.97 MBytes 83.7 Mbits/sec 939 28.7 KBytes [ 5] 4.00-5.00 sec 9.97 MBytes 83.6 Mbits/sec 951 17.3 KBytes [ 5] 5.00-6.00 sec 9.99 MBytes 83.8 Mbits/sec 913 31.5 KBytes [ 5] 6.00-7.00 sec 9.96 MBytes 83.5 Mbits/sec 956 20.1 KBytes [ 5] 7.00-8.00 sec 10.0 MBytes 83.9 Mbits/sec 913 33.0 KBytes [ 5] 8.00-9.00 sec 9.97 MBytes 83.6 Mbits/sec 945 24.4 KBytes [ 5] 9.00-10.00 sec 9.99 MBytes 83.8 Mbits/sec 916 34.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 98.7 MBytes 82.8 Mbits/sec 9337 sender [ 5] 0.00-10.25 sec 98.7 MBytes 80.8 Mbits/sec receiver iperf Done. gold,pts,/home/jmg,503$iperf3 -R -c 192.168.0.80 Connecting to host 192.168.0.80, port 5201 Reverse mode, remote host 192.168.0.80 is sending [ 5] local 192.168.0.2 port 51024 connected to 192.168.0.80 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 9.69 MBytes 81.3 Mbits/sec [ 5] 1.00-2.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 2.00-3.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 3.00-4.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 4.00-5.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 5.00-6.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 6.00-7.00 sec 10.7 MBytes 89.8 Mbits/sec [ 5] 7.00-8.00 sec 10.4 MBytes 87.6 Mbits/sec [ 5] 8.00-9.00 sec 10.7 MBytes 89.9 Mbits/sec [ 5] 9.00-10.00 sec 10.7 MBytes 89.8 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 106 MBytes 88.9 Mbits/sec 1381 sender [ 5] 0.00-10.00 sec 106 MBytes 88.7 Mbits/sec receiver iperf Done. As you can see, it matches what I measured earlier. And just to prove that the machine CAN move 100MB/sec, I've run iperf3 using the onboard wired ethernet... I need multiple interfaces, which is why I'm bothering trying to get USB3 ethernet working. This is using the onboard bge interface. It's IP is .79: gold,pts,/home/jmg,507$iperf3 -c 192.168.0.79 Connecting to host 192.168.0.79, port 5201 [ 5] local 192.168.0.2 port 61500 connected to 192.168.0.79 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 101 MBytes 850 Mbits/sec0488 KBytes [ 5] 1.00-2.00 sec 112 MBytes 940 Mbits/sec0488 KBytes [ 5] 2.00-3.00 sec 112 MBytes 943 Mbits/sec0731 KBytes [ 5] 3.00-4.00 sec 112 MBytes 940 Mbits/sec0731 KBytes [ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec0
Re: slow USB 3.0 on -current
Kevin Oberman wrote this message on Sun, Jul 12, 2020 at 16:24 -0700: > On Sun, Jul 12, 2020 at 2:55 PM John-Mark Gurney wrote: > > > Hans Petter Selasky wrote this message on Sun, Jul 12, 2020 at 09:57 +0200: > > > On 2020-07-12 00:44, John-Mark Gurney wrote: > > > > Hello, > > > > > > > > I'm having issues getting good ethernet performance from a USB ethernet > > > > adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > > > > AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > > > > > > > > Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > > > > adapter only gets around 10MB/sec performance. During the transfer, > > > > the CPU usage is only around 3-5%, so it's definitely not CPU bound. > > > > > > > > I have tested Windows 10 and NetBSD 9.0 performance, and both provide > > > > 100MB/sec+ w/o troubles. > > > > > > > > I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > > > > > > > > Any hints on how to fix this? > > > > > > > > This may be related, but I'm also having issues w/ booting when I have > > > > both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > > > > > > > > If I move the SD card reader to USB 2.0, the umass device will attach > > > > and work. I have also attached a clip of the dmesg from that > > > > happening. > > > > > > > > Has anyone else seen this issue? Ideas or thoughts on how to resolve > > > > the performance issues? > > > > > > Can you check the output from ifconfig. What is the actual link speed. I > > > suspect it has something to do with the MII bus code/implementation. > > > > ifconfig is reporting it's 1000baseT. > > > > > Also check output from "vmstat -i" during usage to see if the number of > > > IRQ/s is low. > > > > Not sure what is considered low, but I'm seeing consistently around > > 7800 int/s for xhci0. > > > This is just for clarification, but is 'MB' MBytes? In the networking world > that is what it would mean, but the context leads me to think that you mean > Mbits. It's also possible that some numbers are in bits and some in Bytes, > causing real confusion. I'm sure that 1000baseT is bits, of course. MB means megabytes.. I would use Mbps for bits... so, on Win10 and NetBSD, I'm able to get 100 MBytes/sec on Win10/NetBSD, and FreeBSD, I'm only getting a tenth the capability of gige at 9-10 MBytes/sec... I'll note that fetch reports numbers of MBps, which is one of the tools I've been using for testing. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: slow USB 3.0 on -current
On Sun, Jul 12, 2020 at 2:55 PM John-Mark Gurney wrote: > Hans Petter Selasky wrote this message on Sun, Jul 12, 2020 at 09:57 +0200: > > On 2020-07-12 00:44, John-Mark Gurney wrote: > > > Hello, > > > > > > I'm having issues getting good ethernet performance from a USB ethernet > > > adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > > > AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > > > > > > Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > > > adapter only gets around 10MB/sec performance. During the transfer, > > > the CPU usage is only around 3-5%, so it's definitely not CPU bound. > > > > > > I have tested Windows 10 and NetBSD 9.0 performance, and both provide > > > 100MB/sec+ w/o troubles. > > > > > > I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > > > > > > Any hints on how to fix this? > > > > > > This may be related, but I'm also having issues w/ booting when I have > > > both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > > > > > > If I move the SD card reader to USB 2.0, the umass device will attach > > > and work. I have also attached a clip of the dmesg from that > > > happening. > > > > > > Has anyone else seen this issue? Ideas or thoughts on how to resolve > > > the performance issues? > > > > Can you check the output from ifconfig. What is the actual link speed. I > > suspect it has something to do with the MII bus code/implementation. > > ifconfig is reporting it's 1000baseT. > > > Also check output from "vmstat -i" during usage to see if the number of > > IRQ/s is low. > > Not sure what is considered low, but I'm seeing consistently around > 7800 int/s for xhci0. > > -- > John-Mark Gurney Voice: +1 415 225 5579 > This is just for clarification, but is 'MB' MBytes? In the networking world that is what it would mean, but the context leads me to think that you mean Mbits. It's also possible that some numbers are in bits and some in Bytes, causing real confusion. I'm sure that 1000baseT is bits, of course. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: slow USB 3.0 on -current
Hans Petter Selasky wrote this message on Sun, Jul 12, 2020 at 09:57 +0200: > On 2020-07-12 00:44, John-Mark Gurney wrote: > > Hello, > > > > I'm having issues getting good ethernet performance from a USB ethernet > > adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an > > AMD PRO A10-8700B based system using the AMD A78 FCH chipset. > > > > Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB > > adapter only gets around 10MB/sec performance. During the transfer, > > the CPU usage is only around 3-5%, so it's definitely not CPU bound. > > > > I have tested Windows 10 and NetBSD 9.0 performance, and both provide > > 100MB/sec+ w/o troubles. > > > > I have attached dmesg from both FreeBSD -current and NetBSD 9.0. > > > > Any hints on how to fix this? > > > > This may be related, but I'm also having issues w/ booting when I have > > both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. > > > > If I move the SD card reader to USB 2.0, the umass device will attach > > and work. I have also attached a clip of the dmesg from that > > happening. > > > > Has anyone else seen this issue? Ideas or thoughts on how to resolve > > the performance issues? > > Can you check the output from ifconfig. What is the actual link speed. I > suspect it has something to do with the MII bus code/implementation. ifconfig is reporting it's 1000baseT. > Also check output from "vmstat -i" during usage to see if the number of > IRQ/s is low. Not sure what is considered low, but I'm seeing consistently around 7800 int/s for xhci0. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: slow USB 3.0 on -current
On 2020-07-12 00:44, John-Mark Gurney wrote: Hello, I'm having issues getting good ethernet performance from a USB ethernet adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an AMD PRO A10-8700B based system using the AMD A78 FCH chipset. Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB adapter only gets around 10MB/sec performance. During the transfer, the CPU usage is only around 3-5%, so it's definitely not CPU bound. I have tested Windows 10 and NetBSD 9.0 performance, and both provide 100MB/sec+ w/o troubles. I have attached dmesg from both FreeBSD -current and NetBSD 9.0. Any hints on how to fix this? This may be related, but I'm also having issues w/ booting when I have both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. If I move the SD card reader to USB 2.0, the umass device will attach and work. I have also attached a clip of the dmesg from that happening. Has anyone else seen this issue? Ideas or thoughts on how to resolve the performance issues? Hi, Can you check the output from ifconfig. What is the actual link speed. I suspect it has something to do with the MII bus code/implementation. Also check output from "vmstat -i" during usage to see if the number of IRQ/s is low. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
slow USB 3.0 on -current
Hello, I'm having issues getting good ethernet performance from a USB ethernet adapter (ure) under FreeBSD on an HP EliteDesk 705 G2 Mini[1]. It's an AMD PRO A10-8700B based system using the AMD A78 FCH chipset. Under FreeBSD -current (r362596), 12.1-R and 11.4-R, the RealTek USB adapter only gets around 10MB/sec performance. During the transfer, the CPU usage is only around 3-5%, so it's definitely not CPU bound. I have tested Windows 10 and NetBSD 9.0 performance, and both provide 100MB/sec+ w/o troubles. I have attached dmesg from both FreeBSD -current and NetBSD 9.0. Any hints on how to fix this? This may be related, but I'm also having issues w/ booting when I have both a SD USB 2.0 card reader AND the ure plugged into USB 3.0 ports. If I move the SD card reader to USB 2.0, the umass device will attach and work. I have also attached a clip of the dmesg from that happening. Has anyone else seen this issue? Ideas or thoughts on how to resolve the performance issues? Thanks. [1] https://support.hp.com/us-en/document/c04834953 -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ---<>--- Copyright (c) 1992-2020 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT #0 r362596: Thu Jun 25 05:02:51 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 10.0.1 (g...@github.com:llvm/llvm-project.git llvmorg-10.0.0-97-g6f71678ecd2) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 1024x768 CPU: AMD PRO A10-8700B R6, 10 Compute Cores 4C+6G(1796.67-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x660f01 Family=0x15 Model=0x60 Stepping=1 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x2febbfff,DBE,PTSC,MWAITX> Structured Extended Features=0x1a9 XSAVE Features=0x1 AMD Extended Feature Extensions ID EBX=0x1000 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8034414592 (7662 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" arc4random: WARNING: initial seeding bypassed the cryptographic random device because it was not yet seeded and the knob 'bypass_before_seeding' was enabled. ioapic0: MADT APIC ID 4 != hw id 0 ioapic1: MADT APIC ID 5 != hw id 0 ioapic0 irqs 0-23 ioapic1 irqs 24-55 Launching APs: 2 3 1 Timecounter "TSC" frequency 179782 Hz quality 1000 random: entropy device external interface WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0. kbd1 at kbdmux0 000.44 [4342] netmap_init netmap: loaded module [ath_hal] loaded nexus0 efirtc0: efirtc0: registered as a time-of-day clock, resolution 1.00s cryptosoft0: acpi0: acpi0: Power Button (fixed) cpu0: on acpi0 atrtc0: port 0x70-0x71 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.00s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.2 (no driver attached) vgapci0: port 0x2000-0x20ff mem 0xc000-0xc7ff,0xc800-0xc87f,0xc8b0-0xc8b3 irq 43 at device 1.0 on pci0 vgapci0: Boot video device hdac0: mem 0xc8b6-0xc8b63fff at device 1.1 on pci0 pcib1: at device 2.3 on pci0 pci1: on pcib1 bge0: mem 0xc882-0xc882,0xc881-0xc881,0xc880-0xc880 at device 0.0 on pci1 bge0: CHIP ID 0x05762100; ASIC REV 0x5762; CHIP REV 0x57621; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Using defaults for TSO: 65518/35/2048 bge0: Ethernet address: fc:3f:db:07:1c:f2 pci0: at device 8.0 (no driver attached) hdac1: mem 0xc8b64000-0xc8b67fff at device 9.2 on pci0 xhci0: mem 0xc8b68000-0xc8b69fff at device 16.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA xhci0: Unable to map MSI-X table usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ahci0: port 0x2118-0x211f,0x2124-0x2127,0x2110-
