linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 6 Mar 2017 10:25:51 -0800	[thread overview]
Message-ID: <faafc817ee74ba39171199985756b87b@mail.gmail.com> (raw)
In-Reply-To: <CAEFj9868zDVomdjQhrzNKs9ANaRF85wdA49vKwVZJ2dUiTpoVg@mail.gmail.com>

> >> 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.
> >>
> >
> > Airtime link metrics should choose the multiple links if it is good
> > compared to direct link.
> >
> >> That's why there are link and path metrics.
> >
> > I don't think that you don't get this. Every nodes sends out multiple
> > PREQs.
> > Other nodes received it with rebroadcast again. Take note on this.
> >
> >> Improving the link metric isn't going to help with PREQ reliability
> >> problems.
> >
> > PREQ realiabilit? It is broadcast management frame and usually using
> > lowest transmission rate. So it is realiabe.

They are only reliable when compared to individual rate controlled frames.
But, in general, they are most certainly not reliable. Even in a shielded
and conductive (i.e. with physical wires connecting antennas) environment
lost PREQ frames are not hard to see.

  -- Jesse

  reply	other threads:[~2017-03-06 18:25 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
     [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 [this message]
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=faafc817ee74ba39171199985756b87b@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).