On 16 March 2016 at 16:37, Dave Taht <dave.taht@xxxxxxxxx> wrote: > it is helpful to name the test files coherently in the flent tests, in > addition to using a directory structure and timestamp. It makes doing > comparison plots in data->add-other-open-data-files simpler. "-t > patched-mac-300mbps", for example. Sorry. I'm still trying to figure out what variables are worth considering for comparison purposes. > Also netperf from svn (maybe 2.7, don't remember) will restart udp_rr > after a packet loss in 250ms. Seeing a loss on UDP_RR and it stop for > a while is "ok". I'm using 2.6 straight out of debian repos so yeah. I guess I'll try using more recent netperf if I can't figure out the hiccups. Michał > Dave Täht > Let's go make home routers and wifi faster! With better software! > https://www.gofundme.com/savewifi > > > On Wed, Mar 16, 2016 at 3:26 AM, Michal Kazior <michal.kazior@xxxxxxxxx> wrote: >> On 16 March 2016 at 11:17, Michal Kazior <michal.kazior@xxxxxxxxx> wrote: >>> Hi, >>> >>> Most notable changes: >> [...] >>> * ath10k proof-of-concept that uses the new tx >>> scheduling (will post results in separate >>> email) >> >> I'm attaching a bunch of tests I've done using flent. They are all >> "burst" tests with burst-ports=1 and burst-length=2. The testing >> topology is: >> >> AP ----> STA >> AP )) (( STA >> [veth]--[br]--[wlan] )) (( [wlan] >> >> You can notice that in some tests plot data gets cut-off. There are 2 >> problems I've identified: >> - excess drops (not a problem with the patchset and can be seen when >> there's no codel-in-mac or scheduling isn't used) >> - UDP_RR hangs (apparently QCA99X0 I have hangs for a few hundred ms >> sometimes at times and doesn't Rx frames causing UDP_RR to stop >> mid-way; confirmed with logs and sniffer; I haven't figured out *why* >> exactly, could be some hw/fw quirk) >> >> Let me know if you have questions or comments regarding my testing/results. >> >> >> Michał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
