Date: Mon, 27 Jun 2016 15:40:25 -0300 From: =?UTF-8?B?T3RhY8OtbGlv?= <otacilio.neto@bsd.com.br> To: freebsd-current@freebsd.org Subject: Re: Bad rtwn(0) performance with RTL8188CE on -CURRENT after r302035 Message-ID: <30e70f37-c375-8bc0-45b9-7ea6db55c733@bsd.com.br> In-Reply-To: <20160627183454.GD28353@athena.sysfault.org> References: <20160627170619.GB28353@athena.sysfault.org> <bacdd981-d5a6-18c9-af35-55912237bd60@bsd.com.br> <CAJ-Vmo=FMEEc=T094k6sW4WW3KnjCL6OSarvT=QA2e38XofX_Q@mail.gmail.com> <20160627183454.GD28353@athena.sysfault.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 27/06/2016 15:34, Marcus von Appen escreveu: > On, Mon Jun 27, 2016, Adrian Chadd wrote: > >> Heh, there isn't any 11n support in rtwn (and won't be until I unify >> rtwn and urtwn post-11.) > I do not know about that. My experience from pre-r302035 were 1-2 Mbit/s > downstream from some servers, but often enough just for a minute or two > before everything stopped working. > >> I'll go find the rtwn NIC and see if I can figure out what's going on. > Let me know, if and how I can assist with it. > > Cheers > Marcus About everything stopping I have faced a problem similar to this. Bellow is a log of a session where the problem occurs. I'm testing using netperf. % netperf -H squitch MIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to squitch () port 0 AF_INET : histogram : interval : dirty data : demo Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 65536 32768 32768 14.03 0.02 shutdown_control: no response received errno 28 % ping squitch PING squitch (192.168.0.13): 56 data bytes ^C --- squitch ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss % urtwn0: device timeout urtwn0: device timeout
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30e70f37-c375-8bc0-45b9-7ea6db55c733>