Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > On the other hand, there is hardware (even from Atheros/Zydas!) that > will not provide status reports for every frame. Also at76c50x-usb doesn't report status AFAIK. I think we need to have a new hw flag to indicate if driver reports frame status. > Also, I'm not entirely sure why the AP would lose the frame? It's a > unicast frame that will be retransmitted quite a number of times. Is it > really actually going out on the air or is there something else wrong? > Maybe just the queue priority inversion issue since this frame goes out > as higher priority as most data frames? I have received reports that in a busy office networks nullfunc frames get lost, I'm assuming due to collisions on the air. For example, wl1251 (in which firmware sends the nullfunc frame) sends an event to the host if nullfunc frame fails for some reason. I think we need to take into account in mac80211 the case when nullfunc frames get lost. > If you really need to provide this functionality I think you should > probably do it "properly" in the sense that you react to the "frame > acked" by enabling PS, rather than the other way around. This is much better. Also I'm worried about the test for nullfunc frame being a racy. I would prefer to make it sure that the nullfunc frame really is for the powersave transition. > That requires a hardware flag though that enables mac80211 to know > that all frames will get a status report unless something is > seriously wrong, since otherwise we'd *never* go into PS. Agreed. -- Kalle Valo -- 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
