From: David Lang <david@lang.hm>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Thoughts on tackling airtime fairness
Date: Wed, 11 May 2016 08:24:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1605110821200.1548@nftneq.ynat.uz> (raw)
In-Reply-To: <87zirwk4lw.fsf@toke.dk>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1858 bytes --]
On Wed, 11 May 2016, Toke Høiland-Jørgensen wrote:
> David Lang <david@lang.hm> writes:
>
>>> - How to measure the results? Can we dump the information from the
>>> driver (and is it accurate)? Do we need to parse aircaps? Something
>>> else?
>>
>> we need to be able to instrament the driver (I don't know if we can
>> get enough data there or not currently)
>>
>> trying to work with aircaps has the problem that what you see in the
>> aircap doesn't match what either the sender or receiver sees
>>
>> Take retransmissions as an example. They only happen because the
>> receiver didn't see them. If you were to get an aircap off the same
>> antenna as the receiver, you also wouldn't see them and therefor could
>> not account for them. In the real world, you are doing the aircap from
>> a different device, with a different antenna so what you see will be
>> even more different. Now think about the normal case where you have
>> two stations taking in two very different locations and one device to
>> do the aircap.
>>
>> If we don't have anything else, aircaps are what we have to fall back
>> on, but we need to realize how much we can't see at that point.
>
> Hmm, hadn't thought of that. Damn. Well, guess we'll have to trust the
> driver (or make it trustworthy if we can't).
the good news is that getting this information out of the driver should not be
hard. It knows when it does a retransmit.
I also suspect that we could get away without explictly tracking retransmits for
now. As it retransmits to a station, it's also going to end up slowing down if
it's a long-term problem.
we need to think of the scale we are trying to be fair on. I think that if we
are fair on the scale of seconds we will gain 80% of the effect that we would
get if we were trying to be fair on the order of ms, and it's much easier to do
:-)
David Lang
next prev parent reply other threads:[~2016-05-11 15:24 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
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 [this message]
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.1605110821200.1548@nftneq.ynat.uz \
--to=david@lang.hm \
--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