From: David Lang <david@lang.hm>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Luca Muscariello <luca.muscariello@gmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Thoughts on tackling airtime fairness
Date: Wed, 11 May 2016 08:07:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1605110805000.1548@nftneq.ynat.uz> (raw)
In-Reply-To: <87futolndh.fsf@toke.dk>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1216 bytes --]
On Wed, 11 May 2016, Toke Høiland-Jørgensen wrote:
>> Ten years ago I played with SFQ and madwifi for 802.11g to get max-min
>> time fairness (and so proportional rate fairness) with excellent
>> results. The hacking I made was based on using time quanta instead of
>> bytes. Which required me to get the current PHY rates (AP to all
>> STAtions) and dynamically compute/update SFQ time quanta.
>
> Do you happen to recall what precision you achieved or how much the
> precision was really important? Several papers seem to assume that very
> high precision is not terribly important since it all evens out in the
> end, and I can see how that could be true; but would like to have it
> confirmed :)
I think the point here is that perfect is the enemy of good enough. Right now
the only attempt at fairness is packet counts. Anything that improved this would
be a win. We can probably get several orders of magnatude improvement from even
the most crude measurements.
So start simple/cheap and see how much improvement there is, only go to more
precision (more expensive) if you find there's a need to.
for that matter, retries may be something that you start off ignoring, just like
multicast
David Lang
next prev parent reply other threads:[~2016-05-11 15:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:19 Toke Høiland-Jørgensen
2016-05-11 12:55 ` Luca Muscariello
2016-05-11 13:45 ` Toke Høiland-Jørgensen
2016-05-11 14:48 ` Luca Muscariello
2016-05-11 15:10 ` Toke Høiland-Jørgensen
2016-05-11 15:17 ` David Lang
2016-05-11 15:20 ` David Lang
2016-05-11 15:28 ` Toke Høiland-Jørgensen
2016-05-11 15:33 ` Luca Muscariello
2016-05-11 16:19 ` Dave Taht
2016-05-11 16:29 ` Dave Taht
2016-05-11 16:40 ` Toke Høiland-Jørgensen
2016-05-11 16:33 ` Luca Muscariello
2016-05-11 15:07 ` David Lang [this message]
2016-05-12 15:59 ` Dave Taht
2016-05-11 15:04 ` David Lang
2016-05-11 16:09 ` Luca Muscariello
2016-05-11 16:41 ` Dave Taht
2016-05-11 18:13 ` Dave Taht
2016-05-12 7:26 ` Michal Kazior
2016-05-12 8:21 ` Luca Muscariello
2016-05-12 8:40 ` David Lang
2016-05-12 8:48 ` Michal Kazior
2016-05-11 18:28 ` Luca Muscariello
2016-05-11 18:35 ` Luca Muscariello
2016-05-11 15:03 ` David Lang
2016-05-11 15:15 ` Toke Høiland-Jørgensen
2016-05-11 15:24 ` David Lang
2016-05-11 16:35 ` moeller0
2016-05-11 23:25 ` David Lang
2016-05-12 6:41 ` moeller0
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.1605110805000.1548@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=luca.muscariello@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