From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Making association faster
Date: Tue, 24 Jan 2017 09:24:27 -0500 [thread overview]
Message-ID: <5e407ab9-bbcb-6859-b4dc-e91d9fb2cc68@rogers.com> (raw)
In-Reply-To: <1485265115.227821858@mobile.rackspace.com>
On 24/01/17 08:38 AM, dpreed@reed.com wrote:
> https://arxiv.org/abs/1701.02528
>
> Interesting approach. Nice analysis.
>
> Needs to be in OpenWRT?
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
It's more of a client mechanism as such: the access point needs to do a
sort of mirror image, to keep scan times down and be seen as a
preferred connection target. Not being bottlenecked looks important (;-))
--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
next prev parent reply other threads:[~2017-01-24 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 13:38 dpreed
2017-01-24 14:24 ` David Collier-Brown [this message]
2017-01-24 15:14 ` [Bloat] [Make-wifi-fast] " Dave Taht
2017-01-24 17:07 ` 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=5e407ab9-bbcb-6859-b4dc-e91d9fb2cc68@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