From: Jesse Jones <jjones@uniumwifi.com>
To: Johannes Berg <johannes@sipsolutions.net>,
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: Mon, 6 Mar 2017 10:01:00 -0800 [thread overview]
Message-ID: <bb0cad75534e337507d6b06030909f20@mail.gmail.com> (raw)
In-Reply-To: <1488803913.5761.11.camel@sipsolutions.net>
> > Well it certainly attempts to via stuff like carrier sense. But that
> > is not fool proof and any time two routers hear a frame and both
> > decide to forward it immediately there is a chance that they will both
> > sense the air at the same time, decide that it is clear, and lose both
> > their forwarded frames due to a collision. How often that happens is
> > hard to say but we have observed that exact behavior a few years ago
> > with an 802.11 multicast routing protocol and adding jitter
> > significantly improved reliability.
>
> I'm really surprised by this since they both should jitter their
> transmissions
> already between CWmin and CWmax. Is that window somehow really super
> small for what you're doing?
I don't think so.
-- Jesse
next prev parent reply other threads:[~2017-03-06 22:33 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 [this message]
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
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=bb0cad75534e337507d6b06030909f20@mail.gmail.com \
--to=jjones@uniumwifi.com \
--cc=agreen@cococorp.com \
--cc=jjones@cococorp.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).