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 we may lose the information contained in them). 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. Best regards, Alexis Green On 2/27/2017 5:30 AM, Johannes Berg wrote: > On Fri, 2017-02-24 at 11:58 -0800, Alexis Green wrote: >> From: Jesse Jones <jjones@xxxxxxxxxxxxx> >> >> When more than one station hears a broadcast request, it is possible >> that multiple devices will reply at the same time, potentially >> causing collision. This patch helps reduce this issue. > > It's not clear to me what you mean by "collision"? Over the air the NAV > should handle the avoidance thereof, so I don't really see what this > does wrt. collisions? > > Are these frames somehow duplicates? But I don't see any suppression if > you've already put a frame on the "jittered" list then it will never be > deleted from it again, so it doesn't suppress anything in that sense? > > johannes >
