Hi, Michal > I suppose there's a limit how much peer entries firmware is able to > pack up into a single event. The second event you handle here is still > going to have some sort of a limit and you'll end up dropping results > again. The same probably goes with vdev stats (which aren't handled > yet, but hey). vdev stats is not supported by firmware 999.999.0.636, am I right? BTW, I also saw that the same happen to latest AP firmware whenever the peer stats is more than 1. But since the first peer stats is self stats, so it is ok to overwrite it. > I think a better approach would be to make read_target_stats *append* > data to the stats structure and make ath10k wait for more possible > events instead of being satisfied with just one. > > The way you do it now seems like you end up with the extra results > being shown upon *next* stat request-response.. i.e. you see old > results. Will take a look on this. ---- Chun-Yeow -- 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
