From: Bob McMahon <bob.mcmahon@broadcom.com>
To: David Lang <david@lang.hm>
Cc: chromatix99@gmail.com, bloat-announce@lists.bufferbloat.net,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net, dpreed@deepplum.com,
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 18:55:36 -0700 [thread overview]
Message-ID: <CAHb6Lvpe=2Qk2TOJUbMxGYw69Zo2UgKFbr=ER55NUeQY3S+iLw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1808271750490.2583@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]
Hmm, not sure I understand the distinction. CTS per the AP informs those
other transmitters to stay quiet per the CTS NAV. I may be
misunderstanding things. Thanks for the continued discussions. It helps
to better thoroughly understand the issues.
Bob
On Mon, Aug 27, 2018, 6:52 PM David Lang <david@lang.hm> wrote:
> On Mon, 27 Aug 2018, Bob McMahon wrote:
>
> > I thought that RTS/CTS would handle the case of hidden nodes, i.e. a
> device
> > that fails to successfully transmit can resort to RTS/CTS to get the
> > receiver to reserve time for it. Also, lack of a RX ack seems ok to
> > trigger MAC level retransmits.
>
> the problem isn't getting the receiver to reserve time for it, it's
> getting the
> other transmitter(s) to not step on it when it transmits. Those other
> transmitters may belong to different people, sharing a channel with your
> system
> and nothing else.
>
> David Lang
>
> > It seems the LBT bug is the collision avoidance overheads when it isn't
> > needed, i.e. no other energy would cause the RX PHY to fail its decode
> and
> > the EDCA backoffs had no benefit, stochastic or otherwise. Optimizing
> > that out is said to be not possible from local information only and per
> > "shared" spectrum.
> >
> > Bob
> >
> >
> > On Mon, Aug 27, 2018 at 3:33 PM David Lang <david@lang.hm> wrote:
> >
> >> On Mon, 27 Aug 2018, Jonathan Morton wrote:
> >>
> >>> 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.
> >>
> >> Also, there may be other transmitters that the recipient of the packets
> >> can hear
> >> that you cannot hear, so it's not possible to detect colliding
> >> transmissions
> >> directly in all cases.
> >>
> >> This is another trap that digital/wired people fall into that doesn't
> >> really
> >> apply in the analog/radio world.
> >>
> >> David Lang
> >>
> >
>
[-- Attachment #2: Type: text/html, Size: 2669 bytes --]
next prev parent reply other threads:[~2018-08-28 1:56 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
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 [this message]
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='CAHb6Lvpe=2Qk2TOJUbMxGYw69Zo2UgKFbr=ER55NUeQY3S+iLw@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=bloat-announce@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=david@lang.hm \
--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