On 2014-03-10 15:40, Michael Braun wrote: > Before, ath9k divided time in ATH_BCBUF many equally sized slots. > Each bss then was assigned to a single slot, leaving some or more slots empty. > The beacons of a bss were sent at the beginning of the slot for this bss, > and then the buffered multicast packets might be sent out. > > As multicast packets are sent a lowest bitrate, wireless throughput > of multicast packets is very limited, and thus the time available > is crucial to avoid buffer overflow, which I frequently observed. I think in setups where you need to be able to send more multicast packets, you should consider increasing the multicast rate.
> This patch changes the behaviour of ath9k in two ways: > 1. the time available when processing a slot is increased > to cover all subsequent unoccupied slots as well. > This size is tracked in the variable named "slotwidth". I think we should not allow multicast transmission to eat up too much airtime during the beacon interval. If APs are flooded with multicast packets, it must not drown out useful unicast traffic. > 2. during each slot, buffered packets from *all* bss are > sent out in a round-robin fashing, skipping those > bss where stations are currently not listing. > That could be either due to > - last dtim did not containt the relevant flag or > - a multicast packet not containing the "more data" > flag was sent out. > The state is tracked in multicastWakeup, which is > true iff the stations in this bss should already > be woken up. That does not seem like a good idea to me. Powersave clients waking up to receive multicast packets should be allowed to go to sleep again as soon as possible. Keeping them awake unnecessarily by not clearing the "more data" bit at the last packet make them eat more power. > I currently don't know whether a non-buffered multicast packet > can slip between buffered packets (or between dtim notification > and the first buffered packet), so that an STA receives a > multicast packet without MOREDATA set while there a still > buffered packets to be received and just short before being > delivered on-air. The CAB queue gets enabled after a beacon and then takes priority over all other queues. No packets will slip in between once its transmission starts. - Felix _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
