On Tue, Sep 9, 2008 at 9:33 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2008-09-08 at 23:09 +0300, Jouni Malinen wrote: >> Johannes Berg wrote: >> > When we're an AP, shouldn't we also in some way honour the block-ack >> > action frames? Or will that be done in hostapd, which then sets up >> > block-ack via some unspecified way? >> >> The current design assumes that hostapd takes care of all management >> frames, so eyes, these would need to go to hostapd for processing and >> then setup back to mac80211 through some new command.. > > Well we can always pick out those action frames in the kernel if we want > to, that's not the problem, is it? We've indeed has kept inside just BA session action frames. > > Should the design be changed? It seems that this is more related to the > rate scale algorithm and the "can we support aggregation for this STA" > question, both of which we currently have information about in the > kernel and not hostapd. The decision might come both from RS and hostapd. RS just have more info whether there will be gain from aggregation. When throughput is not high enough it's just an overhead. Though some APs open session immediately uppon association without and RS decision. Our design is that BA can be triggered not only for RS. Tomas > johannes > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
