From: Johannes Berg <johannes@sipsolutions.net>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, rmanohar@codeaurora.org
Subject: Re: [PATCH v2 2/3] mac80211: Make mesh failure moving average configurable
Date: Wed, 08 Feb 2017 09:31:23 +0100 [thread overview]
Message-ID: <1486542683.4603.10.camel@sipsolutions.net> (raw)
In-Reply-To: <1485893272-6893-2-git-send-email-rmanohar@qca.qualcomm.com>
On Tue, 2017-01-31 at 12:07 -0800, Rajkumar Manoharan wrote:
> Currently mesh moving fail average is calculated based on constant
> weight factor. In worst case moving average reaches threshold by
> considering 16 msdu tx ack status and deactivates mesh path. Having
> a constant weight factor might not be suitable for all environments.
> So make it tunable parameter and also lower default weight to 10 so
> that mesh broken link calculation will consider more packet status
> (32 msdus ack status) before dropping mesh path.
I don't think this makes a lot of sense, and with a conversion to the
EWMA helpers it would probably not really be possible anyway.
johannes
next prev parent reply other threads:[~2017-02-08 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 20:07 [PATCH v2 1/3] mac80211: fix mesh moving average stuck Rajkumar Manoharan
2017-01-31 20:07 ` [PATCH v2 2/3] mac80211: Make mesh failure moving average configurable Rajkumar Manoharan
2017-02-08 8:31 ` Johannes Berg [this message]
2017-01-31 20:07 ` [PATCH v2 3/3] mac80211: clear failure average upon mesh path deactivation Rajkumar Manoharan
2017-02-08 8:30 ` [PATCH v2 1/3] mac80211: fix mesh moving average stuck 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=1486542683.4603.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.