From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 9F97921F409 for ; Sat, 18 Apr 2015 03:38:28 -0700 (PDT) Received: by oica37 with SMTP id a37so90527144oic.0 for ; Sat, 18 Apr 2015 03:38:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=lmDiHeF7+Z50OH3Sn66zgOndQ7KehdEBKkGlTmVNzNY=; b=H/Dh4VOCh5sFC8TJZcYEg7fNZfXbZ3EZ32xyTDtH97Zwy0FXepNcASAOWncm+wWC6e Vx6+TsRjg4xW/9HzNS5zBvWEJ4Qj2Ecokx6UBsgCdDfBMDb+svh7V755LcRoJOQ4KeKc N5qPtR5pUapavVlG7OUoGuz3RIyAoxlvV1JXjWZxj1pmqWeRVeplp8ay98epBisWJ9DA fThd/f0VUpRgUUsP6Zwg/0o6PA+c4sS1E4YE3+PcH6LF0xRsboJzOYiagY0Jfigk9gDs EyRhP9FIm4OCyPxQTuhTnfpxY8gdecBxw4vOqJUFMz+k4qiDmLhVFCfFFi7zUFjcAd2u DOnA== X-Received: by 10.202.71.84 with SMTP id u81mr6188110oia.81.1429353507461; Sat, 18 Apr 2015 03:38:27 -0700 (PDT) MIME-Version: 1.0 Sender: white.phoenix@gmail.com Received: by 10.202.188.8 with HTTP; Sat, 18 Apr 2015 03:37:57 -0700 (PDT) In-Reply-To: References: From: leetminiwheat Date: Sat, 18 Apr 2015 06:37:57 -0400 X-Google-Sender-Auth: 5qks7QTAl4gBxyv6ykVEK8FfTEM Message-ID: To: Dave Taht Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] ath9k WMM not obeying DSCP/TOS flags? 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: Sat, 18 Apr 2015 10:38:56 -0000 On Sat, Apr 18, 2015 at 2:57 AM, Dave Taht wrote: Thanks for the replies, very informative! >> WMM seems particularly useful for mobile devices and/or crowded >> airspace, so I'd like to somehow get this working right. > > No it is not useful for crowded airspace, unless you are trying for a tem= porary > game theory win over everyone else that is not using wmm. > > I have long documented the ills of the VO queue in general in benchmarks > and documentation on how it interacts badly with aggregation. As for > using the BK queue effectively, a common problem is that much traffic > is mis-marked as CS1 that should not be. I don=C2=B4t recall disabling it= in > the stable release of cerowrt, nor did I attempt to push the patch up > to openwrt, so openwrt probably continues to (mis)use the VO queue. > > In general, you do best by minimizing TXOPs and maximizing aggregation > in crowded wifi environments. Are you sure mobile phones don't treat VO differently, such as disabling more power savings features in order to handle VO packets better? I did notice an improvement in a voice-chat app through the VI queue but It's still not perfect. with PINGOPT=3D1 the device jitters between 2ms-300ms with little to no traffic, 2ms-150ms with txqueuelen 16, but with constant downstream traffic it holds steady around 3ms. My thinking was perhaps VO packets would keep it from doing tricks with aggregation and causing delay and static in voice chat apps that don't set their traffic properly to the client OS. > Gaining the resources to fix wifi has eaten most of the last 10 months > of my life, AFTER helping come up with some of the theoretical fixes > over the last 4 years. We are finally in a position to make a run at > making deployable some of the same latency reducing techniques we have > successfully applied to wired links to wifi, but MUCH work remains, > and nearly zero funding exists, still. I had honestly hoped to be able > to fully prototype and test the fixes over the summer, but that hope > fades more and more every day. Well I for one greatly appreciate all the work you and everyone else has done to fix networking. I wouldn't hesitate to donate if I was in a financial position to do so. Thanks again for the reply and for clearing some things up that i was scratching my head over. P.S. amazing stuff in your debloat script! though hard to read even with a decent understanding of LUA. Can't seem to get it to change txqueuelen though even after installing ethtool, fixing the path, and appending FORCE_RING=3D'tx 16' to hotplug/iface/00-debloat, but I've got a custom init script at the end boot that does most of what I need. I understand at this point (if time/finances were permitted) you'd be working on chaos calmer which doesn't even use hotplug anymore anyways.