Date: Mon, 13 Jul 2020 10:50:03 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Kevin Oberman <rkoberman@gmail.com>, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: slow USB 3.0 on -current Message-ID: <50d00b19-9e27-4d0f-f3d1-af0574687c14@selasky.org> In-Reply-To: <20200713010240.GJ4213@funkthat.com> References: <20200711224426.GC4213@funkthat.com> <b0053811-20c6-53d6-1197-6ae50a7033ce@selasky.org> <20200712215449.GI4213@funkthat.com> <CAN6yY1uigZ20jMF8ccN77CN2fsco%2BEJHeTRMDGH3jTv=Rff2=A@mail.gmail.com> <20200713010240.GJ4213@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50d00b19-9e27-4d0f-f3d1-af0574687c14>