From: Johannes Berg <johannes@sipsolutions.net>
To: Matthias May <matthias.may@neratec.com>,
Jesse Jones <jjones@uniumwifi.com>,
agreen@cococorp.com, linux-wireless@vger.kernel.org
Cc: Jesse Jones <jjones@cococorp.com>
Subject: Re: [PATCH v2] mac80211: Jitter HWMP MPATH reply frames to reduce collision on dense networks.
Date: Tue, 14 Mar 2017 14:45:55 +0100 [thread overview]
Message-ID: <1489499155.10872.1.camel@sipsolutions.net> (raw)
In-Reply-To: <19214832-030e-2028-49a2-2db087c8c857@neratec.com>
> Isn't CWmin and CWmax only used for retries?
No.
> We recently had the problem that on 5MHz channels probe-responses of
> APs which can't hear each other (hidden node problem) always collide.
I think this is what I neglected - if the APs won't hear each other,
all their own sensing and NAV won't help since it'll never be updated.
CWmin/max are short enough to not actually matter in this case since
they're not long enough to avoid colliding entirely even if one picks
the lowest and the other the largest possible value.
johannes
next prev parent reply other threads:[~2017-03-14 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 19:58 [PATCH v2] mac80211: Jitter HWMP MPATH reply frames to reduce collision on dense networks Alexis Green
2017-02-27 13:30 ` Johannes Berg
2017-02-27 20:10 ` Alexis Green
2017-03-02 8:36 ` Johannes Berg
2017-03-02 17:41 ` Jesse Jones
2017-03-06 12:38 ` Johannes Berg
2017-03-06 18:01 ` Jesse Jones
2017-03-09 15:49 ` Matthias May
2017-03-10 8:40 ` Kalle Valo
2017-03-10 15:24 ` Alexis Green
2017-03-13 15:49 ` Benjamin Beichler
2017-03-14 13:45 ` Johannes Berg [this message]
2017-03-20 16:41 ` Thomas Pedersen
2017-03-16 10:16 ` Johannes Berg
2017-03-16 10:18 ` Johannes Berg
2017-03-19 1:48 ` 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=1489499155.10872.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=agreen@cococorp.com \
--cc=jjones@cococorp.com \
--cc=jjones@uniumwifi.com \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.may@neratec.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).