Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: Loganaden Velvindron <loganaden@gmail.com>,
	make-wifi-fast@lists.bufferbloat.net,
	 LEDE Development List <lede-dev@lists.infradead.org>
Subject: Re: [Make-wifi-fast] ath9k airtime fairness stabiity issues?
Date: Thu, 5 Jan 2017 06:18:18 -0800	[thread overview]
Message-ID: <CAA93jw5iURcShAjSebNN4uE7w=s+2s5=-mTPJ8OPQBofQp5i7g@mail.gmail.com> (raw)
In-Reply-To: <46229222-ccb9-549d-578d-a8f4c9b83de4@nbd.name>

On Thu, Jan 5, 2017 at 5:23 AM, Felix Fietkau <nbd@nbd.name> wrote:
> On 2017-01-05 14:22, Loganaden Velvindron wrote:
>> On Thu, Jan 5, 2017 at 4:59 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>> Felix:
>>>
>>> Was there a bugreport?  (don't see one)
>>>
>>> Do you have a specific device or behavior triggering this revert?
>>>
>>>
>>> On Thu, Jan 5, 2017 at 4:42 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>>> https://github.com/lede-project/source/commit/c296ba834db4ce8c71e0ad7030aab188fe60b27b
>>>
>>>
>>
>> Hi nbd & Toke,
>>
>> Would it be possible to enable it only on platforms like the tp-link
>> archer c7 v2 and the ubnt, where we have confirmed test reports for
>> the upcoming release ?
> I think it's quite unlikely that these issues are hardware specific.
> It's probably more related to the environment, types of clients, or even
> traffic patterns.

OK, well, I filed a bug. Can I encourage your reporters to chime in on
their issues and what hardware they see them on?

https://bugs.lede-project.org/index.php?do=details&task_id=368

We have extensive testbeds available, but my big one is 2 hours away
right now (and running a version of lede with this patch from october
or so), and hard to upgrade remotely. Been building up a new one in SF
(warmer) this week, just deployed a bunch of "c.h.i.p"s to stress it
out, but now I have to go check to see which builds of lede I
installed where. I'm pretty sure the UAP-lites are running jan 2...
the wndr is jan 4....

(And here I was dreaming up ways to seriously stress out ipv6
multicast (adding tons of routes to babel,
and/or using "uftp" heavily) (see
https://bugs.lede-project.org/index.php?do=details&task_id=253 ))

I'm going to finish getting something up that works and then go blow
up multicast harder, I think, while scratching my head on ATF. At
least I can get some non-atf data on how the chips behave, I guess.


-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

      parent reply	other threads:[~2017-01-05 14:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 12:59 Dave Taht
2017-01-05 13:02 ` Felix Fietkau
2017-01-05 13:11   ` Dave Taht
2017-01-05 13:22 ` Loganaden Velvindron
2017-01-05 13:23   ` Felix Fietkau
2017-01-05 14:03     ` Michal Kazior
2017-01-05 14:51       ` Dave Taht
2017-01-05 15:17         ` [Make-wifi-fast] [LEDE-DEV] " L. D. Pinney
2017-01-05 15:28           ` Felix Fietkau
2017-01-05 18:53             ` Weedy
2017-01-05 14:18     ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5iURcShAjSebNN4uE7w=s+2s5=-mTPJ8OPQBofQp5i7g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=lede-dev@lists.infradead.org \
    --cc=loganaden@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=nbd@nbd.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox