On Thu, Mar 2, 2017 at 9:41 AM, Jesse Jones wrote:
>> 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-
Hi Johannes,
Thank you for the comments, I'll see if I can apply all of your
suggestions and resubmit.
Alexis
On Thu, Mar 16, 2017 at 3:18 AM, Johannes Berg
wrote:
> Sorry - this is the other half of my reply that I accidentally deleted
> before sending...
>
>> +static void flush_tx_skbs(struct
Sorry - this is the other half of my reply that I accidentally deleted
before sending...
> +static void flush_tx_skbs(struct ieee80211_sub_if_data *sdata)
> +{
> + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh;
> + struct mesh_tx_queue *tx_node;
> +
> + spin_lock_bh(&ifmsh->mesh_tx
Hi,
So I guess after all the discussion, you should amend the commit log a
bit, certainly at least to mention the hidden-node issue.
Regarding the patch itself, I'm not super happy with how big it is,
some additional comments below:
> +struct mesh_tx_queue {
> + struct list_head list;
> +
> 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 wo
Am 09.03.2017 um 16:49 schrieb Matthias May:
> On 06/03/17 13:38, Johannes Berg wrote:
>>> 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
These images work intermittently for me. Here they are rehosted:
[1] http://i.imgur.com/zM0eLNk.png
[2] http://i.imgur.com/E7GL7U3.png
On Fri, Mar 10, 2017 at 12:40 AM, Kalle Valo wrote:
> Matthias May writes:
>
>> [1] http://may.nu/images/problem.png
>> [2] http://may.nu/images/jittered.png
>
Matthias May writes:
> [1] http://may.nu/images/problem.png
> [2] http://may.nu/images/jittered.png
I get 404 "Not Found" for these.
--
Kalle Valo
On 06/03/17 13:38, Johannes Berg wrote:
>
>> 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
> > 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
> > the
> 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 forwar
> 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 s
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
Hi Johannes,
This is loosely based on RFC5148, specifically event-triggered message
generation as described in section 5.2.
The frames are not duplicated, but, hopefully offset enough so they don't
collide at the receiver (and, since, these are management frames, there is no
retransmission and
On Fri, 2017-02-24 at 11:58 -0800, Alexis Green wrote:
> From: Jesse Jones
>
> Changes since v1: Only flush tx queue if interface is mesh mode.
> This prevents kernel panics due to uninitialized spin_lock.
>
> When more than one station hears a broadcast request, it is possible
> that multiple
15 matches
Mail list logo
