From: Jon Pike <jonpike54@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Make-wifi-fast Digest, Vol 29, Issue 9
Date: Mon, 18 Sep 2017 22:36:49 -0700 [thread overview]
Message-ID: <CALukJKRq108Uc6mmWmYMk1JprR_DjPmZmqQUMzO8V70tzBAMvQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.0.1505318401.16618.make-wifi-fast@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]
Hey Toke...
Did you notice a guy responded to your commit on LEDE-DEV? He's reporting
no speed problems on his C2600... This is turning into a head scratcher.
I was going to finally get back to this thread and suggest that at least
the C5/7 special build that rOOt manages on the LEDE forum could benefit
from this, (uh, except for that pesky lack of latency reduction?) after it
gets reverted from the nightly.
Now, I'm just wondering what benifits there would be with this. I realize
I've pretty much forgotten now what kinds of bufferbloat reduction and or
airtime fairness bits ath10k had before, or would have with this. So if
you wouldn't mind going over that again, at least I'd have the right info
to pass along on what the benifits would be... assuming it's reccomendable
at this point.
On Sep 13, 2017 9:00 AM, <make-wifi-fast-request@lists.bufferbloat.net>
wrote:
> Send Make-wifi-fast mailing list submissions to
> make-wifi-fast@lists.bufferbloat.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
> or, via email, send a message with subject or body 'help' to
> make-wifi-fast-request@lists.bufferbloat.net
>
> You can reach the person managing the list at
> make-wifi-fast-owner@lists.bufferbloat.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Make-wifi-fast digest..."
>
> Today's Topics:
>
> 1. Re: Make-wifi-fast Digest, Vol 29, Issue 1
> (Toke Høiland-Jørgensen)
>
>
> ---------- Forwarded message ----------
> From: "Toke Høiland-Jørgensen" <toke@toke.dk>
> To: Adrian Popescu <adriannnpopescu@gmail.com>
> Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
> make-wifi-fast@lists.bufferbloat.net
> Bcc:
> Date: Tue, 12 Sep 2017 19:03:24 +0200
> Subject: Re: [Make-wifi-fast] Make-wifi-fast Digest, Vol 29, Issue 1
>
>
> On 12 September 2017 16:03:36 CEST, Adrian Popescu <
> adriannnpopescu@gmail.com> wrote:
> >I was testing on QCA9*9*80, not QCA9*8*80. It probably works fine on
> >C7. It
> >doesn't work on the C2600.
>
> Ah, right. Bugger. Could you confirm that the latest nightly is broken?
> Then I'll ask John to revert the patch...
>
> -Toke
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
[-- Attachment #2: Type: text/html, Size: 3839 bytes --]
next parent reply other threads:[~2017-09-19 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1505318401.16618.make-wifi-fast@lists.bufferbloat.net>
2017-09-19 5:36 ` Jon Pike [this message]
2017-09-19 9:38 ` Toke Høiland-Jørgensen
2017-09-19 12:17 ` Adrian Popescu
2017-09-19 12:32 ` Toke Høiland-Jørgensen
2017-09-19 20:51 ` Adrian Popescu
2017-09-19 21:10 ` Toke Høiland-Jørgensen
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=CALukJKRq108Uc6mmWmYMk1JprR_DjPmZmqQUMzO8V70tzBAMvQ@mail.gmail.com \
--to=jonpike54@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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