From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] wifi AP switching time
Date: Fri, 04 Jan 2013 10:08:38 -0500 [thread overview]
Message-ID: <50E6F076.4070403@rogers.com> (raw)
In-Reply-To: <mailman.5.1357243201.32365.bloat@lists.bufferbloat.net>
On Jan 1, 2013 6:50 PM, "Michael Richardson" <mcr@sandelman.ca> wrote:
>> A comment was made a month ago or so about how long it takes wifi APs
>> to switch from transmitting (unicast) to one station to another. That
>> there was quite a large latency here, and that this was one reason that
>> the AP designers wanted large buffers to accmulate, so that the
>> switching time could be amortized over a larger number of packets.
Pedro Tumusok <pedro.tumusok@gmail.com> replied
> I might be way of here, but to me this sounds like a-mpdu which is used to
> aggregate frames to get higher throughput. Thats in the specification, its
> in 802.11ac and I believe that it go introduced with 802.11n.
>
> It is there to mitigate the overhead of aquiring the channel.
And that in turn sounds like a place where codel may be needed to ensure
the buffer drains down to nothing in the general case. Alternatively, a
simpler approach might be to buffer only when actively trying a acquire
a channel.
I wonder if there are other only-for-one-reason buffers lying around in
the communication path (;-))
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
(416) 223-8968
next parent reply other threads:[~2013-01-04 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1357243201.32365.bloat@lists.bufferbloat.net>
2013-01-04 15:08 ` David Collier-Brown [this message]
2013-01-07 1:34 ` Michael Richardson
2013-01-07 3:43 ` Pedro Tumusok
2013-01-01 17:49 Michael Richardson
2013-01-03 9:18 ` Pedro Tumusok
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E6F076.4070403@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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