Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:41052 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752150AbdEQN73 (ORCPT ); Wed, 17 May 2017 09:59:29 -0400 Message-ID: <1495029567.2442.18.camel@sipsolutions.net> (sfid-20170517_155933_807420_FB2E8590) Subject: Re: [PATCH v2] mac80211: mesh - always do every discovery retry From: Johannes Berg To: Chun-Yeow Yeoh Cc: Jesse Jones , "linux-wireless@vger.kernel.org" , Alexis Green , Alexis Green Date: Wed, 17 May 2017 15:59:27 +0200 In-Reply-To: (sfid-20170329_123356_020574_F9F8F5DD) References: <39c846a5bcfa1fff26f69a082466e414@mail.gmail.com> <1490775841.7948.5.camel@sipsolutions.net> (sfid-20170329_123356_020574_F9F8F5DD) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2017-03-29 at 18:33 +0800, Chun-Yeow Yeoh wrote: > I would suggest the following modification of commit messages and > code. Let me know whether this is fine. > > --------- > I would suggest the following edition to the commit message: > > Instead of stopping path discovery when a path is established, > continue the > attempts to find alternative paths until we hit the > dot11MeshHWMPmaxPREQretries > limit. However, this is not a standard behavior and may easily > increase the number of > broadcast PREQ frame in your network. So this feature is turned off > by default. > > and the remaining are removed due to misleading explanation. > > Then, in the mesh_path_timer, I think that only the following is > needed: > > - if (mpath->flags & MESH_PATH_RESOLVED || > - (!(mpath->flags & MESH_PATH_RESOLVING))) { > + if (!multiple_discoveries && > +    (mpath->flags & MESH_PATH_RESOLVED || > +     (!(mpath->flags & MESH_PATH_RESOLVING)))) { Alexis? johannes