From: Bob Copeland <me@bobcopeland.com>
To: Yaniv Machani <yanivma@ti.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Maital Hahn <maitalm@ti.com>,
Johannes Berg <johannes@sipsolutions.net>,
Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Subject: Re: [PATCH v2 2/3] mac80211: mesh: improve path resolving time
Date: Tue, 19 Jul 2016 08:44:56 -0400 [thread overview]
Message-ID: <20160719124456.GD11996@localhost> (raw)
In-Reply-To: <CAEFj987X26u59K32Mt-bKBSTmy3cWvOiNNBG7K4wbdQBAdR97Q@mail.gmail.com>
On Tue, Jul 19, 2016 at 12:59:56AM +0800, Chun-Yeow Yeoh wrote:
> > To improve that, added an 'immediate' flag to be used when the path needs to be resolved.
> > Once set, a PREQ frame will be send w/o considering the MinInterval parameter.
>
> Suggest that you try to reduce the mesh_hwmp_preq_min_interval to your
> desired value instead of introducing a new patch specific to your use
> case.
>
> IEEE 802.11-2012 has defined dot11MeshHWMPpreqMinInterval attribute to
> specify the minimum interval of time during which a mesh STA can send
> only one Action frame containing a PREQ element. This is to avoid
> flooding of broadcast PREQ frame especially when the number of mesh
> STA is increased.
Good point, according to 13.10.9.3, conditions for sending PREQ include:
"The mesh STA has not sent a PREQ element for the target mesh STAs less
than dot11MeshHWMPpreqMinInterval TUs ago. If this is the case, the
transmission of the PREQ has to be postponed until this condition becomes
true."
Adopting this patch would violate that, so please disregard my suggested
rewrites; we should just skip this one.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-07-19 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 16:59 [PATCH v2 2/3] mac80211: mesh: improve path resolving time Yeoh Chun-Yeow
2016-07-19 12:44 ` Bob Copeland [this message]
2016-07-19 13:02 ` Machani, Yaniv
2016-07-19 13:43 ` Bob Copeland
2016-07-19 16:01 ` Yeoh Chun-Yeow
2016-07-19 20:01 ` Machani, Yaniv
2016-07-20 6:45 ` Yeoh Chun-Yeow
2016-07-20 12:15 ` Machani, Yaniv
2016-07-20 16:40 ` Yeoh Chun-Yeow
2016-07-20 18:17 ` Machani, Yaniv
2016-07-21 2:29 ` Yeoh Chun-Yeow
-- strict thread matches above, loose matches on Subject: below --
2016-07-13 11:45 Yaniv Machani
2016-07-19 12:36 ` Bob Copeland
2016-08-11 13:22 ` Johannes Berg
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=20160719124456.GD11996@localhost \
--to=me@bobcopeland.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maitalm@ti.com \
--cc=yanivma@ti.com \
--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).