From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Managed to break 802.11n (on a 3800)
Date: Thu, 16 Jan 2014 17:35:27 -0500 [thread overview]
Message-ID: <CAA93jw58CfS3b_xv=w0Q4yXfnUxDP64m7iyL_+j=6axtPmKLiA@mail.gmail.com> (raw)
In-Reply-To: <BDC09B87-AB4B-4D40-9EB0-D355023B4F29@gmail.com>
On Thu, Jan 16, 2014 at 2:08 PM, Aaron Wood <woody77@gmail.com> wrote:
>
>>> Sebastian, after sorting out the router, it's still biased, but far
>>> less
>>> so, about a 2:1 ratio between upload and download.
>>
>> So I See offen 10:1 and worse @165Mbit/s raw wireless rate
>
> I get mixed results, but they aren't good. IIRC, apple really changed something about the media access in 10.8, I'll look into that. And see if my wife will let me install netperf on her laptop (I think it's still running 10.7)
>
>
>>> Also, my understanding was that with rts/cts, the router was in control
>>> of
>>> that aspect of things?
>>
>> That is what I thought AS well, but it is not what I See with osx 10.8.
>>
>
> It may be a case of the station aggressively asking to send, and the AP granting instead of sending data to the station that's waiting.
Um, probably not. Both station and AP are doing EDCA scheduling, (I'd
hope) which was originally a p2p style protocol. So it
is kind of overly "fair" to both. The client is doing better
aggregation since it is only going one way, the AP has trouble with
aggregation due to lack of per station queueing.
folk have done work to try and give the APs more priority and looking
at that has also long been on the todo list.
> It should be clear in a monitor-mode tcpdump (or a statistical summary of packets).
but do check. I generally get terrible results from macos, and the
intel wifi chip in the laptop. the ath9k in another laptop is
considerably better, and ath10k (on the nuc) is not horrible. It's
terrible on both ends, on this test and both the clients and the APs
need a ton of work...
> --Aaron
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-01-16 22:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 15:03 Aaron Wood
2014-01-16 15:29 ` Sebastian Moeller
2014-01-16 15:46 ` Aaron Wood
2014-01-16 17:20 ` Sebastian Moeller
2014-01-16 19:08 ` Aaron Wood
2014-01-16 20:10 ` Sebastian Moeller
2014-01-16 21:33 ` Aaron Wood
2014-01-16 22:50 ` Dave Taht
2014-01-16 23:15 ` Sebastian Moeller
2014-01-16 23:40 ` Dave Taht
2014-01-17 20:15 ` Toke Høiland-Jørgensen
2014-01-17 20:17 ` Dave Taht
2014-01-19 19:01 ` Toke Høiland-Jørgensen
2014-01-19 20:01 ` Sebastian Moeller
2014-01-19 20:58 ` Toke Høiland-Jørgensen
2014-01-19 21:12 ` Sebastian Moeller
2014-01-16 22:35 ` Dave Taht [this message]
2014-01-16 22:30 ` Dave Taht
2014-01-16 22:56 ` Sebastian Moeller
2014-01-16 23:12 ` Dave Taht
2014-01-16 23:25 ` Sebastian Moeller
2014-01-16 15:38 ` Robert Bradley
2014-01-16 15:46 ` Aaron Wood
2014-01-16 22:08 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw58CfS3b_xv=w0Q4yXfnUxDP64m7iyL_+j=6axtPmKLiA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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