From: Jesse Jones <jjones@uniumwifi.com>
To: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Alexis Green <agreen@cococorp.com>,
Alexis Green <agreen@uniumwifi.com>
Subject: RE: [PATCH v2] mac80211: mesh - always do every discovery retry
Date: Fri, 3 Mar 2017 10:49:51 -0800 [thread overview]
Message-ID: <39c846a5bcfa1fff26f69a082466e414@mail.gmail.com> (raw)
In-Reply-To: <CAEFj9874ynLcjn7AhpB-ajre3twpwHM4iEVN2ozYEGDPGErs0Q@mail.gmail.com>
> > Yes, that is a real issue. We are planning on doing some further work
> > in this area to try to minimize the explosions that can be seen with
> > PREQs in larger networks while balancing the need for reliability.
> >
> > Path discovery
> >> should stop once the path is established. By attempting 2nd, 3rd or
> >> 4th doesn't guarantee the next path will be "good".
> >
> > It doesn't guarantee anything of course but it does raise the
> > probability that the right path will be found. For example take four
> > nodes in a ring where the A-B, B-C, C-D links are all good but the A-D
> > link is poor. Poor enough that the higher data rates are hosed for
> > that link but the basic rate used by management frames is relatively
> > unaffected. If we assume that the reliability of management frames is
> > 90% then in order for A to route to D it needs to get a PREQ to D and
> > a PREP back. It has two options 1) for A-D the reliability will be
> > 0.9^2 = 81% 2) for A-B-C-D the reliability will be 0.9^6 = 53%.
>
> What is round trip delay between A-D compared to A-B-C-D? 1 hop away the
> throughput is reduced by half.
Well A-D is going to have a much smaller RTT than A-B-C-D. And, yes, using
multiple hops is going to reduce throughput but I'd much rather use multiple
120 Mbps links than a link that only supports 12 Mbps.
>Also if you have more nodes using longer
> path, you consume more airtime leads to really bad network performance,
> especially when B, C, or even D wants to start initial data transmission.
That's why there are link and path metrics.
> One way of improving the path is either enhancing the airtime link metric
> by
> considering the factor that you mentioned in or else introducing vendor-
> specific path metric. Sending more broadcast frames over the network won't
> be a good solution.
Improving the link metric isn't going to help with PREQ reliability
problems. Sending more PREQs will.
-- Jesse
next prev parent reply other threads:[~2017-03-03 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 1:28 [PATCH v2] mac80211: mesh - always do every discovery retry Chun-Yeow Yeoh
2017-03-02 17:32 ` Jesse Jones
2017-03-03 10:39 ` Chun-Yeow Yeoh
2017-03-03 18:49 ` Jesse Jones [this message]
[not found] ` <CAEFj987m=5a6pWZLMtTcVshmVfOmwwbb-+s0FR_+Dz6_xx7Dtw@mail.gmail.com>
2017-03-04 12:05 ` Chun-Yeow Yeoh
2017-03-06 18:25 ` Jesse Jones
2017-03-07 2:06 ` Chun-Yeow Yeoh
2017-03-29 8:24 ` Johannes Berg
2017-03-29 10:33 ` Chun-Yeow Yeoh
2017-05-17 13:59 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2017-02-28 23:50 Alexis Green
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39c846a5bcfa1fff26f69a082466e414@mail.gmail.com \
--to=jjones@uniumwifi.com \
--cc=agreen@cococorp.com \
--cc=agreen@uniumwifi.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yeohchunyeow@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).