From: Adrian Popescu <adriannnpopescu@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jon Pike <jonpike54@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Make-wifi-fast Digest, Vol 29, Issue 9
Date: Tue, 19 Sep 2017 15:17:27 +0300 [thread overview]
Message-ID: <CAF3M4P0XmxPTAfAzJy03cidzhbEN561GY7g=LEbq8ZJ+eTvBtw@mail.gmail.com> (raw)
In-Reply-To: <87tvzzjaef.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
I'll compile again from the latest sources to test again.
Please don't revert the patch because of my report.
On Tue, Sep 19, 2017 at 12:38 PM, Toke Høiland-Jørgensen <toke@toke.dk>
wrote:
> Jon Pike <jonpike54@gmail.com> writes:
>
> > 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.
>
> Yeah, that is odd. Not really sure what to do about it at this point;
> maybe just leave it in and see if more people complain?
>
> > 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.
>
> I don't have any ath10k cards in my own testbed, so I don't have a good
> dataset for the potential gains. Not sure if someone else on the list
> has done comparisons and can share results?
>
> -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: 2420 bytes --]
next prev parent reply other threads:[~2017-09-19 12:17 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
2017-09-19 9:38 ` Toke Høiland-Jørgensen
2017-09-19 12:17 ` Adrian Popescu [this message]
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='CAF3M4P0XmxPTAfAzJy03cidzhbEN561GY7g=LEbq8ZJ+eTvBtw@mail.gmail.com' \
--to=adriannnpopescu@gmail.com \
--cc=jonpike54@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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