From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 651A121F1BA for ; Sun, 6 Jul 2014 12:46:18 -0700 (PDT) Received: by mail-wi0-f169.google.com with SMTP id hi2so13802875wib.0 for ; Sun, 06 Jul 2014 12:46:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=nDrRsHpZwvAhRqKu1EGIkl6WHC3jLG/u1Ae21WXavhQ=; b=gqTeeuQH9zLQrwbDzKtYID/rIdL7SY0PuF6Fj6JWkRdxMswRaRzMDBpLEh7Zsc2U4B U3Dbsjf35jg92M2rQ3nTIVKXW96iMKmXtNWDl8WZvqQ2iOAAnjOzCiYOj0T22L42JcxY WG6pCtawMooXuIVlCoWlLFpmky4e0hHfS+MeE654yoZJyjStFKOTUeCnmj+EEwDzeC8A eJgN2LNp2uZsnS4z95RlMH/7qglefn7HDMIqm7pdpIKNCAOTr7lJfpbShahjoemeI2jp BS05T6F9D5/QXn7JnbmEqfEk3Rc76638awVfxEOlZMcacCmaX6B0UzWCbnwPhij8uZ7i H7dQ== X-Received: by 10.180.95.136 with SMTP id dk8mr1130448wib.8.1404675975711; Sun, 06 Jul 2014 12:46:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.217.55.1 with HTTP; Sun, 6 Jul 2014 12:45:55 -0700 (PDT) In-Reply-To: References: From: "R." Date: Sun, 6 Jul 2014 15:45:55 -0400 Message-ID: To: Dave Taht Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt-3.10.44-6 released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2014 19:46:18 -0000 All of my devices are connected on the 2.4 Ghz AP of a WNDR3800 running 3.10.44-6. Here's my feedback: + WiFi stability has improved in the sense that the AP no longer disappears= . - Latency spikes still exist. Huge latency lag comes in for up to a minute (can be seen in ping stats). It usually fixes itself within the minute. - Net connectivity can go out for up to a minute on all devices. It usually fixes itself within the minute. - "Failed to stop TX DMA, queues=3D0x004!" still occuring. Had 23 instances in the last 9 hours. - New warning appears multiple time in logs: "daemon.warn avahi-daemon[2154]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?)" Overall, fairly satisfied. On Thu, Jun 26, 2014 at 3:53 PM, Dave Taht wrote: > I have been blowing it up with continuous traffic, saturating the cpu, > talking to multiple devices, using crypto and ethernet, now for > several days. > > I am using sfq on the wifi, rather than fq_codel, at least temporarily. > > Occasionally, using the rrul test, I can get it to temporarily either > lose a route or deassociate from wifi, or something else like netperf > itself blowing up, but it always comes back within a few seconds. So > far, using the rrul_be test I haven't seen that happen. I do see cpu > absolutely maxed at present with rrul and not rrul_be. > > I have given up on tuning the wifi aggregate queue length (formerly > 12, now 48) as much as I had before - as the previous setting had > adverse effects on download throughput, so I'll put that fix in the > next release and live with the added latency until we can pull > together the make-wifi-fast project. > > I see an improvement on the simultaneous upload/download test from > 10mbit up/.2 down to 6up,3down, latency (as measured on the main > client) of about 80ms (which still sucks about 10x worse than what > seems possible) > > I ran out of space on my packet captures... > > I am going to be adding more clients, switching back to fq_codel, and > adding in ipv6 if this continues to take the load I am throwing at it. > Then adding impairments to degrade the wifi to more marginal levels. > > Interestingly I have not got any instruction traps, nor the famed dma > overrun bug/recovery in this release so far... I am encouraged, but > until I setup a mac with bad connectivity and have things run for > days and days I won't sleep well. > > And I had done a build from this codebase for the picostation and am > watching that crash under normal load regularly. That box only has > 32MB of memory, where the cerowrt box has 128MB memory. > > > On Thu, Jun 26, 2014 at 12:28 PM, Jim Reisert AD1C > wrote: >> Been running since Wednesday evening, no issues so far. >> >> -- >> Jim Reisert AD1C, , http://www.ad1c.us > > > > -- > Dave T=C3=A4ht > > NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_029= 6_indecent.article > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel