Lets make wifi fast again!
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: David Lang <david@lang.hm>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Thoughts on tackling airtime fairness
Date: Wed, 11 May 2016 18:35:52 +0200	[thread overview]
Message-ID: <B07A9945-DE02-48DE-9C3B-1039C1A4062B@gmx.de> (raw)
In-Reply-To: <87zirwk4lw.fsf@toke.dk>


> On May 11, 2016, at 17:15 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> David Lang <david@lang.hm> writes:
>> 
>> 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).

	This issue seems surmountable, just make sure the air-capping machine is a) located halfway between the other two hosts in question and b) has better antennas ;) . It should be possible to “degrade” the antenna quality of the two hosts to make sure the air-capper (sounds like a fancy whale species) has better RF visibility…

Best Regards
	Sebastian


> 
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast


  parent reply	other threads:[~2016-05-11 16:36 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
2016-05-11 16:35     ` moeller0 [this message]
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=B07A9945-DE02-48DE-9C3B-1039C1A4062B@gmx.de \
    --to=moeller0@gmx.de \
    --cc=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