On 3 March 2015 at 11:15, Krishna Chaitanya <chaitanya.mgit@xxxxxxxxx> wrote: > On Tue, Mar 3, 2015 at 3:06 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: >> >>> >> Cisco 4410N originally forced us to enable VO by >>> >> default only because it treated non-VO ACs as >>> >> legacy. >> >>> Mixed mode (uapsd + legacy) is not really the optimal >>> configuration, where we expect STA to send trigger frames periodically >>> to retrieve the DL packets (especially very first packet). >>> >>> But still if we want power save, i suggest going for >>> All u-apsd (0xF), so that AP will inform us by setting the TIM bit >>> and we can retrieve the first frame. >>> (We have this patch internally and it works well). >> >> Except where it doesn't work, like on the Cisco 4410N - see above. > But for that single AP, we are forced to lose efficient power savings > unless user configured explicitly. Correct me if I'm wrong, but u-APSD makes sense only if you have userspace apps aware of it. I don't know any. VoIP traffic uses and it works just because it generate bi-directional traffic in most cases so you have implicit trigger frames generated when you Tx, but that's probably as far as the practical use-case goes, no? You'd still need netfilter rules to reclassify your traffic anyway, wouldn't you? If you mainly wait for data you need to send trigger frames periodically and only userspace app knows what Rx latency is tolerated (that's why relying on driver/firmware auto-trigger generation doesn't cut it). Anyway I don't think you can ask users to do the opposite (i.e. disable u-APSD if they experience problems with APs). Wi-Fi should Just Work. Joys of IOT.. Michał -- 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
