From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 42B213B29F for ; Sat, 1 Oct 2016 15:05:43 -0400 (EDT) Received: by mail-qk0-x22b.google.com with SMTP id j129so126612256qkd.1 for ; Sat, 01 Oct 2016 12:05:43 -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-transfer-encoding; bh=fkdpvvyosiDdEmyilh4QBN+hqEwDsZ6wVZcvATKq9C4=; b=YmGT6+5dkb90VNVIeVWlmorj/Yj0OutlL4dtm7OR2Xz4L7/NMD8YZlzfQ69Za+X1V9 zttjhNWhrlWfpqPNnGmYhcza544F9EDZRSL56ENr5l+1eRnYrg/WWP7sBqfsa8xQVbrV DydI+EBoWJxcyo3w5c/zVQIsFOUIu3/+WaZEZVobHep4YuAHEOjvh1YJtj0fWAxKZ7bD vXj6wM9aFSKayC0fYyNjk/zHUhRmE2Hghn9m3JsBVkrp5piM49udmda0vsfwQroQHFMR /8mmvFB8UtHov30pmSQge3KBtg3spMtLZLIrMwKBPv4l3Ay5bcrYDV1+UVVkaj4ZJXLF bc6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=fkdpvvyosiDdEmyilh4QBN+hqEwDsZ6wVZcvATKq9C4=; b=UIxntRyZp4lyh6Zp4N/j2YmG+9y76y6tHlxm9BKfW2cIYFiZeCgAh6pHhtZfY4pJSu 5Ru9egkTZ6gZMzGllmZlp9uOxCwcGqkvHkeknY17WD8oUqFRm/VS4c8BVMPshkwCUE2r Nh9rrM+ef7jMw0pBEgk5B3qTHQwrzAr2nOXDADAtd5dlK/0a0+38wlEvTpjSaDaWbzQw SwwMzxSDPqe3TUoZNiaJDOQ8uznf52VqMfnO2nllET3wTivy9yxiCaQoLWuDl2k+OQBg 5wR4Iz1MHGE7Mcl+bpbF5lIGLRNT/mzLL4yRALKbUoM3tF7ME5vBk7vdPeCu9QayKJrV POVg== X-Gm-Message-State: AA6/9RmrlgS3kCilmjYLpIQ4lJ9xYvJDnrrxyk/OHnPeal7QkkHDr0FQyyIkoobCCtWTi2VDDBtUHb3tVo1/zw== X-Received: by 10.55.69.72 with SMTP id s69mr13253256qka.153.1475348742902; Sat, 01 Oct 2016 12:05:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.146.164 with HTTP; Sat, 1 Oct 2016 12:05:42 -0700 (PDT) In-Reply-To: <8760pc9c0k.fsf@toke.dk> References: <8760pc9c0k.fsf@toke.dk> From: Dave Taht Date: Sat, 1 Oct 2016 12:05:42 -0700 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: make-wifi-fast@lists.bufferbloat.net, Michal Kazior Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] net-next is next X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 19:05:43 -0000 OK, so the only thing I don't have a full grip on is what the napi-for-ath10k change did. My plan next week (sometime) would be to reassemble the various pieces for ubuntu, for the x86 apu2 (ath9k, ath10k) and laptop (ath9k). If there's something that can work on lede, groovy, the boxes I have readily available are ubnt uap-lite and archer c7v2. On Sat, Oct 1, 2016 at 11:09 AM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Dave Taht writes: > >> I'm a little vague on the pieces missing as yet. I think?, still out >> of tree are: > > Don't see anything missing from the list that I have been working on. Of > the things I have: > >> * Hooking up the ath9k to the intermediate queues code > > I expect Kalle to add this sometime during the upcoming merge window > (which opens tomorrow, according to the PHB crystal ball: > http://phb-crystal-ball.org/). > >> * airtime fairness for the ath9k > > Haven't submitted a new version of this since the other things went in. Patches somewhere? > While the basic scheduler works well, there are still some things to > work out before making a serious attempt at upstreaming it (most notably > the interaction with the hardware QoS queues). I was more or less planning to ignore that. Nobody else bothers to test flooding the hardware queues, why should we? :/ And the behavior is better now, regardless. Can't we ignore it? :-P >Also, moving parts of the > code into mac80211 would make it easier to re-use in other drivers. Not > sure which parts, though. same here. Pursuing another chipset (like the mt76 or "c.h.i.p") might lend insight. Sigh. >> * Codel "hack" for low rates > > This still needs to be solved, but the hack I posted previously was just > that: A hack. I think a different approach is needed. I outlined a couple approaches in my previous (overlong, meandering) blog entry ( http://blog.cerowrt.org/post/a_bit_about_bbr/ ) - notably, "giving up" - and turning off codel at a decent sized aggregate for the station, rather than at the global limit of one packet. And there were a few much easier things from layering on top of the airtime fairness stuff that might make the impact of multiple stations on codel less difficult - reducing the txop and reducing the advertised txop - when highly contended. Assembling enough pieces to tackle and test those approaches at slow, middle, and fast rates... would be good, and hopefully I've got a grip on which pieces, now, thx. > >> As for what's in lede.... ? > > LEDE has the previous version of the mac80211 fix and the ath9k patch to > enable the TXQ. That's lede, not lede-staging? > > -Toke --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org