From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] the wifi airtime-fair fq_codel stuff on net-next looks mostly good
Date: Sat, 15 Oct 2016 09:24:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1610150919300.12036@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7r_eeOLGawymPtFt_mgZg-u-auriWirXZE+0=9i80QyQ@mail.gmail.com>
On Wed, 12 Oct 2016, Dave Taht wrote:
> http://openwrtsummit.org/#quick-details
I've had the discussion with "radio guys" before regarding "fairness" of
radio resources. They kept talking about "optimising the cell for
throughput". I told them "then we should give the speaker with the highest
bitrate and demand for bits as much radio resources as possible, and
starve everybody else". This is of course not good for general customer
satisfaction.
After a lot of discussions back and forth, we came to the same conclusion
as you seem to have come to (if I understood Tokes talk correctly), in
that "radio time" is the most fair resource. If someone has bad radio
conditions then they get lower total throughput than the one with good
radio conditions, so the fairness is "equal air time". This means
everybody get equal part of the shared resource, and gives people an
incentive to try to improve radio reception if they have trouble, and
doesn't starve everybody else of airtime just because one device is having
a bad radio day.
So full support for this approach from me, good job!
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-10-15 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 15:18 [Make-wifi-fast] " Dave Taht
2016-10-12 15:32 ` Jim Gettys
2016-10-12 15:46 ` Dave Taht
2016-10-15 7:24 ` Mikael Abrahamsson [this message]
2016-10-15 7:59 ` Luca Muscariello
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=alpine.DEB.2.02.1610150919300.12036@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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