From: Jonathan Morton <chromatix99@gmail.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>
Cc: dpreed@deepplum.com, bloat-announce@lists.bufferbloat.net,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] [Cerowrt-devel] closing up my make-wifi-fast lab
Date: Mon, 27 Aug 2018 22:45:56 +0300 [thread overview]
Message-ID: <A2F03A04-E45A-42CB-8DE1-365BE75BF732@gmail.com> (raw)
In-Reply-To: <CAHb6LvpNYdFAc0ZoUw7Hqw3chZaMjthgDBdDF=rwBvZbV0WsjQ@mail.gmail.com>
> On 27 Aug, 2018, at 10:11 pm, Bob McMahon <bob.mcmahon@broadcom.com> wrote:
>
> I guess my question is can a WiFi transmitting device rely on primarily energy detect and mostly ignore the EDCA probability game and rather search for (or predict) unused spectrum per a time interval such that its digital signal has enough power per its observed SNR? Then detect "collisions" (or, "superposition cases" per the RX not having sufficient SINR) via inserting silent gaps in its TX used to sample ED, i.e. run energy detect throughout the entire transmission? Or better, no silent gaps, rather detect if there is superimposed energy on it's own TX and predict a collision (i.e. RX probably couldn't decode its signal) occurred? If doable, this seems simpler than having to realize centralized (or even distributed) media access algorithms a la, TDM, EDCA with ED, token buses, token rings, etc. and not require media access coordination by things like APs.
The software might be simpler, but the hardware would need to be overspecified to the point of making it unreasonably expensive for consumer devices.
Radio hardware generally has a significant TX/RX turnaround time, required for the RX deafening circuits to disengage. Without those deafening circuits, the receivers would be damaged by the comparatively vast TX power in the antenna.
So in practice, it's easier to measure SNR at the receiver, or indirectly by observing packet loss by dint of missing acknowledgements returned to the transmitter.
- Jonathan Morton
next prev parent reply other threads:[~2018-08-27 19:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 12:26 [Bloat] " David P. Reed
2018-08-27 6:00 ` [Bloat] [Make-wifi-fast] " Bob McMahon
2018-08-27 6:26 ` Jonathan Morton
2018-08-27 7:06 ` Bob McMahon
2018-08-27 7:52 ` Jonathan Morton
2018-08-27 8:34 ` Bob McMahon
2018-08-27 19:11 ` Bob McMahon
2018-08-27 19:45 ` Jonathan Morton [this message]
2018-08-27 19:59 ` Bob McMahon
[not found] ` <alpine.DEB.2.02.1808271431590.2583@nftneq.ynat.uz>
2018-08-28 1:46 ` Bob McMahon
[not found] ` <alpine.DEB.2.02.1808271750490.2583@nftneq.ynat.uz>
2018-08-28 1:55 ` Bob McMahon
2018-08-30 19:12 ` bkil
2018-08-30 19:17 ` Bob McMahon
2018-08-30 20:36 ` bkil
2018-09-03 19:30 ` Bob McMahon
2018-09-06 18:44 ` Jan Ceuleers
2018-08-27 7:24 ` Luca Muscariello
2018-08-27 7:39 ` Bob McMahon
2018-08-27 7:51 ` Luca Muscariello
2018-08-30 19:11 ` bkil
2018-08-27 22:37 Jonathan Morton
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=A2F03A04-E45A-42CB-8DE1-365BE75BF732@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat-announce@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.mcmahon@broadcom.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.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