linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: 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: Thu, 02 Mar 2017 09:36:54 +0100	[thread overview]
Message-ID: <1488443814.8390.3.camel@sipsolutions.net> (raw)
In-Reply-To: <58B487A8.7000602@cococorp.com> (sfid-20170227_211019_763670_B9D8D712)

Hi Alexis,

> This is loosely based on RFC5148, specifically event-triggered
> message generation as described in section 5.2.

I'm confused. I see how that generally seems to apply to any mobile
network, but it *does* state up-front that
    In some instances, these problems can be solved in these lower
    layers, but in other instances, some help at the network and higher
    layers is necessary.

I believe 802.11 *does* in fact solve these issues at lower layers.

Can you explain how you observed any problem in this area?

> The frames are not duplicated, but, hopefully offset enough so they
> don't collide at the receiver 

That wasn't my question - my question regarding duplicating was if this
was intended to *suppress* duplicates, but it sounds like not.

> (and, since, these are management frames, there is no retransmission
> and we may lose the information contained in them).

That statement isn't true in general, though it does seem that some of
the frames you're touching are actually *multicast* frames and as such
don't have any retries.

> If the two (or more) devices that reply are synchronized well enough,
> carrier sense will tell them that air is clear and messages will go
> out at the same time. It doesn't happen too often, but we found it
> noticeable enough in our testing.

I'm still curious how it happens at all, since NAV synchronisation
should prevent it at a much lower level?

johannes

  reply	other threads:[~2017-03-02  9:01 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 [this message]
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
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=1488443814.8390.3.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=agreen@cococorp.com \
    --cc=jjones@cococorp.com \
    --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).