On Sunday, July 31, 2011 06:48:46 PM Harshal Chhaya wrote: > I am still figuring out how to use 64 clients with h/w > encryption on the AR9170 - enabling debug/tracing in my build isn't as > straightforward as suggested by the wiki. Actually, to do this thing correctly, I recon you should ask your employer to get you the AR9170 chip documents from atheros qualcomm [if you haven't acquired them already.] > However, I did find some very helpful information in the debug files > in 'debugfs' including the number of retries. > The current value is 4 for long packets and 7 for short packets. I don't think that the term "short packets" is what you think it is. :D > I think the small # of retries for regular data packets may be one > reason why I am seeing some throughput problems at longer ranges. Actually, your problem could be related to this thread: http://www.spinics.net/lists/linux-wireless/msg73850.html Furthermore, what's "longer range"? Is it 10-20 meters or are you talking about 200m+? [Note: mac80211 has a switch to select different coverage classes. The AR9170 MAC has a register AR9170_MAC_REG_ACK_EXTENSION to up the ACK timeout] > How do I change the number of retries for long packets? Is this a > build-time configuration or can I change it at run-time? Actually, the number of retries is controlled by the selected mac80211's rate control algorithm. However, you first take a look at debug/ieee80211/phy0/statistics/failed_count and see if it really is the lack of additional "retries" which causes data loss. Regards, Chr -- 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
